new version of madplay, libmad and libid3tag are still 0.15.1b, but they seem to work together. i tried adding USE=alsa and USE=esd, but those seem to break it, so that's not included. had to change the depends to let it work with those non-matching versions. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 29797 [details] the new ebuild
use debug && myconf="${myconf} --enable-debugging" \ || myconf="${myconf} --disable-debugging" use nls || myconf="${myconf} --disable-nls" What's wrong with use_enable?
i'm not sure, but i was guessing the previous authors did that for a reason :\ also, it's my first ebuild so i'm shy :D
thanks... I'll take a look at this in a few =)
hmm... is this even needed? I thought lame fixed itself in the 3.96 release... can you verify that you need this version.
ok, it's late forgive me... it doesn't matter what version of lame is in portage... other people could've used it, so I guess this hack is valid, but I'd like to patch it to not do the gain correction if 3.96 works. can you verify for me that 3.96 still makes "broken" files...
the what? the only think i noticed this ebuild has is --with-accuracy (rather than like --with-speed).. so it should be the same as all previous ebuilds of madplay right?
look at the Changelog upstream. it just does some audio level adjustment on mp3s that were encoded with lame >=3.95.1
From what I can tell, Lame is still using the 89dB gain level, so madplay will correct that (because madplay wanted 83dB for replay gaim). The 89dB replay gain is mentioned in man lame, and in the changelog. There is no mention of them going back to 83dB though. They did add some options to disable replay gain in 3.96 though. So I think it's safe to assume that if you use any of the replay gain options in Lame 3.96, they will still be "broken". I don't know if it's possible to verify this on a more technical level though...
