Lossless Transcode Corrupting Recordings

[Scott Harris <snharris99@…>]

I have had 3 or 4 occasions over the last 2-3 weeks where a lossless tanscode after creating a commercial cutlist has rendered the recordings entirely unusable.

• Transcode runs for 3 - 4 hours instead of the usual 20 - 30 minutes.
• Size is 5x normal, where the resulting file would normally be about 4GB, it's 20GB on the corrupted file.
• Reported time is 2x normal where the resulting file would normally be about 40 mins, it reports as 1:20 on the corrupted file.
• Audio is missing.
• Video is extremely interlaced and pixelated.

The backend logs show (taken from the last recording to be corrupted)....

2011-10-25 06:46:16.171 Warning: partial frame found!

2011-10-25 06:46:16.188 #0 PTS:03:51:04.030 Delta: 0.0ms queue: 1

2011-10-25 06:46:16.490 Inserting 1 I-Frames after #2

2011-10-25 06:46:16.585 WARNING - Unsupported FPS change from 59.96 to 29.97

2011-10-25 06:46:16.973 Inserting 1 I-Frames after #14

2011-10-25 06:46:16.983 WARNING - Unsupported FPS change from 59.96 to 29.97

2011-10-25 06:46:17.086 Inserting 2 I-Frames after #2

QString::arg: Argument missing: "Frame 9 > 8. Corruption likely at pos: 8" , 2915128

2011-10-25 06:46:17.126 Frame 9 > 8. Corruption likely at pos: 8

2011-10-25 06:46:17.188 Inserting 2 I-Frames after #8

2011-10-25 06:46:17.391 Inserting 2 I-Frames after #14

QString::arg: Argument missing: "Frame 21 > 20. Corruption likely at pos: 20" , 3260296

2011-10-25 06:46:17.434 Frame 21 > 20. Corruption likely at pos: 20

2011-10-25 06:46:17.499 Inserting 2 I-Frames after #20

2011-10-25 06:46:17.834 Inserting 2 I-Frames after #26

With the last 2 messages (9>8 and 21>20) just being repeated over and over again with only the ", 3260296" part changing.

The original recordings seemed fine. However, perhaps if the file had that many issues, that perhaps that transcode should fail instead of ruining the recording?

[beirdo]

Please upgrade to a newer version (like 0.25-fixes). That entire section has been rewritten to get rid of Qt3 structures, and no more support will be given on the old code.

[Raymond Wagner]

I'm going to close this one, as it's likely this has been fixed unintentionally at some point in the last two years. Please re-open it if the problem is still happening.