Remove sequentially duplicate frames when using FFmpeg
Is there any way to detect duplicate frames within the video using ffmpeg
?
I tried -vf
flag with select=gt(scene\,0.xxx)
for scene change. But, it did not work for my case.
Use the mpdecimate filter, whose purpose is to "Drop frames that do not differ greatly from the previous frame in order to reduce frame rate."
-
This will generate a console readout showing which frames the filter thinks are duplicates.
ffmpeg -i input.mp4 -vf mpdecimate -loglevel debug -f null -
-
To generate a video with the duplicates removed
ffmpeg -i input.mp4 -vf mpdecimate,setpts=N/FRAME_RATE/TB out.mp4
The setpts filter expression generates smooth timestamps for a video at FRAME_RATE
FPS. See an explanation for timestamps at What is video timescale, timebase, or timestamp in ffmpeg?
I also had this problem and Gyan's excellent answer above got me started but the result of it was desynchronized audio so I had to explore more options:
mpdecimate vs decimate filters
-
mpdecimate
is the standard recommendation I found all over SO and the internet, but I don't think it should be the first pick- it uses heuristics so it may and will skip some duplicate frames
- you can tweak the detection with
frac
parameter, but that's extra work you may want to avoid if you can - it is not really supposed to work with
mp4
container (source), but I was usingmkv
so this limitation didn't apply on my case, but good to be aware of it
-
decimate
removes frames precisely, but it is useful only for periodically occurring duplicates
detected vs actual frame rate
- so you have multimedia file with duplicate frames, it is good idea to make sure that the detected frame rate matches the actual one
-
ffprobe in.mkv
will output the detected FPS; it may look like thisStream #0:0: Video: h264 (Main), yuvj420p(pc, bt709, progressive), 1920x1080, SAR 1:1 DAR 16:9, 25 fps, 25 tbr, 1k tbn, 50 tbc (default)
the actual frame rate can be found out if you open the media
in.mkv
in a media player that lets you step one frame at the time; then count the steps needed to advance the playback time for 1 second, in my case it was 30 fps- not a big surprise for me, because every 6th frame was duplicate (5 good frames and 1 duplicate), so after 25 good frames there was also 5 duplicates
what is N/FRAME_RATE/TB
-
except the use of
FRAME_RATE
variable theN/FRAME_RATE/TB
is equal to the example below from ffmpeg documentation (source)Set fixed rate of 25 frames per second:
setpts=N/(25*TB)
-
the math behind it perfectly explained in What is video timescale, timebase, or timestamp in ffmpeg?
- it basically calculates timestamp for each frame and multiplies it with timebase
TB
to enhance precision
- it basically calculates timestamp for each frame and multiplies it with timebase
FRAME_RATE
variable vs literal FPS value (e.g. 25)
- this is why it is important to know your detected and actual FPS
- if the detected FPS matches your actual FPS (e.g. both are 30 fps) you can happily use
FRAME_RATE
variable inN/FRAME_RATE/TB
- but if the detected FPS differs than you have to calculate the
FRAME_RATE
on your own- in my case my actual FPS was 30 frames per second and I removed every 6th frame, so the target FPS is 25 which leads to
N/25/TB
- if I used
FRAME_RATE
(and I actually tried that) it would take the wrong detected fps of 25 frames i.e.FRAME_RATE=25
, run it throughmpdecimate
filter which would remove every 6th frame and it would update toFRAME_RATE=20.833
soN/FRAME_RATE/TB
would actually beN/20.833/TB
which is completely wrong
- if I used
- in my case my actual FPS was 30 frames per second and I removed every 6th frame, so the target FPS is 25 which leads to
to use or not to use setpts
- so the setpts filter already got pretty complicated especially because of the FPS mess that duplicate frames may create
- the good news is you actually may not need the setpts filter at all
-
here is what I used with good results
ffmpeg -i in.mkv -vf mpdecimate out.mkv
ffmpeg -i in.mkv -vf decimate=cycle=6,setpts=N/25/TB out.mkv
-
but the following gave me desynchronized audio
ffmpeg -i in.mkv -vf mpdecimate,setpts=N/FRAME_RATE/TB out.mkv
ffmpeg -i in.mkv -vf mpdecimate,setpts=N/25/TB out.mkv
ffmpeg -i in.mkv -vf decimate=cycle=6 out.mkv
-
as you see
- mpdecimate and decimate does not work the same way
- mpdecimate worked better for me without setpts filter
- while decimate needed setpts filter and furthermore I need to avoid
FRAME_RATE
variable and useN/25/TB
instead because the actual FPS was not detected properly
note on asetpts
- it does the same job as setpts does but for audio
- it didn't really fix desync audio for me but you want to use it something like this
-af asetpts=N/SAMPLE_RATE/TB
- maybe you are supposed to adjust the
SAMPLE_RATE
according to the ratio of duplicate frames removed, but it seems to me like extra unnecessary work especially when my video had the audio in sync at the beginning, so it is better to use commands that will keep it that way instead of fixing it later
tl;dr
If the usually recommended command ffmpeg -i in.mkv -vf mpdecimate,setpts=N/FRAME_RATE/TB out.mkv
does not work for you try this:
ffmpeg -i in.mkv -vf mpdecimate out.mkv
or
ffmpeg -i in.mkv -vf decimate=cycle=6,setpts=N/25/TB out.mkv
(cycle=6
because every 6th frame is duplicate and N/25/TB
because after removing the duplicates the video will have 25 fps (avoid the FRAME_RATE
variable); adjust for your use case)
I tried the solution here and none of them seem to work when you need to trim the video and keep the audio. There is a mpdecimate_trim repo that does a good job. It basically list all the frames to be dropped (using mpdecimate
) and then creates a complex filter to trim all those frames (and the corresponding audio) from the video by splitting the video and only including the portion without duplicate frames.
I did have to tweak a few options in the code though. For instance, in mpdecimate_trim.py
, I had to change this line:
dframes2 = get_dframes(ffmpeg(True, "-vf", "mpdecimate=hi=576", "-loglevel", "debug", "-f", "null", "-").stderr)
I had to detect duplicates a bit more aggressively, so I changed the mpdecimate
option to mpdecimate=hi=64*32:lo=64*24:frac=0.05