Seeing upwards of 24 hour lag in live shoutcast stream

mjicecast · 8th May 2013, 21:53

We're running a shoutcast stream and find in about 3 or 10 requests we are seeing a delay of upwards of 23 hours for a live stream. We haven't found any issue with the encoder or source. Is there any caching mechanism on the shoutcast server that could account for this?

DrO · 8th May 2013, 22:02

unless you've managed to configure a massive buffer, there's nothing by default that would be able to manage to maintain a 23hr+ buffer and only provide it on specific connection attempts (as your post seems to imply). depending on the encoding bitrate, there can be up to a minute (or maybe 2) delay, but 30seconds or less is more typically assuming normal 96kbps bitrates.

alfabravo14 · 9th May 2013, 00:10

I think the only way..to have a 23 hrs delay
would be to have a second (independent) stream
where the playlists are shifted by 23 hours.

I suggest you analyze more on who gets this delay and who not (stats/ip´s)
that might give you a clue. (Where are they, what player/agent, device, Os, Time)

8th May 2013, 21:53	#1
mjicecast Junior Member Join Date: May 2013 Posts: 1	Seeing upwards of 24 hour lag in live shoutcast stream We're running a shoutcast stream and find in about 3 or 10 requests we are seeing a delay of upwards of 23 hours for a live stream. We haven't found any issue with the encoder or source. Is there any caching mechanism on the shoutcast server that could account for this?

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

8th May 2013, 22:02	#2
DrO Join Date: Sep 2003 Posts: 27,873	unless you've managed to configure a massive buffer, there's nothing by default that would be able to manage to maintain a 23hr+ buffer and only provide it on specific connection attempts (as your post seems to imply). depending on the encoding bitrate, there can be up to a minute (or maybe 2) delay, but 30seconds or less is more typically assuming normal 96kbps bitrates.

9th May 2013, 00:10	#3
alfabravo14 Banned Join Date: Feb 2013 Posts: 70	I think the only way..to have a 23 hrs delay would be to have a second (independent) stream where the playlists are shifted by 23 hours. I suggest you analyze more on who gets this delay and who not (stats/ip´s) that might give you a clue. (Where are they, what player/agent, device, Os, Time)