29.09.2021, 05:38
A source clip can have flags regarding whether they are interlaced or not, but like the normal interlaced info it often is not reliable.
If you call you get data like:
Some deinterlacers use these,...
Problem is that just because a frame is interlaced, doesn't mean it shows combing. Sometimes progressive input is encoded with an interlaced flag or telecined contend it flagged as progressive or vise versa.
Cu Selur
If you call
ffprobe -i "<path to input>" -show_frames
[FRAME]
media_type=video
stream_index=0
key_frame=0
pts=149673
pts_time=1.663033
pkt_dts=151473
pkt_dts_time=1.683033
best_effort_timestamp=149673
best_effort_timestamp_time=1.663033
pkt_duration=1800
pkt_duration_time=0.020000
pkt_pos=532604
pkt_size=87443
width=1920
height=1080
pix_fmt=yuv420p
sample_aspect_ratio=1:1
pict_type=P
coded_picture_number=5
display_picture_number=0
interlaced_frame=1
top_field_first=1
repeat_pict=0
color_range=tv
color_space=bt709
color_primaries=bt709
color_transfer=bt709
chroma_location=left
[/FRAME]
Problem is that just because a frame is interlaced, doesn't mean it shows combing. Sometimes progressive input is encoded with an interlaced flag or telecined contend it flagged as progressive or vise versa.
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.