One of the error log I got after installing Audacity 2.3.2 and launching it (step 3, 4 and 5):Ġ3:51:11: Error: Couldn’t find symbol ‘AudacityModule’ in a dynamic library (error 127: La procédure spécifiée est introuvable.)Ġ3:51:13: > Trying to load FFmpeg libraries> …Ġ3:51:13: mLibAVFormatPath (‘C:\Program Files (x86)\Ffmpeg For Audacity\avformat-52.dll’) is not empty. It could be that something needs to be changed with the way the installer updates/replaces/uninstall previous versions of FFmpeg. … it seems it is necessary to uninstall the previous FFmpeg installation in order to make the more recent version of Audacity work. There is no need to uninstall FFmpeg 0.6.2 first. If you have the previous FFmpeg 0.6.2 installed to the same location, the FFmpeg 2.2.2 installation will overwrite the 0.6.2 installation with the new files. So I believe that, unlike what is said here, After this was done, I exited and launched Audacity again: no debug error, working fine, FFmpeg still detected. Followed the official Audacity instructions here, and it worked fine, detecting the library immediately. Installed Audacity 2.3.2, this time it’s launching without any debug error messages.Ĭhecked the Preferences, it said FFmpeg was not detected. Followed the steps, checked the -version in CMD: it worked. ~ 8) So I followed that Wikihow guide that included steps for the PATH modification. ~ 7) Tried installing the latest version of FFmpeg from the official website, but it seems it doesn’t come with an installer (got the 4.2.1, 64 bits, static from here, official link for Windows builds) Uninstalled Audacity, removed the remaining folder in Program Files, reinstalled Audacity 2.3.2, same errors.Īfter reading the post by sadmoody 2.3.0 Debug Error - #22 by sadmoody I uninstalled Audacity, but also uninstalled FFmpeg, then rebooted. Uninstalled Audacity, reinstalled Audacity 2.3.2, same errors. Launching Audacity immediately produced these debug error messages. Installed Audacity 2.3.2 over the existing 2.0.6, by simply installing it in the same folder. Previous installs : Audacity 2.0.6 and “ FFMpeg for Audacity” 0.6.2ĭownloaded Audacity 2.3.2 on Fosshub, “Audacity Windows Installer”, MD5 = 42b470ba618d0e89427dcbc590e9d5be Sorry for the old bump, but it’s the first result on Google Search and the issue just happened to me on 2.3.2, and I fixed it on my end! We could do with a lot more people to test release candidates, but as Audacity is created and supported by volunteers, we have to make do with what resources are available. Unfortunately, despite the enormous number of users of Audacity, there a very few that test and give meaningful feedback about these pre-release versions. “Release Candidates” (pre-release test versions) are due to become available within the next few weeks. It will be built against a different build of WxWidgets, so hopefully this bug will not occur in the next version. The next release of Audacity is due this month. The bug was not discovered before release because it does not occur for any of the developers or testers. It’s not that the developers don’t care about this bug, it’s that the developers are not able to reproduce this bug, but they believe that it is probably due to building Audacity against a version of WxWidgets that has too high a level of debug messages. However, having already given so much, one would think that they would want to go the last few yards and get rid of this behaviour. I tried to install lame manually, but did it wrong - after that ive started getting these debug error as same as the pring of the guys. My audacity was fine till i gotta the need of openning a *.mp3 file.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |