
If you export as MP3 the new MP3 has gone-through another generation of lossy compression and some "damage" does accumulate. Audacity is going to decompress when it opens it anyway.Īs you may know, MP3 is lossy compression. It's just easier and more foolproof if you convert/decompress to WAV (or FLAC). It can optionally use FFmpeg to open MP3s and it's more forgiving than the built-in decoder but I forgot the trick that tells Audacity to use it. If it's MP3 it will say "MPEG Audio (Version 1) (Layer 3)".Īudacity doesn't need FFmpeg for MP3s. MediaInfoOnline can tell you if it's an MP3 but it won't tell you if there's a problem. Audacity is going to decompress the file anyway so although it's an extra step for you, it's basically the same process. The easiest solution is to convert the file to WAV or FLAC with a 3rd party application like KabuuAudio Converter or TAudioConverter. Audacity is more picky about MP3s than most other software and there are a lot of "bad ones" out there. I really hope she does.I assume the files play in Windows Media Player, etc?Įither it's not really an MP3 or it's an "imperfect MP3". I hope she comes back and tries again with the new pointers (and, as GHOT pointed out, the right zipped file). We've shown OP that it can be done, and easily.


Did you get a choice, or did the program just find the file immediately after you pushed Locate? I think now (just maybe) it gave me a choice between the program finding it and yours truly finding it.

I'm sure that (if memory serves, and sometimes it doesn't) when I pushed Locate, it responded with a. Why would that work for you and not for me? I'm not doubting you, I'm just puzzled.

But that surely can't be because your avformat-55.dll was in a folder you named FFMPeg, while mine was in a folder I named ffmpeg-win-2.2.2. You've discovered that you can eliminate "negotiated to the ffmpeg-win-2.2.2 folder, selected avformat-55.dll, OK" by doing what exactly?Īfter I pushed Locate, I had to browse to my ffmpeg-win-2.2.2 folder, which is inside the same folder my other Audacity files are in. When you go tp Preferences > Libraries and click the Locate button it detects then automatically, you don't even need to go browsing for them.Okay. If you unzip ffmpeg-win-2,2,2.zip to the \App\FFMPeg sub-folder in the folder where Audacity is installed then it really is a breeze.
