I tried running your exact command and got the same result. Dropped frame 173 and a later duplicated frame.
I've attached 15 frames here of the results. https://drive.google.com/drive/folders/139rjLqsxIuAO_3yzVNe4dD7-gI9YPRgn?usp=drive_link I've attached 5 frames each of the original input, using detelecine, and using fieldmatch+decimate with your command. The 2nd frame of the original input was skipped with fieldmatch+decimate. The frames are similar looking, but the character is a lot more blurry and the sword is at a different angle. Specifically detelecine2.png was skipped in fieldmatch+decimate. On Wed, May 28, 2025 at 7:35 PM Mark Filipak <markfilipak.i...@gmail.com> wrote: > I did this: > > ffmpeg^ > -i g:\detelecine_input.mkv^ > -vf fieldmatch,decimate^ > -c:a aac^ > -c:v libx264^ > g:\fieldmatch_decimate_only_no_r.mkv > > I couldn't get the frame numbers burned into the pictures, so I counted > them as I single stepped. > > There were no dropped frames. There were no repeated frames. > _______________________________________________ > ffmpeg-user mailing list > ffmpeg-user@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". > _______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
