[mythtv] Ticket #9801: mythtranscode produces unusable output when transcoding mpeg4->mpeg4 with cutlists

[Michael T. Dean]

On 10/31/2011 04:37 PM, MythTV wrote:
> #9801: mythtranscode produces unusable output when transcoding mpeg4->mpeg4 with
> cutlists
>
> Comment (by bugfixed@…):
>
>   Well I found the bug and have a simple working fix -- but since the devs
>   persist on maintaining this is merely a duplicate of #8864 (which I can
>   assure everybody it is not) and since the devs seem to think the bug
>   itself is of low priority and not worthy of any attention, I assume that
>   these same devs are probably not interested in my fix. The bug by the way
>   is in the core libmythtv code.
>
>   I will be happy to share the bug fix when the devs stop acting so
>   defensively about their precious project and stop trying to hide and
>   minimize the presence and importance of bugs, but instead start acting
>   maturely and helpfully to help users (particularly those who are willing
>   and able to contribute) to resolve critical bug (especially those that
>   destroy recordings or break important existing functionality)
>


http://code.mythtv.org/trac/wiki/TicketHowTo

"If your ticket gets marked as '*worksforme*' or '*invalid*' consider 
this a challenge to improve the bug report. Problems often only occur 
with a particular setting, with some particular hardware or even with a 
specific recording. Figuring out what exactly is causing the problem 
will make it possible to reproduce the bug, which is the first step in 
fixing it. If the ticket is marked as invalid rather than worksforme, it 
probably failed some check on this checklist. Also, don't get into an 
argument with whoever closed your ticket. Remember, since this person 
reviewed your ticket, this is the person most likely to fix your problem."

In this case, the ticket was closed as a duplicate.  If it's not a 
duplicate, your challenge is to show us the difference (or, better, yet, 
fix both bugs).  Or, just submit your patch to #8864 and then when it's 
applied and #8864 isn't fixed, feel free to tell us.

An open, but ignored bug, does no more good than a closed bug.  It's up 
to someone who cares to fix this problem to present a valid argument to 
support the case that there is, in fact, a bug, and that the code needs 
changing (and that the change does less harm than good).  The easiest 
way to do this is to point out the actual bug and/or a proposed fix.

IMHO, we really have to stop this terrible approach we've been taking of 
"guilty-until-proven-innocent" where bugs are left open until someone 
can prove that there's no bug.  Instead, we should close bug reports 
that aren't going to be looked at/aren't understood/aren't helping/are 
simply providing a placebo for users who think someone else is going to 
take care of it, and hope users take up the challenge of improving the 
bug reports.

Mike