Public bug reported:
I compared different mp3 encoding methods, and figured out that mp3
files encoded with gst-lame and with lame using the same settings match
different file sizes.
-rw-r--r-- 1 bdelagoutte bdelagoutte 6,6M 2007-11-26 17:59 the_sea_gst.mp3 ->
produced with gstreamer
-rw-r--r-- 1 bdelagoutte bdelagoutte 9,9M 2007-11-26 17:59 the_sea_lame.mp3 ->
produced with lame
-rw-r--r-- 1 bdelagoutte bdelagoutte 59M 2007-11-26 17:40 the_sea.wav ->
original wav file
Step to reproduce :
1. Rip a CD track into one wav file foo.wav
2. Encode this file into mp3 using gstreamer-lame
$ gst-launch-0.10 filesrc location=foo.wav ! wavparse ! audioconvert ! lame
preset=1002 ! filesink location=foo_gst.mp3
3. Encode this file into mp3 using command line lame
$ lame --preset extreme foo.wav foo_lame.mp3
4. Compare file size of foo_lame.mp3 and foo_gst.mp3
Note: this behavior can be reproduce with others presets (standard /
1001) and with normal switches as well (-V0 --vbr-new / vbr=4 vbr-
quality=0)
** Affects: gst-plugins-ugly-multiverse0.10 (Ubuntu)
Importance: Undecided
Status: New
--
Unexpected behavior of lame encoding plugin
https://bugs.launchpad.net/bugs/165219
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
