That sounds excessive
One of our clients streamed a funeral last week, and latency was
several seconds.
And they were going the long way around - the funeral was in Anaheim,
they were using an encoder connected to an internet satellite uplink
to a ground station in Georgia, we connected to a stream splitting
server in Ashburn, VA, then to streaming servers in Los Angeles, CA.
Basically your worst case scenario, and far less latency then you are
experiencing.
First question - where is the latency, at the encoder or at the CDN?
You can check by pulling a stream from your encoder and pulling a
stream from your CDN and comparing
Second - how are you measuring the 10-40 second time difference?
> Is there a way to minimize latency for Live broadcasts? When we broadcast
> now with WindowsMedia services we're typically seeing anywhere from 10 to 40
> seconds of latency. We have a security system with 16 cameras connected
> which I can logon from anywhere in the continental US and see with almost no
> latency. Any suggestions? We broadcast to anywhere from 10-300 unicast
> streams.
Samuel - 30 Jan 2008 21:49 GMT
OK - I'm in Maryland using Windows Media Encoder 9 Series and pushing to a
Windows Media Server in Ashburn, VA as well, and when I connect to watch
that stream from our monitoring station in Potomac, MD it has a 22 second
latency. From the same monitoring station I connect directly to the encoder
with media player 11 and get a 12 second latency. Seems excessive to me too!
> That sounds excessive
> One of our clients streamed a funeral last week, and latency was
[quoted text clipped - 20 lines]
>> latency. Any suggestions? We broadcast to anywhere from 10-300 unicast
>> streams.
Neil Smith [MVP Digital Media] - 31 Jan 2008 19:02 GMT
Possibly that points to quite a long latency at the distribution
server then. This article discusses ways to improve that
http://www.microsoft.com/windows/windowsmedia/howto/articles/reducingstartuplate
ncy.aspx
And the following article covers all sources of broadcast delays in
the system - some of which are *required* for normal operation :
http://www.microsoft.com/windows/windowsmedia/howto/articles/BroadcastDelay.aspx
My best guess at your issue wouldn't necessarily be with the buffers,
I'm thinking that you're providing a mms URL to WMP and forcing it to
negotiate whichever protocol is supported by your firewall passthrough
In this limited case I would explicitly specify either rtsp or http
URL to the server and stick to that since you know the environment can
be configured to pass the packets at the firewall from known network
locations.
HTH
Cheers - Neil
>OK - I'm in Maryland using Windows Media Encoder 9 Series and pushing to a
>Windows Media Server in Ashburn, VA as well, and when I connect to watch
[quoted text clipped - 26 lines]
>>> latency. Any suggestions? We broadcast to anywhere from 10-300 unicast
>>> streams.
------------------------------------------------
Digital Media MVP : 2004-2008
http://mvp.support.microsoft.com/mvpfaqs
Mike Lowery - 01 Feb 2008 16:32 GMT
And if your network supports it, you could try multicast or rtspu instead of
a TCP-based protocol (more latency.)
I've routed live WMV via satellite all around the world (multiple hops) with
~10s of delay this way.
> Possibly that points to quite a long latency at the distribution
> server then. This article discusses ways to improve that
[quoted text clipped - 57 lines]
> Digital Media MVP : 2004-2008
> http://mvp.support.microsoft.com/mvpfaqs
Johnny Cakes - 02 Feb 2008 17:02 GMT
Thanks all - will keep trying to make determination and post my findings!
> And if your network supports it, you could try multicast or rtspu instead
> of a TCP-based protocol (more latency.)
[quoted text clipped - 65 lines]
>> Digital Media MVP : 2004-2008
>> http://mvp.support.microsoft.com/mvpfaqs