PDA

View Full Version : Variable streaming rates



Steve Pawsey-Bowerman
2003-12-19, 07:45
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

dean
2003-12-19, 10:00
That's a great idea. I'll add it to our feature request list.

-dean

On Dec 19, 2003, at 6:45 AM, Steve Pawsey-Bowerman wrote:

> 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
>
>
>