Hello I installed FFmpeg, long before even looking at audacity. FFmpeg is actually installed on another drive entirely. What my question is “how does one tell audacity the FFmpeg folder (version 3.2.2) is on drive F:\ffmpeg-3.2.2\bin” ? Also what is this dylib? I have an ffmpeg.exe, but no weird things like that. (Yes, hidden folder is on by default and drive is completely indexed) Can I just select the ffmpeg.exe?
It might be best to run the FFmpeg for Audacity installer and install another copy. It might be a special compile.
To “tell” Audacity where it is, go to Edit → Preferences → Libraries and click Locate.
It’s avformat-55.dll and several other DLLs, and on my computer it’s located in C:\Program Files (x86)/FFmpeg for Audacity.
You can’t choose ffmpeg.exe in Audacity’s Libraries Preferences. To load FFmpeg via Preferences, you have to install FFmpeg 2.2.2 according to FAQ:Installation, Startup and Plugins - Audacity Manual. You can use a slightly later FFmpeg 2.2.3 but it has to be a “shared” build that includes separate dylib files.
If you want to use the 3.2.2 ffmpeg.exe, the only way to do that is to choose the command-line “(external program)” when you export and include “F:\ffmpeg-3.2.2\bin\ffmpeg.exe” as the first part of the command. See Exporting to an External Program. Note that you cannot use FFmpeg to import files this way - it’s just export.
Gale
Well, that’s kind of inconvenient. Might as well just use FFMPEG by itself w/ windows 10 default recording app. Thanks for you help though.
I agree that it would be better to leverage arbitrary ffmpeg executables rather than be tied to specific (now oudated) versions of shared libraries (DLL files) but we don’t really have the resources to make that change right now.
One possibility might be to accept that using different FFmpeg versions is “advanced usage” and have command-line import like we have command-line export. It might be less work than making the standard export dialogues use ffmpeg executables.
Gale