[mythtv-users] Record defaulting to PAL vice NTSC

[matt]

Thanks for the reply.

I never had a problem with this before.
My bttv modules are loaded on startup. Also I haven't changed anything with
the bttv modules in a few months, nor have I rebooted in quite a while. So I
don't think this applies to my situation.

----- Original Message ----- 
From: <steve at nexusuk.org>
To: "matt" <matthew at imisssleep.com>; "Discussion about mythtv"
<mythtv-users at mythtv.org>
Sent: Friday, December 12, 2003 7:20 PM
Subject: Re: [mythtv-users] Record defaulting to PAL vice NTSC


> On Fri, 12 Dec 2003, matt wrote:
>
> > If I open xawtv, set to NTSC, then close it, run backend & frontend, and
> > then view live tv it works fine (i.e. is set to NTSC). This really
baffles
> > me.
>
> Not sure if this is at all related, but if the bttv module isn't loaded on
> my machine when Myth starts up then it gets automagically modprobed when
> Myth opens the device (as it should) but then Myth fails to set the
> channel (It gets "frequency out of range" errors or somesuch ISTR, which
> is very odd since I'm using Svideo).  After that, Myth will never be able
> to set the channel until I rmmod the module or reboot the box.  My
> solution is to startup mythbackend in a script that does:
>
> modprobe bttv
> sleep 1
> mythbackend
>
> Try that and see if it works around your problem (I assume that if you try
> to access the bttv driver immediately after it's loaded then it's still
> doing some initialisation and things break).
>
> -- 
>
>  - Steve
http://www.nexusuk.org/
>
>         *** Presented in DoubleVision (Where Drunk) - Futurama ***
>
>