Re: [FFmpeg-user] Approach to Fully Lossless Concat

2018-10-17 Thread VP Lists
Yes, I had to, I think. I defaulted to that, then moved to intermediate .ts files just to make it even more foolproof…so I am thinking. ffmpeg -y -i \"concat:#{ couple }\" -bsf:a aac_adtstoasc #{ d }/final.mp4 Those are file lists and path. > On Oct 17, 2018, at 10:45 AM, Paul B Mahol

Re: [FFmpeg-user] Approach to Fully Lossless Concat

2018-10-17 Thread Paul B Mahol
On 10/17/18, VP Lists wrote: > On Oct 4: > >> Hi folks. I've created a list of small clips in random order, each with a >> unique filename. This file is used for a concat input file. >> >> In the verbose processing, I get lots of these after a few of the first >> files are processed: >> >>

Re: [FFmpeg-user] Approach to Fully Lossless Concat

2018-10-17 Thread VP Lists
On Oct 4: > Hi folks. I’ve created a list of small clips in random order, each with a > unique filename. This file is used for a concat input file. > > In the verbose processing, I get lots of these after a few of the first files > are processed: > > Error while decoding stream #0:0:

Re: [FFmpeg-user] Approach to Fully Lossless Concat

2018-10-17 Thread Carl Eugen Hoyos
2018-10-17 13:32 GMT+02:00, VP Lists : > I’ve tried two approaches to bring some short clips I’ve created in > QuickTime Player 7, all together in a concat. Both approaches > demonstrated a shift in audio vs video timelines. Command line and complete, uncut console output missing, please

[FFmpeg-user] Approach to Fully Lossless Concat

2018-10-17 Thread VP Lists
Hi there. I’ve tried two approaches to bring some short clips I’ve created in QuickTime Player 7, all together in a concat. Both approaches demonstrated a shift in audio vs video timelines. They were: - Direct concat - Intermediate xxx.ts files brought together via concat after The syntax