I've actually found out why the mistake happened. It didn't happen. Back
then. When it was decided to move to this configuration for transcoding,
the -v switch simply indicated to use VBR encoding. In later versions of
LAME this changed and it became a substitute for -V 4.
Old LAME (3.89) relevant help section:
Code:
--------------------
VBR options:
-v use variable bitrate (VBR) (--vbr-mtrh)
--vbr-old use old variable bitrate (VBR) routine
--vbr-new use new variable bitrate (VBR) routine
--vbr-mtrh a merger of old and new (VBR) routine
-V n quality setting for VBR. default n=4
0=high quality,bigger files. 9=smaller files
-b <bitrate> specify minimum allowed bitrate, default 32 kbps
-B <bitrate> specify maximum allowed bitrate, default 320 kbps
--------------------
New LAME (3.99.5) relevant help section:
Code:
--------------------
VBR options:
-V n quality setting for VBR. default n=4
0=high quality,bigger files. 9=smaller files
-v the same as -V 4
--vbr-old use old variable bitrate (VBR) routine
--vbr-new use new variable bitrate (VBR) routine (default)
-Y lets LAME ignore noise in sfb21, like in CBR
-b <bitrate> specify minimum allowed bitrate, default 32 kbps
-B <bitrate> specify maximum allowed bitrate, default 320 kbps
--------------------
The sad thing is that Squeezeboxes display the transcoding bitrate that
the server communicates, based on server settings, and not the actual
bitrate of the file being played back. Hence the problem in discovering
this (and why I used foobar2000 streaming to check).
------------------------------------------------------------------------
gorman's Profile: http://forums.slimdevices.com/member.php?userid=56
View this thread: http://forums.slimdevices.com/showthread.php?t=94642
_______________________________________________
discuss mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/discuss
