[FFmpeg-trac] #11122(ffmpeg:new): -force_key_frames source causes pkt->flags to have AV_PKT_FLAG_KEY set incorrectly

[FFmpeg]

#11122: -force_key_frames source causes pkt->flags to have AV_PKT_FLAG_KEY set
incorrectly
----------------------------------------+----------------------------------
             Reporter:  David Johansen  |                     Type:  defect
               Status:  new             |                 Priority:  normal
            Component:  ffmpeg          |                  Version:  7.0
             Keywords:                  |               Blocked By:
             Blocking:                  |  Reproduced by developer:  0
Analyzed by developer:  0               |
----------------------------------------+----------------------------------
 Summary of the bug:
 How to reproduce:
 {{{
 % ffmpeg -i test.mp4 -c:v libx264 -force_key_frames source -f dash
 video.xml
 ffmpeg version n7.0.1-42-g67eec16150 Copyright (c) 2000-2024 the FFmpeg
 developers
 built with gcc 12 (Debian 12.2.0-14)
 configuration: --disable-shared --enable-static --enable-debug --disable-
 doc --disable-ffplay --enable-gpl --enable-libfdk_aac --enable-libx264
 --enable-libx265 --enable-librsvg --enable-openssl --enable-nonfree
 --extra-libs=-lpthread
 libavutil      59.  8.100 / 59.  8.100
 libavcodec     61.  3.100 / 61.  3.100
 libavformat    61.  1.100 / 61.  1.100
 libavdevice    61.  1.100 / 61.  1.100
 libavfilter    10.  1.100 / 10.  1.100
 libswscale      8.  1.100 /  8.  1.100
 libswresample   5.  1.100 /  5.  1.100
 libpostproc    58.  1.100 / 58.  1.100
 }}}

 Setting `-force_key_frames source` causes `pkt->flags` to have
 `AV_PKT_FLAG_KEY` set incorrectly on the 3rd frame even though it
 shouldn't be set. I've checked the reading of the data and `pkt->flags` is
 correct, then then it's being set on the 3rd frame even though that was
 not the case on the input
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/11122>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker