Changes between Initial Version and Version 3 of Ticket #9801


Ignore:
Timestamp:
May 24, 2011, 11:57:36 PM (10 years ago)
Author:
robertm
Comment:

Removing opinion/unsolicited development advice.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #9801

    • Property Priority changed from critical to minor
    • Property Component changed from MythTV - General to MythTV - Mythtranscode
    • Property Severity changed from high to medium
    • Property Summary changed from mythtranscode TRASHES recordings when transcoding mpeg4->mpeg4 with cutlists to mythtranscode produces unusable output when transcoding mpeg4->mpeg4 with cutlists
  • Ticket #9801 – Description

    initial v3  
    4242     http://pastebin.com/5F9qPR3i
    4343
    44 NOTE: I rate this as a CRITICAL PRIORITY/HIGH SEVERITY bug since it will totally TRASH your valuable recordings without any warnings or error messages when run from mythfrontend. Mythfrontend sees the transcoding as completing successfully so it overwrites and destroys the original.
    45 
    46 Again this used to work certainly back in 0.23 days.
    47 By the way this is the second CRITICAL DESTRUCTIVE bug in mythtranscode that was introduced in the transition from 0.23 to 0.24. Both this current bug and the recently fixed audio bug IRREVERSIBLY DESTROYED recordings.
    48 
    49 With all due respect to the volunteer nature of the developers, I would suggest that either mythtranscode be removed from the distribution or that more attention be paid to testing it before releasing a new mythtv version. The surest way to turn off new (or old) users of mythtv is to introduce major bugs into supposedly stable releases that break existing functionality and destroy valuable recordings. Again this is meant with all due respect and appreciation to the developer team