I've used bladeenc for years (despite it's recent end-of-life) and loved it. Updating to gcc 3.2.1 and recompiling bladeenc yields poor-quality mp3s. Looks like it's time to hop on the Ogg (or lame) bandwagon...
assigned
if it is true bladeenc produces poor-quality (how poor btw?), is it known why?
bladeenc has performed very nicely for me over the past 3 years, and was great under Gentoo until I recompiled it using gcc-3.2.1. (It was fine with Gentoo/gcc-2.9X - still is great on my RH systems.) A few weeks ago, I switched to gcc-3.x and started upgrading my Gentoo packages. I recently rebuilt bladeenc using gcc-3.2.1 and ripped some mp3s. bladeenc has serious issues with this compiler. As a check, I manually encoded the same .wavs using bladeenc, lame, and oggenc. They sound fine after being encoded with lame and oggenc, but not bladeenc. The problem is that bladeenc's developer previously announced the end-of-life (as far as he's concerned) for this project. See http://bladeenc.mp3.no/ for the announcement. His rationale is explained there. Has anyone else had problems with bladeenc after updating gcc?
i guess i can't really do much. a user could always download a gcc-2.x series gcc and compile it manually if they really needed it. i guess thats reason enough to keep this in portage (and people are still using gentoo 1.2). the alternative might be to include a binary from elsewhere.
