[mythtv-users] Record defaulting to PAL vice NTSC

[Anthony Joint]

I have also been seeing this. I also have the bttv module loaded at
startup with RedHat 9.0. I have a WinTV Go board. Mythbackend is running
as a service at boot time.

Versions up to 0.13 have worked for me without this problem.

I have wiped out my configuration and rerun the setup program. This did
not have any affect.

I am currently in the process of refilling the database. Once that's
complete. I will attempt a reboot with mythbackend no longer running as a
service. I will allow the system to come up and then run mythbackend
manually to see if this has any affect. Alternatively, since I have an
external tuner, I may pass over the Television input and go straight for
composite in.

Regards,

	-tony


On Fri, 12 Dec 2003, matt wrote:

> 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 ***
> >
> >
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>