[FFmpeg-user] I found the bugs

[Carl Zwanzig]

On 6/12/2024 2:44 PM, Mark Filipak wrote:
> 
> I need someone more knowledgeable about FFmpeg to triage. 

They're often called 'developers'.

> For example, 
> Perhaps the sequence header has some information that conflicts with my 
> cuts (the way cutting out a lone open B-frame turns an ending open GOP 
> into a closed GOP but there's no way to set the 'closed_gop' MPEG tag to 
> '1').

That's not how bug reporting works in any place I've worked. _You_ file 
the bug with all the info you have. The person it's assigned to, or the 
person who takes it, investigates to see what's really happening (and 
maybe asks follow-up questions). Maybe there's an open/closed GOP thing 
that only happens when there's an 'X' in the file name and the moon is 
full..... fine, is it reproducible and interesting enough for someone to 
analyze and look for the error?

It's also possible that things are working as designed and the developer 
response will say that.

The other option is just sitting on the info and if there really is a 
problem allowing it to not be fixed.

Your choice.

z!
who once found a bug in borland libc mktime() that occurred when 
tm_mon=2 and tm_mday=29 but only on an actual leap year