
FFmpeg should automatically choose the number of CPU threads available.Failing to do so may cause parameters being skipped or will prevent FFmpeg from executing. It is important that parameters are specified in the correct order (e.g.If it fails in FFmpeg, then Audacity has the same limitation. One way to test if there is a problem in the Audacity implementation of FFmpeg is to use a command-line version of FFmpeg separately to perform the same task. Information correct as at August 2008 can be viewed on our main Wiki site. In particular, FFmpeg can only export about two-thirds of the formats that it can import. The limitations apply to both specific formats and codecs and to their metadata. This also means that if FFmpeg can't perform a particular conversion, Audacity can't do it either. That is, you should be able to use Audacity to transcode audio with the same results as using FFmpeg directly. Audacity aims to provide the same exporting/importing features as FFmpeg.This contains technical information which can be extremely useful when debugging any FFmpeg export, import or library loading issues. If the exported file is unplayable or corrupt, try the debug log at Help > Show Log. If everything is fine, the file will be exported.Enter your required metadata tags in the "Edit Metadata" dialog that appears (note that some formats may not support all metadata tags, or may support none at all).You must add an extension (for example, ".WAV") compatible with the format you are exporting.

This merges those presets with the current ones in "ffmpeg_presets.xml". To import presets from that location, choose "Import Presets".

The other list will be reduced to show only compatible entries.

