I can't remember the exact detaisl but the numebr relate to player buffer fullness - undecoded and decoded. That said, they won't help you solve rebuffering.
Rebuffering occurs when the player has not enough data - i.e. internal decoded buffer is empty. When streaming a station the player can receive dataeither directly form the station or via LMS. Stream have to go through LMS either because transport protocol used is not supported by player (e.g. Spotify, BBC DASH or HLS) or because the audio format isnot support by the player and has to be transcoded (e.g. Boom does not support AAC). IIRC although LMS is required setup Pandora connection once playing it is a MP3 stream which plays direct to player. Don't know about Deezer. Booms is an "old" player now with a small internal buffer which means audio from station has to be smoth stream to avoid rebuffering - if the stream is "lumpy" and data comes in bursts then player is liable to run out of data. If you are playing AAC stream and LMS is on a Windows system - there may be another issue but . Things to try: 1. Under LMS WebUI Settings./Advanced/Network change "Radio Station Buffer Seconds" to a higher number. This will increase the "delay" before station starts playing but increase the amount of data buffered in player. Can help smooth out "lump" 2. Under LMS WebUI Setting/Player/<playername>/Audio set "Streaming Method" to "proxied". Thsi will mean data from station will first be buffer by LMS - ans LMS hosts have bigger buffers and acts as an intermediate - this can help smooth out "lumpy" stream ------------------------------------------------------------------------ bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=107744 _______________________________________________ Squeezecenter mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/squeezecenter
