GNOME Bugzilla – Bug 320200
vorbisenc: min-bitrate and max-bitrate are 1/1000 bps rather than 1 bps
Last modified: 2005-11-30 02:26:30 UTC
Using gstreamer 0.8.11 and the python bindings with this gst string: filesrc name=source ! mad name=demuxer ! audioconvert ! vorbisenc quality=0.0 min-bitrate=97000 max-bitrate=224000 ! filesink location=/tmp/transcode/000\ blah.ogg Results in a very small file, and the following output from ogginfo: New logical stream (#1, serial: 1a619f82): type vorbis Vorbis headers parsed for stream 1, information follows... Version: 0 Vendor: Xiph.Org libVorbis I 20040629 (1.1.0 rc1) Channels: 2 Rate: 44100 Nominal bitrate: 64.000000 kb/s Upper bitrate: 0.224000 kb/s Lower bitrate: 0.097000 kb/s Vorbis stream 1: Total data length: 21901 bytes Playback length: 2m:47.888s Average bitrate: 1.043594 kb/s Logical stream 1 ended Multiplying them by 1000 giving me this string: filesrc name=source ! mad name=demuxer ! audioconvert ! vorbisenc quality=0.0 min-bitrate=97000000 max-bitrate=224000000 ! filesink location=/tmp/transcode/000\ blah.ogg gives me the following output from ogginfo (and an expected size file): New logical stream (#1, serial: 6ac619a1): type vorbis Vorbis headers parsed for stream 1, information follows... Version: 0 Vendor: Xiph.Org libVorbis I 20040629 (1.1.0 rc1) Channels: 2 Rate: 44100 Nominal bitrate: 64.000000 kb/s Upper bitrate: 224.000000 kb/s Lower bitrate: 97.000000 kb/s Vorbis stream 1: Total data length: 2176816 bytes Playback length: 2m:47.888s Average bitrate: 103.726451 kb/s Logical stream 1 ended The documentation produced by "gst-inspect vorbisenc" states that the unit is bps, not millibps (millibps doesn't really make sense anyhow ;) ).
I've fixed this for 0.9.x, which will be in the upcoming 0.9.6 release. A backport to 0.8.x would be simple, but I don't intend to do it - 0.9 IS THE FUTURE!
I only care that it's fixing in the new releases as well. The only reason I didn't report for 0.9.x is that I was too lazy to build it and check that the bug was still in there :p (yes sorry, but I figured it would take all of 10 minutes to check for the bug in the latest build with it already setup).