So I stick with special behavior for -V0 until a real need for something else comes up.Having thougt it over, I'm also not sure if it makes sense for say -V5. Probably the best way of improving quality here is to use -V4, -V3, ...BTW 3.98.4x does waste bits. Bits are always wasted when you choose an encoding setting higher than necessary to be indistinguishable from the original. This happens with many kind of music for most people with any setting above -V5. But as not any kind of music is fine with -V5, higher settings are also alright, for those people who want it fine or at least close to fine with all of their music, and who don't have to care about storage space.
As for your Lame usage from XLD: what is XLD?
(Set of ripping guides)
I use XLD for encoding my -V0s. The LAME of XLD is wrapped in a XLDLameOutput.bundle file, compiled as a universal binary. How can I replace the LAME package inside the bundle with the 3.98.4x?
Quote from: Thorolf on 06 November, 2011, 07:30:55 AMI use XLD for encoding my -V0s. The LAME of XLD is wrapped in a XLDLameOutput.bundle file, compiled as a universal binary. How can I replace the LAME package inside the bundle with the 3.98.4x?This is not quite clear enough, perhaps due to some of your terminology. Do you mean that a compiled binary of LAME is contained within an .app-like package? Did you determine this using Finder, a right-click, and Show Package Contents? If so, can’t you just replace the binary as you would any other file?
It's MAC OS stuff, anyway.Sorry, I am not able to compile to a MAC target, even if I understood the specials of XLDLameOutput.