Opened 14 years ago

Closed 12 years ago

#3246 closed defect (fixed)

mythtranscode --mpeg2 fails: expectedPTS != expectedDTS+ptsIncrement

Reported by: anonymous Owned by: skamithi
Priority: minor Milestone: unknown
Component: MythTV - Mythtranscode Version: 0.20
Severity: medium Keywords: mythtranscode lossless expectedPTS expectedDTS ptsIncrement
Cc: Ticket locked: no


version: mythtv-0.20_svn13053

mythtranscode mpeg2<->mpeg2 is failing on a specific recording. I ran mythtranscode by hand on the recordingfile and got the following error message:

$ mythtranscode --infile 1051_20070319070000.mpg --outfile 1051_20070319070000.mpg.tmp --mpeg2 2007-03-22 12:58:56.244 Using runtime prefix = /usr 2007-03-22 12:58:56.479 New DB connection, total: 1 2007-03-22 12:58:56.506 Enabled verbose msgs: important 2007-03-22 12:58:56.552 New DB connection, total: 2 Mux rate: 66.45 Mbit/s 2007-03-22 12:59:02.462 Frame 6 > 2. Corruption likely at pos: 238137532 2007-03-22 12:59:30.422 Frame 12 > 8. Corruption likely at pos: 1232901932 [snip] 2007-03-22 13:04:16.908 Frame 12 > 8. Corruption likely at pos: 11583348904 2007-03-22 13:04:17.199 expectedPTS != expectedDTS+ptsIncrement $

I found a thread ( in mythtv-users where others have been complaining about the problem, but no indication that a bug report was filed. I also searched for existing bugs and found none with this description.

Attachments (1)

expected_dts.diff (560 bytes) - added by skamithi 14 years ago.
this patch works for me. as others have reported only breaks when honoring cutlists.

Download all attachments as: .zip

Change History (15)

comment:1 Changed 14 years ago by jharvell@…

Sorry the last post was anonymous. It was me.

comment:2 Changed 14 years ago by Geoffrey Hausheer

Owner: changed from Isaac Richards to Geoffrey Hausheer

comment:3 Changed 14 years ago by Geoffrey Hausheer

Can you ocnfirm that this recording is over 11GB in size? That seems awfully large even for HD material.

In any case, try something like: dd if=1051_20070319070000.mpg of=tmp.mpg bs=1024 count=20000 seek=11575000 which should give you a 20MB file then rerun:

mythtranscode --infile tmp.mpg --outfile 1051_20070319070000.mpg.tmp --mpeg2

and see if it fails. you can play around with different combinations of seek and count to try to get something that mythtranscode will crash on. If you can get the size smaller than 20MB, you can send me the sample, and I can try to debug, but otherwise, it's not something that can be easily debugged with logs on such a large file.

comment:4 Changed 14 years ago by paulh

Component: mythtvmythtranscode

Changed 14 years ago by skamithi

Attachment: expected_dts.diff added

this patch works for me. as others have reported only breaks when honoring cutlists.

comment:5 Changed 14 years ago by skamithi

attached patch fixes issues with me. transcoded 9 files thereafter that previously failed and all seem fine now. problem only occurs when honoring cutlists.

comment:6 Changed 13 years ago by mitchell2345

I am seeing this exact same issue with atrpms-bleeding packages r15447.

Should this problem been fixed and committed so it shows up in these packages?

Thanks, Mitchell

comment:7 Changed 13 years ago by stuartm

Milestone: unknown0.21
Owner: changed from Geoffrey Hausheer to skamithi
Status: newassigned

comment:8 Changed 13 years ago by Shane Shrybman <gnome42@…>

(Just some extra info that _might_ be pertinent)

I have seen a similar error in the past. It was fixed by [14443] #3416, which was applied in September 2007. So, if the recording was made during the interval before that when this bug existed in trunk it could be the source of the problem.

comment:9 Changed 13 years ago by skamithi

(In [15752]) Refs #3246. commit patch that fixes the problem for me. problem is crash of mythtranscode when transcoding recordings with cutlists

comment:10 Changed 13 years ago by mitchel2345

some of my recordings to work with r15741 but other fail. Sometime the cutlist works other time it fails. Same behavior for ffmpeg.

I wish i new how to fix stuff like this :(


comment:11 Changed 13 years ago by skamithi

Milestone: 0.21unknown

comment:12 Changed 12 years ago by dekarl@…

skamithi, I (with googles help) couldn't find any mention of this bug past [15752], can this ticket be closed?

comment:13 Changed 12 years ago by stuartm

Component: mythtranscodeMythTV - Mythtranscode

comment:14 Changed 12 years ago by robertm

Resolution: fixed
Status: assignedclosed

It appears this should have been closed some time ago. Anyone still experiencing this with .22 can open a new ticket.

Note: See TracTickets for help on using tickets.