[FFmpeg-user] I found the bugs

[Mark Filipak]

MasterQuestionable has downgraded the timestamp bug from 'important' to 'normal'. I'm copying my 
response here because trac is in a different account and that account's email-'cc's are rejected by 
ffmpeg-user. --Mark.

https://trac.ffmpeg.org/ticket/11055
https://streams.videolan.org/ffmpeg/incoming/11055/Ticket_11055.m2ts

On 18/06/2024 20.51, FFmpeg wrote:
-snip header-
 > Changes (by MasterQuestionable):
 >
 >   * priority:  important => normal
 >
 > Comment:
 >
 >   ͏    Normalize priority.
 >   ͏    I think this only influences not very much cases, mostly coined:
 >   ͏    That only involves illy-produced videos.
 >
 >   ͏    Doesn't merit high priority as one that could wreak general havoc.

Please find something wrong with Ticket_11055.m2ts. I'd dearly like to know what it is. If it is 
"illy-produced", show how is it "illy-produced". When "I think" becomes "We show", then I will 
believe it.

I think this may be a far ranging bug that affects '-ss' and that provokes many of the 
"non-monotonous DTS" error messages that seem to appear out of nowhere when a trivial, non-timing, 
non-timestamp change is made to a transcode or to a remux. I confess that I write "I think" rather 
than "We think" because I've not yet gotten others on ffmpeg-user to look at Ticket_11055.m2ts and 
to take this issue seriously enough to join me. Certainly, no one else on ffmpeg-user has 
communicated that they've tested (or even watched) Ticket_11055.m2ts.

This bug clearly wrecks '-vf showinfo' and '-show_frames' and makes them useless.

According to an examination of the actual packets, only '-f framecrc' reports correctly.

Please do not downgrade this bug without actual proof that is "illy-produced".