Re: Problems setting tuner params for Osprey 100 w/ bttv 0.7.106

[David Topper <topper@xxxxxxxxxxxx>]

Hi again,

Well, I am currently doing the following (in addition to what I mention 
below):

   /* SET VIDEO CHANNEL */
   vidcan.channel = 2;
   vidcan.tuners = 0;
   vidcan.type = VIDEO_TYPE_TV;
   if (-1== ioctl(cam, VIDIOCSCHAN,&vidcan)) {
       perror ("ioctl VIDIOCSCHAN");
       exit (-1);
   }

So I'm not sure what to set here.  

vidcan.norm = NTSC?

Also, I've determined that the actual phenomenon is fixed with avicap by 
setting the "deinterlace" or "preview" option.  So my new question is 
how one goes about setting that, which seems to have been taken care of 
with my old code below.

Thanks very much,

DT

> Subject:
> Re: Problems setting tuner params for Osprey 100 w/ bttv 0.7.106
> From:
> Gerd Knorr <kraxel@xxxxxxxxxxx>
> Date:
> 15 May 2003 10:22:10 +0200
> To:
> video4linux-list@xxxxxxxxxx
>
>
> "David J. Topper" <topper@xxxxxxxxxxxx> writes:
>
>  
>
> > 	vidtun.mode = VIDEO_MODE_NTSC;
> > 	if (-1== ioctl(cam, VIDIOCSTUNER,&vidtun)) {
> > 		perror ("ioctl VIDIOCSTUNER");
> > 		exit (-1);
> > 	}
> >    
>
> use video_channel->norm + VIDIOCSCHAN instead.  tv norm in struct
> video_tuner is a design bug (exactly because it makes sense to switch
> tv norms even on hardware which hasn't a tuner) and only there for
> historical reasons.
>
>  Gerd