I ended up using the concat demuxer instead, which worked just fine but is not as simple since I can’t just name the files on the command line. So, is there something wrong or out of date with the documentation? Does it not work on Windows for some reason (I would think that being in quotes should prevent the pipe characters from being an issue), because in all cases it just seems to ignore the command after the first file. And the time it reported for the output file, about 18 minutes, is that of the first segment only.
Then I tried it with MOV files from the Canon camera.Īgain, there was no error, but the result was only the (approximate) size of the first file, which is 4GB in this device. But there is no error of any kind, either.
The final lines of output (shown below) shows that the media time is the same as the first part (1:02). I didn't think it was strange that the information displayed at the start of the run only showed the first file, as the parts are supposed to be identical in format so it only has to sniff one to find out. 2GB in size, but not identical to the first part. I tried: ffmpeg -i "concat:ste-000.wav|ste-001.wav" -c copy Zoom.wavĪnd the result was just the first part again, with no concatenation. I first tried the WAV files I got from the Zoom H4N recorder. Naturally the codec and container will always be identical, across the pieces. This way I don't have "parts" that need to be kept together, and applying settings to a clip doesn't require duplicating everything on the continuation segments.
My devices generally split up the files it saves to the SD cards, either with a 2G or 4G file size limit.īefore importing the files into my timeline, it would be very convenient to concatenate the logical files back together to one physical file. I'm using the latest ffmpeg (3.2.4) on 64-bit Windows 10.
0 kommentar(er)
