Bugzilla – Bug 662
Silence MP3 does not honour bitrate limit
Last modified: 2011-03-16 04:39:09 UTC
When streaming media via the .../stream.mp3 URL, music is transcoded as necessary to support the bitrate limit configured for that player. However, when the server is paused or stopped, the silence MP3 that is played is not transcoded and attempts to transmit at its full bitrate (320 kbits). This has the result that the the server will flood the network connection during this time, if the network cannot keep up with 320kbit (as is the case over my 256kbit ADSL upload limit, for example). Other than this, I love SlimServer and Squeezebox! There may be some good reason for this that I don't understand, but the reason eludes me so far. Thanks, Stuart
the good reason could, perhaps, be simplicity. not to hack on usage of the stream.mp3 feature but it is understandably not the highest priority. it looks like the server is simply sending chunks from a single silence.mp3 file without having to mess with loading it to the playlist and runnign all the conversion checks that are done for real tracks. Why this has to be a 320kbps silence.mp3 instead of 64kbps, I dont know. Maybe the lbrsilence.mp3 file would work just fine in this case.
Created attachment 706 [details] simple patch to deliver lbrsilence for bitrate limited http players if maxRate is not 0 or 320, send lbrsilence.mp3 (96kbps). Drawback is that this loops much faster so the cpu load is much higher.
Please consider to commit the patch...
as of change 6177, will deliver lbrsilence.mp3 when stream.mp3 bitrate is not 320 or 'no limit'. this will be in 6.5 builds as of Jan 10. probably as much as will be done on this one. It will get rid of the rebuffering issues that come up every so often with new users. with softsqueeze available, use of that should be encouraged.
This bug appears to have been fixed in the latest release! If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look. Make sure to include the version number of the software you are seeing the error with.
Routine bug db maintenance; removing old versions which cause confusion. I apologize for the inconvenience.