[mythtv-commits] Ticket #7978: Programme duration about 80% of actual duration for new recordings.

MythTV mythtv at cvs.mythtv.org
Sat Feb 6 17:11:24 UTC 2010


#7978: Programme duration about 80% of actual duration for new recordings.
---------------------------------------------+------------------------------
 Reporter:  Ian Macdonald <ian@…>            |       Owner:  ijr       
     Type:  defect                           |      Status:  new       
 Priority:  major                            |   Milestone:  0.22      
Component:  MythTV - General                 |     Version:  0.22-fixes
 Severity:  medium                           |     Mlocked:  0         
---------------------------------------------+------------------------------

Comment(by rkdart@…):

 I have what I think is the same problem as well.  I'm using Fedora 11 with
 the ATRPMS packages on a single master backend and Fedora 12 with RPM
 Fusion mythfrontend packages as well as some Mythbuntu boxes with their
 version of the frontend.  Seems like it might be a problem with the
 recordings themselves somehow, or at least the way the frontend is parsing
 them.  The recordings that are having problems all seem to be from the
 last week (since Jan. 31).

 As examples, I have one recording that was extremely short in reported
 duration (about 5 minutes on a 30 minute recording), and one that was too
 long by about 4-5 minutes (on a 30 minute recording).  Both the Fedora and
 Mythbuntu frontends have the exact same seeking problems.  Looking at most
 of my newer recorded programs, the reported times vary from about 15% to
 700%+ of the correct times.

 For the two examples mentioned above, the one that is reporting longer
 than actual was recorded on a Hauppage PVR-250, and the one reporting
 shorter than actual was recorded using a Pinnacle PCTV HD 800i (it was a
 HD program recorded OTA, and was sandwiched between two other shows with
 the same resolution on the same channel, both of which reported
 correctly).  I also ran the '''optimize_mythdb.pl''' script and that
 didn't fix anything for me.

 [[BR]][[BR]]

 Here's what I think is the relevant log snippet from the first (reported
 longer than actual -- 36m43s reported but actual seems to be 31m46s)
 recording:

 {{{
 2010-02-06 10:13:01.392 AFD: Recording has no position -- using
 libavformat seeking.
 2010-02-06 10:13:01.392 Input #0, mpeg, from
 'myth://192.168.10.4:6543/3061_20100204223000.mpg':
 2010-02-06 10:13:01.392   Duration: 00:36:43.01, start: 0.189278, bitrate:
 4516 kb/s
 2010-02-06 10:13:01.392     Stream #0.0[0x1e0]: Video: mpeg2video,
 yuv420p, 720x480 [PAR 8:9 DAR 4:3], 1001/60000, 6000 kb/s, 29.97 tbr, 90k
 tbn, 59.94 tbc
 }}}

 And here's what '''ffmpeg -i 3061_20100204223000.mpg''' says about the
 same recording (note that it displays the correct duration):

 {{{
 Seems stream 0 codec frame rate differs from container frame rate: 59.94
 (60000/1001) -> 29.97 (30000/1001)
 Input #0, mpeg, from '3061_20100204223000.mpg':
   Duration: 00:31:46.11, start: 0.189278, bitrate: 5219 kb/s
     Stream #0.0[0x1e0]: Video: mpeg2video, yuv420p, 720x480 [PAR 8:9 DAR
 4:3], 6000 kb/s, 29.97 tbr, 90k tbn, 59.94 tbc
     Stream #0.1[0x1c0]: Audio: mp2, 48000 Hz, 2 channels, s16, 384 kb/s
 }}}

 [[BR]][[BR]]

 Here is the log from the second recording (HD OTA) that's reported much
 shorter than actual (it reports a correct duration here but shows up as
 5:34 on the OSD popup, and does not allow me to seek past 5:34 at all):

 {{{
 2010-02-06 10:42:41.568 Input #0, mpegts, from
 'myth://192.168.10.4:6543/2251_20100131210000.mpg':
 2010-02-06 10:42:41.568 MythSocket(15ede50:33):
 writeBlock(0x140231094289624, 58)
 2010-02-06 10:42:41.568   Duration: 00:29:58.66, start: 41395.903622,
 bitrate: 13898 kb/s
 2010-02-06 10:42:41.569     Stream #0.0[0x31]: Video: mpeg2video, yuv420p,
 1280x720 [PAR 1:1 DAR 16:9], 1001/120000, 19000 kb/s, 59.94 tbr, 90k tbn,
 119.88 tbc
 2010-02-06 10:42:41.569     Stream #0.1[0x34]: Audio: ac3, 48000 Hz,
 stereo, s16, 384 kb/s
 2010-02-06 10:42:41.569     Stream #0.2[0x35]: Audio: ac3, 48000 Hz,
 stereo, s16, 384 kb/s
 2010-02-06 10:42:41.569 AFD: Position map found
 2010-02-06 10:42:41.569 AFD: Successfully opened decoder for file:
 "myth://192.168.10.4:6543/2251_20100131210000.mpg". novideo(0)
 }}}

 Here's from '''ffmpeg -i 2251_20100131210000.mpg'''

 {{{
 Seems stream 0 codec frame rate differs from container frame rate: 119.88
 (120000/1001) -> 59.94 (60000/1001)
 Input #0, mpegts, from '2251_20100131210000.mpg':
   Duration: 00:29:58.66, start: 41395.903622, bitrate: 13898 kb/s
   Program 1
     Stream #0.0[0x31]: Video: mpeg2video, yuv420p, 1280x720 [PAR 1:1 DAR
 16:9], 19000 kb/s, 59.94 tbr, 90k tbn, 119.88 tbc
     Stream #0.1[0x34](eng): Audio: ac3, 48000 Hz, stereo, s16, 384 kb/s
     Stream #0.2[0x35](eng): Audio: ac3, 48000 Hz, stereo, s16, 384 kb/s
 }}}

 [[BR]][[BR]]

 Finally, here's a log from another HD show immediately before the one
 reporting 5:34 for the OSD, same channel -- and which works fine (correct
 end time reported on OSD)

 {{{
 2010-02-06 12:09:01.166 Position map filled from DB to: 107769
 2010-02-06 12:09:01.167 Dec: SyncPositionMap prerecorded, from DB: 7053
 entries
 2010-02-06 12:09:01.167 Dec: SyncPositionMap, new totframes: 107769, new
 length: 1797, posMap size: 7053
 2010-02-06 12:09:01.167 Input #0, mpegts, from
 'myth://192.168.10.4:6543/2251_20100131203000.mpg':
 2010-02-06 12:09:01.167   Duration: 00:29:58.43, start: 39596.132589,
 bitrate: 14474 kb/s
 2010-02-06 12:09:01.167     Stream #0.0[0x31]: Video: mpeg2video, yuv420p,
 1280x720 [PAR 1:1 DAR 16:9], 1001/120000, 19000 kb/s, 59.94 tbr, 90k tbn,
 119.88 tbc
 2010-02-06 12:09:01.167     Stream #0.1[0x34]: Audio: ac3, 48000 Hz, 2
 channels (FL|FR|FC|LFE|SL|SR), s16, 448 kb/s
 2010-02-06 12:09:01.167     Stream #0.2[0x35]: Audio: ac3, 48000 Hz,
 stereo, s16, 192 kb/s
 2010-02-06 12:09:01.167 AFD: Position map found
 2010-02-06 12:09:01.168 AFD: Successfully opened decoder for file:
 "myth://192.168.10.4:6543/2251_20100131203000.mpg". novideo(0)
 }}}

 I'm happy to give any suggestions a try or get more log files, if anybody
 has any ideas...

-- 
Ticket URL: <http://svn.mythtv.org/trac/ticket/7978#comment:2>
MythTV <http://www.mythtv.org/>
MythTV


More information about the mythtv-commits mailing list