[FFmpeg-trac] #7702(undetermined:new): Incorrect video frame reporting

FFmpeg trac at avcodec.org
Mon Jan 28 06:24:33 EET 2019


#7702: Incorrect video  frame reporting
-------------------------------------+-------------------------------------
             Reporter:  budman1      |                    Owner:
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:
              Version:  unspecified  |  undetermined
             Keywords:               |               Resolution:
             Blocking:               |               Blocked By:
Analyzed by developer:  0            |  Reproduced by developer:  0
-------------------------------------+-------------------------------------

Comment (by budman1):

 You are kidding right? I succeeded in creating a segment that has frame 0
 dts/pts timecode of 0.000000 for better merging. Players play segment
 starting with frame 0 (1850).  You cannot extract frame 0 (1850/1851)
 because ffprobe displays the first frame as being crystal clear, complete
 frame, audio in sync 'B' frame.

 Bug is: Players view frame 0/1 (1850/1851) so they are included. ffmpeg
 cannot extract those frames because according to ffprobe they do not
 exist!

 One more item: 25 FPS and 29.97 FPS work correctly.  30 FPS does not.

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


More information about the FFmpeg-trac mailing list