[mythtv-users] mythbackend crashes

[Brian May]

>>>>> "Brian" == Brian May <bam at snoopy.apana.org.au> writes:

I got a different type of crash today. MythTV recorded a show (via DVB
card), but without sound!

When recording the first show, I got the messages:

2004-03-25 23:30:02 Started recording "Angel" on channel: 12001 on cardid: 9, sourceid 12
2004-03-25 23:30:03 DVB#0 WARNING - Status: NO LOCK!
2004-03-25 23:30:08 DVB#0 ERROR - Poll timed out too many times, bailing.
2004-03-25 23:30:08 DVB#0 ERROR - Tuning for channel #7 failed.
Videostream: ASPECT: 16:9  Size = 720x576  FRate: 25 fps  BRate: 15.00 Mbit/s
Audiostream: Layer: 2  BRate: 256 kb/s  Freq: 48.0 kHz
2004-03-26 00:00:00 Found changes in the todo list.
2004-03-26 00:05:04 Found changes in the todo list.

There was no sound all the way to the end of the recording. The
picture was perfect.

When recording the next show on the next channel, it worked perfectly
from the very start:

2004-03-26 00:30:00 Changing from RecordingOnly to None
2004-03-26 00:30:01 Found changes in the todo list.
2004-03-26 00:30:05 Started recording "James Cameron's Dark Angel" on channel: 12001 on cardid: 9, sourceid 12
2004-03-26 00:30:05 DVB#0 Successfully tuned to channel 7.
2004-03-26 00:30:05 Changing from None to RecordingOnly
2004-03-26 00:30:05 DVB#0 Recorder: Card opened successfully.
Input #0, mpeg, from '/var/lib/mythtv//12001_20040325233000_20040326003000.nuv':Videostream: ASPECT: 16:9  Size = 720x576  FRate: 25 fps  BRate: 15.00 Mbit/s
  Stream #0.0: Video: mpeg2video, 720x576, 25.00 fps
Audiostream: Layer: 2  BRate: 256 kb/s  Freq: 48.0 kHz

When playing back the first, I repeatedly get the following message:

no codec for stream index 1

I would speculate the problem was initially channel 7 messing up, and
briefly was not transmitting audio (or something like that), however
that was the only time when MythTV tried to tune to channel 7. Despite
the fact MythTV couldn't tune, it recorded what it received regardless
and didn't retry tuning until the next program. If this was the case,
it seems very wrong.

Again, I ask:

    Brian> Would it be most constructive use of my time if I try to
    Brian> debug the problem (what is the best way of doing this? It
    Brian> seems to be different each time) or upgrade to the latest
    Brian> CVS version?

Also, how compatible is the CVS version with the 0.14 version? Can I
upgrade/downgrade the back-end and keep the same database and front
end? Or if I upgrade the backend does this mean I have to upgrade all
the front-ends simultaneously and revert to the old database if I have
to downgrade for any reason?
-- 
Brian May <bam at snoopy.apana.org.au>