[FFmpeg-trac] #8536(wiki:closed): 'wiki: Concatenate' confusion
FFmpeg
trac at avcodec.org
Mon Feb 24 08:41:28 EET 2020
#8536: 'wiki: Concatenate' confusion
-------------------------------------+-----------------------------------
Reporter: markfilipak | Owner:
Type: defect | Status: closed
Priority: minor | Component: wiki
Version: unspecified | Resolution: wontfix
Keywords: | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-----------------------------------
Changes (by Gyan):
* priority: normal => minor
* resolution: => wontfix
* status: new => closed
* component: website => wiki
Comment:
For context, the preceding text is
------
Create a file mylist.txt with all the files you want to have
concatenated in the following form (lines starting with a # are ignored):
{{{
# this is a comment
file '/path/to/file1.wav'
file '/path/to/file2.wav'
file '/path/to/file3.wav'
}}}
Note that these can be either relative or absolute paths. Then you can
stream copy or re-encode your files:
{{{
ffmpeg -f concat -safe 0 -i mylist.txt -c copy output.wav
}}}
The -safe 0 above is not required if the paths are relative.
------
So 'paths' refers to the file paths specified in the concat text file, as
signified by the specimen `/path/to/file1.wav`. With `-safe 1`, all file
paths must be deemed safe.
Here's the requirement for filename safety, as given in the
[http://ffmpeg.org/ffmpeg-formats.html#Options docs]:
If set to 1, reject unsafe file paths. A file path is considered safe
if it does not contain a protocol specification and is relative and all
components only contain characters from the portable character set
(letters, digits, period, underscore and hyphen) and have no period at the
beginning of a component.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/8536#comment:1>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list