[mythtv-users] help - some recordings seem to be much too short.

Chris Rouch chris.rouch at gmail.com
Tue Jan 5 18:20:24 UTC 2010


On Tue, Jan 5, 2010 at 6:59 PM, Chris Rouch <chris.rouch at gmail.com> wrote:
> On Tue, Jan 5, 2010 at 3:42 AM, Michael T. Dean <mtdean at thirdcontact.com> wrote:
>> On 01/03/2010 05:05 PM, Chris Rouch wrote:
>>> I've just upgraded to 0.22. All the programs that i recorded before
>>> the upgrade all playback correctly. But some of the ones recorded
>>> since do not. The recording is good - mplayer plays it correctly and
>>> shows the correct length - but mythfrontend thinks it is much shorter
>>> than it really is. That said if i skip forward using mythfrontend i
>>> can skip past the point where it would play to and it will play for a
>>> few minutes more before stopping again.
>>>
>>> As an example, I recorded the last episode of doctor who. With padding
>>> this is a 1 hour, 31 minute recording and a 1.7Gb file mythfrontend
>>> shows it as being 20 minutes long and stops when it reaches 21
>>> minutes. if i then skip forward to around 7 minutes (as shown on the
>>> display) i can see that i'm at the point where playback stopped (i.e
>>> 20 minutes) and watch again for 5 minutes or so. the amount extra i
>>> can gain this way seems to get less with each iteration. needless to
>>> say this makes playback very tedious.
>>>
>>> this seems to be the case with all recordings on bbc1 and bbc2, but
>>> not on the other channels i've recorded from since the upgrade.
>>>
>>> does anyone have any ideas how to fix this?
>>>
>>
>> First step:
>> http://www.mythtv.org/wiki/User_Manual:Periodic_Maintenance#Optimize_the_Database
>>
>
> That should be running from cron.daily anyway, but I ran it by hand to
> make sure. It made no difference.
>
> Thanks,
>
> Chris
>

This is what I see in the backend logs when this happens:

2010-01-05 19:14:01.545 adding: kendall as a client (events: 0)
2010-01-05 19:14:01.625 mythbackend version:
branches/release-0-22-fixes/mythtv/ [22973] www.mythtv.org
2010-01-05 19:14:01.626 Using runtime prefix = /usr
2010-01-05 19:14:01.626 Using configuration directory = /var/lib/mythtv
2010-01-05 19:14:01.626 Empty LocalHostName.
2010-01-05 19:14:01.626 Using localhost value of sheedy
2010-01-05 19:14:01.633 New DB connection, total: 1
2010-01-05 19:14:01.638 Connected to database 'mythconverg' at host: localhost
2010-01-05 19:14:01.638 Closing DB connection named 'DBManager0'
2010-01-05 19:14:01.639 Connected to database 'mythconverg' at host: localhost
2010-01-05 19:14:01.644 Current MythTV Schema Version (DBSchemaVer): 1244
2010-01-05 19:14:01.701 New DB connection, total: 2
2010-01-05 19:14:01.701 Connected to database 'mythconverg' at host: localhost
2010-01-05 19:14:02.602 AFD: Opened codec 0x887b5e0, id(MPEG2VIDEO) type(Video)
2010-01-05 19:14:02.602 AFD: codec MP2 has 2 channels
2010-01-05 19:14:02.602 AFD: Opened codec 0x887c9e0, id(MP2) type(Audio)
2010-01-05 19:14:02.734 Preview: Grabbed preview
'/a/tv/mythtv/recordings/112_20100101021800.mpg' 720x480 at 300s
2010-01-05 19:14:02.815 MainServer::ANN Playback
2010-01-05 19:14:02.815 adding: kendall as a client (events: 0)
2010-01-05 19:14:02.816 MainServer::HandleAnnounce FileTransfer
2010-01-05 19:14:02.816 adding: kendall as a remote file transfer
2010-01-05 19:15:24.747 MainServer::ANN Monitor


Sometimes I also get lots of these:

2010-01-05 19:10:03.298 [mpeg2video @ 0x4a033ee0]Missing picture start code

(when I first upgraded I was getting tens of thousands of these, but
on playback of one of the bad recordings just now I got around 20 of
them).


Chris


More information about the mythtv-users mailing list