It seems it was never FFMPEG's fault, as quicktime and Blender opened the
files complete. The culprit was Adobe Premiere.
A rather complete solution can be found here:
On Mon, Feb 5, 2018 at 4:37 PM, Fernando Peña D'Andrea <
> The second one caused that. But I figured the problem. I was searching for
> the wrong culprit. It's a bug in Adobe Premiere, not on FFMPEG nor my
> python script.
> To whoever happens to incur on the same problem: https://superuser.
> On Mon, Feb 5, 2018 at 10:18 AM, Carl Eugen Hoyos <ceffm...@gmail.com>
>> 2018-02-01 21:28 GMT+01:00 Fernando Peña D'Andrea <
>> > Hello, all!
>> > I'm trying to script-cut a 24 fps video and it gets close to the right
>> > thing, except for two missing frames at the beginning of every segment I
>> > cut with seeking.
>> > I've found out that index-frames (keyframes) could become an issue for
>> > seeking, so I first create an intermediate file with every frame as a
>> > frame using this line:
>> > ffmpeg -i input.mov -c:v libx264 -g 1 -c:a copy intermediate.mp4
>> > Then I proceed to make a cut with this line. Notice I'm drawing some
>> > on top of it:
>> > ffmpeg -hide_banner -y -i intermediate.mp4 -ss 00:00:02.083333333333
>> > -to 00:00:02.875000000000 -vf
>> > drawtext=fontfile=DroidSans.ttf:fontsize=48:text="segment2":
>> > output.mp4
>> > No matter the length of the segment, the first two frames get dropped.
>> Which of the two commands you provided drop two frames?
>> Please test current FFmpeg git head and provide the command line
>> you tested together with the complete, uncut console output.
>> Carl Eugen
>> ffmpeg-user mailing list
>> To unsubscribe, visit link above, or email
>> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
ffmpeg-user mailing list
To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".