[mythtv] Current DVB problems rundown
lists at kenneth.aafloy.net
Sun Sep 11 02:03:18 UTC 2005
Søndag 11 september 2005 03:36, skrev Mark Weaver:
> Daniel Kristjansson wrote:
> > On Fri, 2005-09-09 at 17:33 +0100, John Pullan wrote:
> >>I wonder if Daniel could provide us with a new current list of problems
> >> ?
> > As far as I'm aware it's down to two:
> > Mysterious rec vs livetv problem (Adam Egger)
> > Need "mythbackend -v record,channel,siparser" output from
> > both on same channel with latest SVN.
> > DVB lock threshold (John Poet -- DVB driver issue)
> > Need to know driver + driver/kernel version used.
> > The first I hoped would be fixed by fixing the less mysterious
> > problems, and the second is relatively new.
> I still have:
> - Tuning to an off air channel (UK, transmitting data only) causes the
> frontend to lock up
Can reproduce this, even worse is it that the tuned channel is stored before
it's confirmed that it works, so when you want to restart the backend it will
be set on a broken channel.
Just to mention it, there are many reasons a channel can fail on dvb, where
tuning is the most obvious. Another thing that can fail randomly is the cam,
which can hang at irregular intervals. This is most likely caused by broken
section parsing in the cam, since this also happens on commercial tuners.
What is lame about the cam issue is that the time the backend/frontend wait's
is not extended to account for a cam reset cycle, which takes some time with
As a quick fix I've just commented out the section in tv_rec.cpp:~3781,
I'll see if I can handle this properly some day and send a patch.
> - Seeking in liveTV is broken
Couldn't reproduce this in a quick test.
> - And a new one, I now get random audio + video glitches when tuning to
> a new channel.
I have gotten audio distortion of various kinds when changing between streams
with different parameters, ranging from pure noise to 44.1 @ 48.
More information about the mythtv-dev