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

[FFmpeg]

#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 markfilipak):

 Replying to [comment:25 pdr0]:
 > Replying to [comment:20 markfilipak]:
 > > Replying to [comment:14 pdr0]:
 > > > Ticket_11080.m2ts is the same problem as ticket #11055 - not a valid
 stream
 > > >
 > > > Not cut/appended on IDR boundaries, no IDR pictures , decreasing
 frame_num and decreasing POC violations in coded stream order
 > > >
 > > > eg.
 > > > Notice frame_num drops from 243 to 191
 > >
 > > The clip has only 97 frames.
 > >
 > > Notice that frame_num applies to slices. Notice that H.264 says what
 to do with frame_num, but it never defines "frame_num".
 >
 > Yes, if you look at the parser ...

 You have a parser for MPEG2TS? Actual physical bits would help me to see
 what you're writing about. I write that because it seems to me you (or
 MPEG) are mixing stream frames, which have only timestamps and not frame
 numbers, with something that goes by frame numbers. I suspect they're
 actually frame offsets, not frame numbers. I suspect they're used for
 transforming slices between reference slices in other frames as opposed to
 transforming while frames. I suspect this has something to do with POC,
 which I find to be 'prescribed' rather than 'described', and so, seems
 rather vague and subject to interpretation.

 Two things:

 1 - If you have a parser for MPEG2TS, what is it? How do I get it? I can
 parse TS (as in MOV files) but not MPEG2TS.

 2 - I have a proposal: Since this is going beyond a bug report and the
 time you are putting in is growing, how about I pay you? Money for
 instruction. That would only be fair to you and I'm willing to do it. If
 such instruction does reveal an actual bug, wonderful. If it doesn't
 that's fine too.
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/11080#comment:32>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker