PasTim wrote: > Should I try altering the 'buffer fullness' parameter, currently at 255? BufferThreshold will not affect rate of filling the internal buffer and so not affect the 404 issue.
"Buffer full threshold" is the level in Kbytes the buffer must reach before the player starts playing. Too small and the player will run out of data before next packet arrives or if there packet flow is lumpy and so there will be a gap. Making it bigger just increases the delay between pressing "play" and hearing music. For a slow speed 32kbps stream a setting of 100 would be about 25 secs delay before audio starts whereas with a 128kbps stream it would be a 6 sec delay and for the BBC DASH Flac it would be about 2 sec delay. A setting of 100 for DASH Flac is about 2 sec but each segment is 3.84 sec so it means audio will start when there is only one packet in player buffer and so for setting less than 100 there is a good chance of a gap in the audio just after playing starts of next packet doesn't arrive within about 1sec. BBC Dash Flac segment (each require a http GET) vary between about 128kbytes and 200kbytes and there is a gap "fetch time" between each segment usually less than 300msec but can be bigger and does vary a lot as noted in the log. So for higher speed stream it is better to have a bufferThrehsold set as high as possible. ------------------------------------------------------------------------ bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=104672 _______________________________________________ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
