© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
Bruce R, please read all the posts carefully. The "lame" element is known to be broken, and has been superseded by "lamemp3enc". Stop encouraging people to use the "lame" element.
https:/
(FYI, Gabriel Bouvigne is one of the core LAME developers).
I did elaborate tests and not even once succeeded to make the "lame" element produce the same output as the standalone LAME program, because the "lame" element internally sets a whole series of developmental LAME flags to ill-conceived values. Ironically, the combination of flags you're suggesting are the ones I came up with in January 2009:
https:/
Notice the last two sentences of my post. Yes, these flags seem to be well behaved if you only look at the output bitrates, but remember, bitrates are not everything. It's perfectly possible to encode at high bitrates and still have audible artifacts *cough* xingmp3encoder *cough*
Again, the "lame" element is officially deprecated; the "lamemp3enc" element leaves all flags at their (good) default values and produces outputs that are bitwise identical to standalone LAME.
Oh yeah, I still don't know what name=enc does, but it's definitely *not* "ensuring use of the correct LAME plugin". My best guess so far is that it sets some tag, which perhaps facilitates interfacing with some other program.