Audacity Forum

... about the former? In such parts of the log that have been presented, the errors about AU files are all "access denied". Errors about FFmpeg are not relevant to this. Gale

... could try SoX with the -b parameter: http://sox.sourceforge.net/sox.html. It is a command-line application. As far as I'm aware, neither SoX or FFmpeg support 10-bit encoding.

... it is again, with line breaks inserted between open software, open first file, open second file. 13:12:36: Audacity 2.1.2 13:12:36: Trying to load FFmpeg libraries... 13:12:36: Trying to load FFmpeg libraries from system paths. File name is 'avformat-55.dll'. 13:12:36: Looking up PATH environment ...

... gone? How do I see the waveform? "Show Log" is below. Win 10, Aud 2.1.2 Log.txt: 13:12:36: Audacity 2.1.2 13:12:36: Trying to load FFmpeg libraries... 13:12:36: Trying to load FFmpeg libraries from system paths. File name is 'avformat-55.dll'. 13:12:36: Looking up PATH environment ...

... :) You have confirmed that Audacity loads DLLs from the project path, which is definitely a security issue. We have also learned, that Lame and FFmpeg must not be installed to make that Attack work. And we have learned how to easily demonstrate it (not needing sysinternal tools anymore). So ...

... files, you should be able to open them directly with Audacity and export as WAV. Some compressed formats may require the optional FFmpeg import/export library. The basic Audacity installation can open MP3s, but you need the optional LAME MP3 encoder if you want to create an MP3.

... it, the "lame_enc.dll" from desktop should be loaded. Here's the Logfile content: 18:44:58: Audacity 2.1.3 18:44:58: Trying to load FFmpeg libraries... 18:44:58: Trying to load FFmpeg libraries from system paths. File name is 'avformat-55.dll'. 18:44:58: Looking up PATH environment ...

So, Gale, can you confirm now, that both DLLs (Lame and FFmpeg) are loaded from the project-path when opening a project-file from Explorer/Desktop on your test-setup?
(with no lame_enc.dll existing in system32-folder)

I was wondering why it took so much longer for Lame to load than FFMpeg in the Logfile. I just realized, that Lame only loads when opening the Settings-Window. But FFMpeg DLLs are loaded immediately after opening the project without the need for any other ...

... being imported, such as an MP3 or an M4A containing AAC audio. The difference you see when reimporting the file is between file types that require FFmpeg to import and those that don't, and whether the file requiring FFmpeg is lossless or not. So, with Default Sample Format at 16-bit: M4A containing ...