Bugzilla – Bug 27
make the transcoding to HTTP streams able to be specified in the URL
Last modified: 2009-03-12 14:57:43 UTC
From: steve.pawsey-bowerman Subject: [slim] Variable streaming rates Date: December 19, 2003 6:45:28 AM PST To: Discuss@lists.slimdevices.com Reply-To: discuss@lists.slimdevices.com Hi, Having got remote streaming working a treat (so that WAN streaming is at a much low bitrate than LAN streaming). I now want to go one better and set-up 3 different (hi,med,low) streams that I can access remotely. Having played around with apache, mod_proxy and virtual IP hosts until blue in the face, I an find no way of doing this (short of running multiple slimserver instances or running multiple physical apache servers). However, one last idea came to mind. I wondered how easy it would be to pass a bitrate parameter into the stream.mp3 request, and subsequently utilize this value in the convert.conf, thus: http://slimserver:9000/stream.mp3 for normal 'unspecified' bitrate streaming (ie uses the source bitrate) http://slimserver:9000/stream.mp3?bitrate=128 for 128Kbs bitrate http://slimserver:9000/stream.mp3?bitrate=32 for 32Kbs bitrate etc etc The convert.conf would then utilize the bitrate variable like mp3 mp3 http * $lame$ --silent --mp3input -b $BITRATE$ -q 9 $FILE$ - Now, I know there's and existing parameter called $BITRATE$, but I think this is the source bitrate rather than destination bitrate. Answers on a postcard.. TIA Steve
Feature added post 5.1.1. Works best as a new client, but can work on a client that has already made a connection. Playback needs to be restarted, or wait for song boundary to get the new rate.
There are 536 bugs in the database with targets of '---' that were fixed prior to new year 2006. I am setting them to targets of 6.2.1 to keep them from showing up in my queries.
*** Bug 11332 has been marked as a duplicate of this bug. ***