Bug 4740 - Automatic Bitrate Limiting?
: Automatic Bitrate Limiting?
Status: NEW
Product: Logitech Media Server
Classification: Unclassified
Component: Streaming From SlimServer
: unspecified
: PC Windows XP
: -- enhancement (vote)
: Future
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-02-05 14:30 UTC by Yann Oehl
Modified: 2011-11-06 23:24 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yann Oehl 2007-02-05 14:30:19 UTC
Just curious if such a feature could be developed... the idea being that if "automatic" was selected in the Bitrate Limiting dropdown, SS could automatically adjust the bitrate up or down depending on the status of the audio buffer. 

Example of use: Currently when streaming remotely if the connection becomes congested the user must manually set the bitrate to a lower level in order to avoid cut-outs... and back up when things clear up. Could this be automated?
Does this make sense? Is it even feasible? Thanks!
Comment 1 KDF 2007-02-05 20:30:53 UTC
the architecture currently only supports a bitrate limit when initiating playback. As such, it would likely be a very large rewrite to adjust on the fly.  Maybe less so as a retry on a buffer underrun.  

Eg: alac->wav transcode underruns, restart playback forcing mp3 to get better overall results
 
similar for radio, if the link is dropped, we could automatically drop the maxrate one more step.  

just ideas - I'm not volunteering to make the patch at this time.
Comment 2 Yann Oehl 2007-02-05 20:38:32 UTC
(In reply to comment #1)
if the link is dropped, we could automatically drop the
> maxrate one more step.  

This is exactly what I was thinking.... nothing too fancy.
Thanks for volunteering KDF!

(Just kidding of course)
Comment 3 Alan Young 2011-11-06 23:24:33 UTC
Unassigned bugs cannot have a priority.