Re: double images, bttv-0.7.107, PixelView PlayTV Pro

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



Excellent call Andy, thank you!

Although, I guess I should have been tipped off by the VIDIOCGCAP reporting max height and width of 970 something by 576.

The way that I fixed it, with you hint, was to request an image from the tuner, which when the code makes a call it sets the tuner to NTSC. Somehow that sets it also for the other inputs and subsequent VIDIOCGCAP reports max height and width 768 x 480 which is correct for USA NTSC for this device.

Now I should figure out how to set the norm on calls to the composite and SVideo inputs, using video for linux (not version 2).

Thanks again.

----- Original Message -----
From: Andy Gombos <gombos_2000@xxxxxxxxxxxxx>
Date: Tuesday, December 23, 2003 12:18 pm
Subject: Re: double images, bttv-0.7.107, PixelView PlayTV Pro

> It looks like the norm is set to PAL when it should be NTSC.
> 
> sschaefer1@xxxxxxxxxx wrote:
> > Hi, I've been using video for linux with my BT878 based Prolink 
> PixelView PlayTV Pro card, model PV-BT878P+(w/FM), for quite some 
> time.> 
> > 
> http://www.prolink.com.tw/english/products/multimedia/playtv%20pro.htm> 
> > The card has a composite, SVideo and TV input, which I have been 
> able to view video from.
> > I've been using a web application to capture still images to 
> display over the web.
> > 
> > Originally when I setup the V4L and the BTTV driver it took a 
> lot of effort, and when I finally managed to get it working I 
> really didn't know which hack got the thing to work. I remember 
> replacing the BTTV code in the kernel structure with a patch, or 
> drivers from a download of newer files. If I remember right the 
> patch screwed things up worse so I started over and then updated 
> the kernel structure's BTTV drivers with new ones. Ultimately 
> though, I wound up using modules, for which I would load them this 
> way (videodev was compiled in the kernel):
> > 
> > insmod /lib/modules/2.4.22/kernel/drivers/media/video/bttv.o 
> card=37 tuner=2 radio=1 autoload=0 bttv_verbose=2 bttv_debug=1
> > 
> > insmod /lib/modules/2.4.22/kernel/drivers/media/video/tuner.o 
> debug=1 type=2
> > 
> > 
> > Now I've started fresh, and built a new kernel (still 2.4.22) 
> with the kernel's BTTV (older drivers) and videodev as modules, 
> then compiled bttv-0.7.107 and installed it so the 
> /lib/modules/2.4.22/.../bttv files are the newest. After loading 
> the drivers with
> > 
> > modprobe bttv card=37 tuner=2 radio=1 bttv_verbose=2 bttv_debug=1
> > 
> > it autoloads videodev.o and tuner.o as expected, but I get 
> images like
> > 
> > http://www.schaefer.dhcp.biz/output.jpg
> > 
> > Any suggestions?
> > 
> > 
> > 
> > --
> > video4linux-list mailing list
> > Unsubscribe video4linux-list-request@xxxxxxxxxx?subject=unsubscribe
> > https://www.redhat.com/mailman/listinfo/video4linux-list
> > 
> 
> 
> --
> video4linux-list mailing list
> Unsubscribe video4linux-list-request@xxxxxxxxxx?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/video4linux-list
> 





[Index of Archives]     [Linux DVB]     [Video Disk Recorder]     [Asterisk]     [Photo]     [DCCP]     [Netdev]     [Xorg]     [Util Linux NG]     [Xfree86]     [Free Photo Albums]     [Fedora Users]     [Fedora Women]     [ALSA Users]     [ALSA Devel]     [Linux USB]

Powered by Linux