ralphFFM wrote:The Problem with strings hanging is tht the Windows Media Player requires that the stream be transcoded. The Problem is that choosing a better Format and pricture quality causes the server's CPU usage to sky rocket at 100%. HTTP Streaming direct from the server brings bad quality but limmted CPU usage. If you ask me, the remote API brings little Advantages for a true streaming Server with multiple asychron viewers.
ralphFFM wrote:Like I said, my test show that using Windows Media Player causes the CPU where DBVLink Server is running to shoot up to and remain at 100%. Not advisable if you wan't to continue using the CPU. This is do to the transcoding on the server side for the ACF protocol.
I switched to a media player which accepts raw_http stream and the API works like a charm without posing a potential hardware threat.
Users browsing this forum: No registered users and 1 guest