Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • The process substitution example here creates an input list that ffmpeg doesn't like; it barfs for me with [concat @ 0x10201a200] Impossible to open '/dev/fd/./01 Track.mp3'. I fixed it by making the path to the files absolute: ffmpeg -f concat -i <(printf "file '/path/to/files/%s'\n" *.mp3) -c copy output.mp3 Commented Feb 24, 2014 at 21:15
  • +1 However, as per this answer, you can specify the files inline with "concat:file1.mp3|file2.mp3" instead of inputs.txt, and then -f concat is unnecessary.
    – Sparhawk
    Commented May 1, 2017 at 3:53
  • 1
    @Sparhawk The concat:file1.mp3|file2.mp3 merges the files before sending it to the decoder. It's basically doing cat file1.mp3 file2.mp3 | ffmpeg -i - and thus can lead to decoding errors when the second file differs from the first or the decoder stumbles over header data in the second file. Using -f concat with a list of files decodes each file on its own and uses the stream only.
    – mbirth
    Commented Jul 30, 2023 at 17:02
  • Nice find @mbirth. There is more information on the ffmpeg page.
    – Sparhawk
    Commented Jul 30, 2023 at 22:48