[FFmpeg-trac] #11080(undetermined:new): FFmpeg timestamps do not consistently agree with packet timestamps

FFmpeg trac at avcodec.org
Tue Jul 2 17:08:03 EEST 2024


#11080: FFmpeg timestamps do not consistently agree with packet timestamps
-------------------------------------+-------------------------------------
             Reporter:  markfilipak  |                    Owner:  (none)
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:
                                     |  undetermined
              Version:  unspecified  |               Resolution:
             Keywords:               |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
Comment (by pdr0):

 Replying to [comment:18 markfilipak]:
 > Replying to [comment:13 Balling]:
 > > ... Well, and also this again starts with non-IDR I frame.
 >
 > I'm making the start frame (i.e., the I-frame) IDR. How can it be
 otherwise? It's the first frame!



 You cannot change the slice/frame type without re-encoding .

 If it was IDR to begin with, frame_num would be "0".  The first slice has
 a frame_num of 227 - hence it's a non-IDR slice. That alone makes it a non
 valid codec video sequence as per the ITU h.264 specs

 G.3.18
 "The first picture of each coded video sequence in decoding order is an
 IDR picture."

 7.4.3
 "The value of frame_num is constrained as follows:
 – If the current picture is an IDR picture, frame_num shall be equal to
 0."
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/11080#comment:23>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list