Here are some instructions that Andy helped me with some time back that I think will be of help. I think I will actually put this to my blog in the near future too. Hope this helps as basically you will want to identify where your tuner really is and make sure it is using the right standard.
You may have to write some udev rules to help out after you have it figured out. Recently I found my dev folders wandering a little. To help you there you can go to the following link for a blog entry that I did on the matter. http://petersopus.wordpress.com/2012/06/18/cure-for-the-drifting-dev-folder/ Thanks, Peter >> Please install v4l2-ctl (probably in a v4l2-utils package) and mplayer. >> >> Kill the mythbackend, if it is running. >> >> Then run v4l2-ctl --list-devices, to see what card corresponds to which >> devices nodes. For example: >> >> $ v4l2-ctl --list-devices >> Hauppauge HVR-1600 (PCI:0000:03:00.0): >> /dev/video0 >> /dev/video24 >> /dev/video32 >> /dev/vbi0 >> >> Hauppauge WinTV PVR-150 (PCI:0000:03:01.0): >> /dev/video2 >> /dev/video26 >> /dev/video34 >> /dev/radio2 >> /dev/vbi2 >> >> Hauppauge HVR-1600 (PCI:0000:03:02.0): >> /dev/video1 >> /dev/video25 >> /dev/video33 >> /dev/radio1 >> /dev/vbi1 >> >> On a device from which you wish to capture S-Video, set the proper input >> and analog TV standard using v4l2-ctl: >> >> $ v4l2-ctl -d /dev/video0 --list-inputs >> ioctl: VIDIOC_ENUMINPUT >> Input : 0 >> Name : Tuner 1 >> Type : 0x00000001 >> Audioset : 0x00000007 >> Tuner : 0x00000000 >> Standard : 0x0000000000001000 (NTSC-M) >> Status : 0x00000000 (ok) >> Capabilities: 0x00000004 (SD presets) >> >> Input : 1 >> Name : S-Video 1 >> Type : 0x00000002 >> Audioset : 0x00000007 >> Tuner : 0x00000000 >> Standard : 0x0000000000FFFFFF >> (PAL-B/B1/G/H/I/D/D1/K/M/N/Nc/60 NTSC-M/M-JP/443/M-KR >> SECAM-B/D/G/H/K/K1/L/Lc) >> Status : 0x00000000 (ok) >> Capabilities: 0x00000004 (SD presets) >> >> Input : 2 >> Name : Composite 1 >> Type : 0x00000002 >> Audioset : 0x00000007 >> Tuner : 0x00000000 >> Standard : 0x0000000000FFFFFF >> (PAL-B/B1/G/H/I/D/D1/K/M/N/Nc/60 NTSC-M/M-JP/443/M-KR >> SECAM-B/D/G/H/K/K1/L/Lc) >> Status : 0x00000000 (ok) >> Capabilities: 0x00000004 (SD presets) >> [...] >> >> $ v4l2-ctl -d /dev/video0 --set-input=1 >> Video input set to 1 (S-Video 1: ok) >> >> $ v4l2-ctl -d /dev/video0 --list-standards >> ioctl: VIDIOC_ENUMSTD >> Index : 0 >> ID : 0x000000000000B000 >> Name : NTSC >> Frame period: 1001/30000 >> Frame lines : 525 >> >> Index : 1 >> ID : 0x0000000000001000 >> Name : NTSC-M >> Frame period: 1001/30000 >> Frame lines : 525 >> [...] >> >> $ v4l2-ctl -d /dev/video0 --set-standard=1 >> Standard set to 00001000 >> >> >> Turn on your S-Video source, and then just capture an MPEG live with mplayer: >> >> $ mplayer /dev/video0 -cache 8192 >> >> or capture a file for later playback >> >> $ cat /dev/video0 > foo.mpg >> ^C >> $ mplayer foo.mpg >> >> >> >>> Here is what I see on the two problematic analog tuners. >> >> Looks like an untuned tuner input driving the encoder, not S-Video. An >> S-Video input that is connected but has no signal is usually a solid >> grey or black screen. >> >> One last step is to verify that you do in fact have a video signal with >> a known good devices (such as a TV). If you have RF analog or RF >> digital reception problems, you may want to review this checklist as >> well: >> >> http://ivtvdriver.org/index.php/Howto:Improve_signal_quality >> >> Regards, >> Andy On 2012-06-27, at 10:53 AM, Robert Rust wrote: > I have been trying in vain for weeks trying to get an HVR-1600 tuner card to > work in a new system I built (Intel mobo, Core i5, 8G RAM). It worked fine > in my old one but I'm not getting anything when I try to capture, either with > MythTV or directly cat'ing /dev/video > filename.mpg. I've tried installing > the same version of mythbuntu (10.04 w/2.6.32 kernel) that I have on my > working system but the motherboard is too new to get network support in that > kernel (so installing all the various dependencies for ivtv-utils appears to > be incredibly difficult). > Any suggestions? I am not seeing anything in kernel log right now suggesting > a direction to go. > > -Robert > _______________________________________________ > ivtv-users mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-users
_______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
