Re: [Audacity-devel] mp3 export P2
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Leland <le...@au...> - 2009-01-01 05:43:25
|
Gale Andrews wrote: > | From Leland <le...@au...> > | Wed, 31 Dec 2008 14:23:41 -0600 > | Subject: [Audacity-devel] mp3 export P2 >> Quoting "Gale (Audacity Team)" <ga...@au...>: >>> OK - in src/export/ExportMP3.cpp I have (locally): >>> >>> // Always write the info (Xing/Lame) tag. Until we stop supporting Lame >>> // versions before 3.98, we must do this after the MP3 file has been >>> // closed. >>> //#if !defined(__WXMSW__) >>> exporter.PutInfoTag(fName); >>> //#endif >>> >>> but both ANSI Release and Unicode Release here on Windows won't recognise >>> lame_enc.dll in >>> http://audacity.homerow.net/index.php?dir=lame >>> >>> so I just get "not found" in Prefs. Is it recognised for you in Prefs on >>> Windows? >>> >> Sorry, try Debug builds. I built it as a debug library. I figured all of us >> would be doing Debug builds. Once we've verified that the issue has been >> resolved, I'll make it a release build and have Buanzo update the distrib site. > > I almost always do (ANSI) Release, because I'm doing regular > development builds for the public (a bit like the Mac nightlies, but > not automated). > > Anyway, I've built Unicode Debug and used the new "multi-threaded > DLL" version of lame_enc.dll with CBR, ABR and VBR (including presets), > and checked for actual and reported length, and for bit rate. I checked > in Explorer, WMP11, iTunes, Foobar, QuickTime and Winamp. I'm glad to > say I can't find any problems at all, even in iTunes. As an added bonus, > WMP11 can now see the Year tag, so we're probably ahead of much of the > competition now as regards Year tags in WMP11 and VBR files in iTunes. > Thanks, Leland. Do you also have to rebuild the dmg for Mac? > Yippee!!! That's good news. No, I don't have to rebuild for the Mac as that one was already a release build. I'll rebuild the Windows fella tonight and notify Buanzo. > David Bailes asked why (external program) using LAME.exe gives a different > achieved average bit rate for a given target compared to lame_enc.dll in > Audacity. Sorry, I don't really know unless there is some algorithm setting > turned on in lame_enc.dll that affects ABR/VBR, or unless it is something > to do with code optimisation differences? At least, lame_enc.dll is consistently > closer to the target than LAME.exe. > Correct. LAME.exec turns other things on/off than we do, so we'd probably never match exactly. But, they should be fairly close. Leland |