Opened 17 years ago
Closed 14 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 |
Description
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 (http://www.gossamer-threads.com/lists/mythtv/users/247655?do=post_view_threaded) 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)
Change History (15)
comment:1 Changed 17 years ago by
comment:2 Changed 17 years ago by
Owner: | changed from Isaac Richards to Geoffrey Hausheer |
---|
comment:3 Changed 17 years ago by
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 17 years ago by
Component: | mythtv → mythtranscode |
---|
Changed 16 years ago by
Attachment: | expected_dts.diff added |
---|
this patch works for me. as others have reported only breaks when honoring cutlists.
comment:5 Changed 16 years ago by
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 16 years ago by
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 16 years ago by
Milestone: | unknown → 0.21 |
---|---|
Owner: | changed from Geoffrey Hausheer to skamithi |
Status: | new → assigned |
comment:8 Changed 16 years ago by
comment:9 Changed 16 years ago by
comment:10 Changed 16 years ago by
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 :(
Mitchell
comment:11 Changed 16 years ago by
Milestone: | 0.21 → unknown |
---|
comment:12 Changed 15 years ago by
skamithi, I (with googles help) couldn't find any mention of this bug past [15752], can this ticket be closed?
comment:13 Changed 14 years ago by
Component: | mythtranscode → MythTV - Mythtranscode |
---|
comment:14 Changed 14 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
It appears this should have been closed some time ago. Anyone still experiencing this with .22 can open a new ticket.
Sorry the last post was anonymous. It was me.