[FFmpeg-user] ffprobe bug in 'interlaced_frame'?

[Mark Filipak]

Thank you, Carl. I'm repeating my submittal in order to keep this thread 
intact. My responses are interposed at the bottom...

For soft telecined videos, all frames have
'progressive_frame' = 1
(source: T-REC-H.262-201202-I, confirmed via VOBEdit).
However, the frames that ffprobe marks 'repeat_pict' = 0 have
'interlaced_frame' = 1.

Assumptions:
1, ffprobe's 'interlaced_frame' is the inverse of MPEG2's 
'progressive_frame', and
2, ffprobe's 'repeat_pict' is identical to MPEG2's 'repeat_first_field', and
3, ffprobe's quirks are also ffmpeg's quirks, so this problem applies 
also to ffmpeg.

If my assumptions are incorrect,
1, What is the correct meaning of ffmpeg's 'interlaced_frame'?
2, What is the correct meaning of ffmpeg's 'repeat_pict'?

Question: Why doesn't ffmpeg use the same metadata names & meanings that 
are found in the H.262 specification?

Question: Is there a way to get ffprobe to output the actual metadata?

Windows command used:
ffprobe -i %1 -select_streams v:0 -show_frames -of flat -sexagesimal | 
FINDSTR /L "key_frame=1 top_field_first repeat_pict interlaced_frame"

Thanks for the help,
Mark.


On 01/26/2020 03:03 PM, Carl Eugen Hoyos wrote:
> Am So., 26. Jan. 2020 um 20:51 Uhr schrieb Mark Filipak
> <markfilipak.windows+ffmpeg at gmail.com>:
>>
>> For soft telecined videos, all frames have
>> 'progressive_frame' = 1
> 
> I may miss something but since FFmpeg does not "support" soft-telecine
> why should there be an interlaced frame?

Yes, ffmpeg does not make soft telecined streams. However, the soft 
telecined videos are inputs, not outputs.

> In general, please provide command line including complete, uncut
> console output when asking questions here.

I provided the command line:
ffprobe -i %1 -select_streams v:0 -show_frames -of flat -sexagesimal | 
FINDSTR /L "key_frame=1 top_field_first repeat_pict interlaced_frame"

The console output is very, very long because it outputs all frames.
However, I assume you want to see the versions I'm using. Here they are:

ffprobe version N-94664-g0821bc4eee Copyright (c) 2007-2019 the FFmpeg 
developers
   built with gcc 9.1.1 (GCC) 20190807
   configuration: --enable-gpl --enable-version3 --enable-sdl2 
--enable-fontconfig --enable-gnutls --enable-iconv --enable-libass 
--enable-libdav1d --enable-libbluray --enable-libfreetype 
--enable-libmp3lame --enable-libopencore-amrnb 
--enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus 
--enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora 
--enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp 
--enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg 
--enable-lzma --enable-zlib --enable-gmp --enable-libvidstab 
--enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa 
--enable-libspeex --enable-libxvid --enable-libaom --enable-libmfx 
--enable-amf --enable-ffnvcodec --enable-cuvid --enable-d3d11va 
--enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth 
--enable-libopenmpt
   libavutil      56. 33.100 / 56. 33.100
   libavcodec     58. 55.101 / 58. 55.101
   libavformat    58. 31.104 / 58. 31.104
   libavdevice    58.  9.100 / 58.  9.100
   libavfilter     7. 58.101 /  7. 58.101
   libswscale      5.  6.100 /  5.  6.100
   libswresample   3.  6.100 /  3.  6.100
   libpostproc    55.  6.100 / 55.  6.100

Thank you for your assistance -- Mark.
> Carl Eugen