oreillymj Wrote: > I had bit-rate limiting on a player I was using to test streaming across > my my broadband connection. Since the upload speed is only 265kbs, I was > testing with limiting set to 192kbs. > > However it seems that the commands sent to Lame were getting it to > encode using VBR and the kbs being displayed in Winamp were often > higher than 192. SlimServer switched from using CBR to using ABR to maximize the sound quality at a given streaming rate. ABR is a type of VBR, but with the bitrate targeted to a fairly constant average level. This should have the effect of increasing quality while still keeping the bitrate across the network link at a fixed level.
> Another strange thing is that Lame was running at all. All of my music > is ripped at 192kbs CBR. > > Surely LAME should only be invoked to re-encode on the fly if the > bitrate limiting setting is below the bitrate the MP3 file was ripped > at. Hmmm... Yeah, but I think this is the only scenario where you can get away with _not_ having to use LAME to re-encode - only when the file is encoded using CBR and when the bitrate is at an equal or lower value than the bitrate limiting. Perhaps this scenario wasn't taken into consideration in the logic, or perhaps SlimServer doesn't store whether or not the file was encoded using CBR. For a file encoded using VBR you can't really say what the bitrate is always going to be, so you pretty much have to re-encode. -- JJZolx Jim ------------------------------------------------------------------------ JJZolx's Profile: http://forums.slimdevices.com/member.php?userid=10 View this thread: http://forums.slimdevices.com/showthread.php?t=20363 _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
