[mythtv] Problems with v4l LiveTV in current svn

[David Maher]

On Fri, 2005-09-30 at 11:30 +1000, David Maher wrote:
> > Please send me a note with the hardware + a reasonable default for it.
> > 
> > When you first configure a DVB card it should be picking a reasonable
> > number depending on the hardware. But in the DB update that added the
> > columns there is no way to determine the exact DVB subtype you have
> > so it defaults to something like 3 seconds. This is too low for things
> > like DVB-S, or special hardware like external DVB over USB devices.
> > 
> > -- Daniel
> 
> On Thu, 2005-09-29 at 09:33 -0400, Daniel Kristjansson wrote:
> 
> > 
> > Please send me a note with the hardware + a reasonable default for it.
> > 
> > When you first configure a DVB card it should be picking a reasonable
> > number depending on the hardware. But in the DB update that added the
> > columns there is no way to determine the exact DVB subtype you have
> > so it defaults to something like 3 seconds. This is too low for things
> > like DVB-S, or special hardware like external DVB over USB devices.
> > 
> > -- Daniel
> 
> Ok, I've had a play with the channel and signal time outs on the dvb
> cards in the backend setup.
> Initially I set them both to 10000ms, which seemed to fix the problem, I
> then went down to 5000ms and noticed that the "should have..." message
> was back, but only after the signal was locked for about five seconds. I
> changed back to 10,000ms and sure enough, I just hadn't waited long
> enough on the first try. The message came back after about 10 seconds.
> My interpretation of this is that the backend never really knows that it
> has a channel lock. My channel changes are fast, I have watchable video
> about 1 second after hitting the arrow key to change channels.
> Hardware wise, my dvb cards are Twinhan VP3020 dtv cards, and I am using
> the vanilla 12.6.13 kernel's dvb support. I am also getting segfaults in
> the backend, but only with the analogue tuner. I'll upgrade to the
> current CVS now and report back. 

Hi again,
I just updated to SVN 7361 and am still seeing the same symptoms. Aside
from the should have gotten a lock dvb message, when I change to my
SAA7134 tuner, then try to change channels, either the backend segfaults
or stops responding, or the frontend goes to a black screen and
sometimes back to the main menu. Occasionally the frontend recovers and
automatically switches to a dvb tuner.

Heres the relevant part of the backend log when switching to the
SAA7134, then trying to change channels.

By the way, what Jon said with regard to your efforts, I think their
great too. I'm happy to play around with this stuff and report back. Let
me know if you need any more.


Backend log excerpt

2005-09-30 12:58:09.398 TVRec(2): Changing from WatchingLiveTV to None
2005-09-30 12:58:09.561 MainServer::HandleAnnounce Playback
2005-09-30 12:58:09.562 adding: xcube.netsol.local as a client (events:
0)
2005-09-30 12:58:09.581 MainServer::HandleAnnounce Playback
2005-09-30 12:58:09.582 adding: xcube.netsol.local as a client (events:
0)
2005-09-30 12:58:09.594 adding: xcube.netsol.local as a remote
ringbuffer
2005-09-30 12:58:09.602 TVRec(3): Changing from None to WatchingLiveTV
2005-09-30 12:58:09.621 Channel(/dev/video0)::SwitchToInput(in 0)
2005-09-30 12:58:09.637 Channel(/dev/video0)::SwitchToInput() setting
video mode to PAL
2005-09-30 12:58:09.653 Channel(/dev/video0)::SetChannelByString(10)
2005-09-30 12:58:09.655 ChannelBase(/dev/video0)::SetCachedATSCInfo():
RESET
2005-09-30 12:58:09.659 Channel(/dev/video0)::TuneTo(8):
curList[9].freq(189250)
2005-09-30 12:58:09.659 Channel(/dev/video0)::Tune(189250000, , analog)
2005-09-30 12:58:09.669 Channel(/dev/video0)::Tune(): Frequency is now
189250000
2005-09-30 12:58:09.670 ChannelBase(/dev/video0)::SetCachedATSCInfo(10):
1_0
[mpeg4 @ 0xb7664ec4]removing common factors from framerate
strange error flushing buffer ...
Segmentation fault
[root at myth ~]#