[FFmpeg-trac] #11192(avformat:new): Raw H264 stream has incorrect frame rate

[FFmpeg]

#11192: Raw H264 stream has incorrect frame rate
------------------------------------+------------------------------------
             Reporter:  ariley      |                    Owner:  (none)
                 Type:  defect      |                   Status:  new
             Priority:  important   |                Component:  avformat
              Version:  git-master  |               Resolution:
             Keywords:              |               Blocked By:
             Blocking:              |  Reproduced by developer:  0
Analyzed by developer:  0           |
------------------------------------+------------------------------------
Comment (by ariley):

 Not quite sure how you can make the assertion that I didn't test master?
 {{{
 $ git branch
 * master
 $ ./ffprobe regression_ba4b73c977.h264
 ffprobe version N-117011-gbb91425eb8 Copyright (c) 2007-2024 the FFmpeg
 developers
   built with gcc 12 (Debian 12.2.0-14)
   configuration: --extra-cflags=-g --extra-cxxflags=-g --optflags=-O0
   libavutil      59. 36.100 / 59. 36.100
   libavcodec     61. 13.100 / 61. 13.100
   libavformat    61.  5.101 / 61.  5.101
   libavdevice    61.  2.101 / 61.  2.101
   libavfilter    10.  2.102 / 10.  2.102
   libswscale      8.  2.100 /  8.  2.100
   libswresample   5.  2.100 /  5.  2.100
 [h264 @ 0x555f4b2ef640] Stream #0: not enough frames to estimate rate;
 consider increasing probesize
 Input #0, h264, from 'regression_ba4b73c977.h264':
   Duration: N/A, bitrate: N/A
   Stream #0:0: Video: h264 (High 4:2:2), yuv422p10le(tv, bt709, top
 first), 1920x1080 [SAR 1:1 DAR 16:9], 25 fps, 59.94 tbr, 1200k tbn
 $ git log --pretty=oneline | perl -pe'exit if (/ba4b73c977/)' | wc -l
 6749
 }}}
 The results in my initial report are from doing a git-bisect on the master
 branch.  It may be 6750 commits back in history, but I'm pretty sure I'm
 still on the master branch.

 If this is a known bug, then I'm happy to have it closed as a duplicate,
 but I wasn't able to find any mention of it in trac -- perhaps I'm not
 using the correct search terms.
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/11192#comment:2>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker