[FFmpeg-trac] #3475(ffprobe:closed): -skip_frame nokey doesn't work with ffprobe

[FFmpeg]

#3475: -skip_frame nokey doesn't work with ffprobe
------------------------------------+--------------------------------------
             Reporter:  duggaraju   |                    Owner:
                 Type:  defect      |                   Status:  closed
             Priority:  normal      |                Component:  ffprobe
              Version:  git-master  |               Resolution:  worksforme
             Keywords:  skip_frame  |               Blocked By:
             Blocking:              |  Reproduced by developer:  0
Analyzed by developer:  0           |
------------------------------------+--------------------------------------
Changes (by cehoyos):

 * keywords:  ffprobe show_frame => skip_frame
 * status:  new => closed
 * resolution:   => worksforme


Old description:

> Summary of the bug:
> How to reproduce:
> {{{
> % ffprobe -skip_frame nokey -select_streams v -show_frames -i input.mp4
>  ... output
> ffprobe version N-60386-g9c978f2 Copyright (c) 2007-2014 the FFmpeg
> developers
>   built on Feb  5 2014 22:08:32 with gcc 4.8.2 (GCC)
> [FRAME]
> media_type=video
> key_frame=1
> pkt_pts=1000
> pkt_pts_time=0.040000
> pkt_dts=1000
> pkt_dts_time=0.040000
> best_effort_timestamp=1000
> best_effort_timestamp_time=0.040000
> pkt_duration=1000
> pkt_duration_time=0.040000
> pkt_pos=1191176
> pkt_size=3327
> width=1920
> height=1080
> pix_fmt=yuv420p
> sample_aspect_ratio=1:1
> pict_type=I
> coded_picture_number=0
> display_picture_number=0
> interlaced_frame=0
> top_field_first=0
> repeat_pict=0
> [/FRAME]
> [FRAME]
> media_type=video
> key_frame=0
> pkt_pts=2000
> pkt_pts_time=0.080000
> pkt_dts=2000
> pkt_dts_time=0.080000
> best_effort_timestamp=2000
> best_effort_timestamp_time=0.080000
> pkt_duration=1000
> pkt_duration_time=0.040000
> pkt_pos=1194771
> pkt_size=268
> width=1920
> height=1080
> pix_fmt=yuv420p
> sample_aspect_ratio=1:1
> pict_type=B
> coded_picture_number=2
> display_picture_number=0
> interlaced_frame=0
> top_field_first=0
> repeat_pict=0
> [/FRAME]
> [FRAME]
>
> As per ticket #1859 https://trac.ffmpeg.org/ticket/1859 this is supposed
> to be fixed. But I can repro it easily with the
> latest build. Is this a bug or am I doing something wrong?
>
> }}}
> I expect the output to only show the key frames information but instead
> it shows all the

New description:

 Summary of the bug:
 How to reproduce:
 {{{
 % ffprobe -skip_frame nokey -select_streams v -show_frames -i input.mp4
  ... output
 ffprobe version N-60386-g9c978f2 Copyright (c) 2007-2014 the FFmpeg
 developers
   built on Feb  5 2014 22:08:32 with gcc 4.8.2 (GCC)
 [FRAME]
 media_type=video
 key_frame=1
 pkt_pts=1000
 pkt_pts_time=0.040000
 pkt_dts=1000
 pkt_dts_time=0.040000
 best_effort_timestamp=1000
 best_effort_timestamp_time=0.040000
 pkt_duration=1000
 pkt_duration_time=0.040000
 pkt_pos=1191176
 pkt_size=3327
 width=1920
 height=1080
 pix_fmt=yuv420p
 sample_aspect_ratio=1:1
 pict_type=I
 coded_picture_number=0
 display_picture_number=0
 interlaced_frame=0
 top_field_first=0
 repeat_pict=0
 [/FRAME]
 [FRAME]
 media_type=video
 key_frame=0
 pkt_pts=2000
 pkt_pts_time=0.080000
 pkt_dts=2000
 pkt_dts_time=0.080000
 best_effort_timestamp=2000
 best_effort_timestamp_time=0.080000
 pkt_duration=1000
 pkt_duration_time=0.040000
 pkt_pos=1194771
 pkt_size=268
 width=1920
 height=1080
 pix_fmt=yuv420p
 sample_aspect_ratio=1:1
 pict_type=B
 coded_picture_number=2
 display_picture_number=0
 interlaced_frame=0
 top_field_first=0
 repeat_pict=0
 [/FRAME]
 [FRAME]
 }}}

 As per ticket #1859 this is supposed to be fixed. But I can repro it
 easily with the
 latest build. Is this a bug or am I doing something wrong?

 I expect the output to only show the key frames information but instead it
 shows all the

--

Comment:

 I tested the following:
 {{{
 $ ffprobe -select_streams v -show_frames fate-
 suite/svq3/Vertical400kbit.sorenson3.mov >test
 $ ffprobe -skip_frame nokey -select_streams v -show_frames fate-
 suite/svq3/Vertical400kbit.sorenson3.mov >test2
 }}}
 The output file {{{test2}}} is much smaller than the file {{{test}}} and
 its creation takes significantly less time.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/3475#comment:1>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker