Peter Schneider <[email protected]> wrote:

>Andy,
>
>With the second PVR-500 tuner I am not getting any audio.  Do you have
>any idea if this might be related to the v4l2 setup?
>
>-Peter
>
>On 2012-02-11, at 4:09 PM, Andy Walls wrote:
>
>> On Sat, 2012-02-11 at 15:44 -0700, Peter Schneider wrote:
>>> Thanks Andy,
>>> 
>>> You are THE MAN!!!!  From the v4l2-ctl command I now have the analog
>>> working on both tuners for the 500 and now on the HVR-1600!!!
>>> 
>>> I am concerned about the HVR-2250 but that will be a debug to happen
>>> when I have an antenna built.  At that time I can use the HVR-1600
>>> digital tuner to test the antenna and then engage the HVR-2250.
>>> 
>>> Thanks again Andy.
>> 
>> You're welcome. :)
>> 
>> -Andy
>> 
>>> -Peter
>>> 
>>> 
>>> On 2012-02-11, at 3:02 PM, Andy Walls wrote:
>>> 
>>>> On Sat, 2012-02-11 at 11:02 -0700, Gmail wrote:
>>>>> Hi All,
>> 
>>>>> 
>>>>> Note: The Analog tuners are being used to capture video through
>the
>>>>> s-video cable from my satellite tuners and the digital ones are
>for
>>>>> future OTA HD.  
>>>> 
>>>> 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
>>>> 
>>>>> 
>>>>> -Peter
>> 
>> 
>> 
>> _______________________________________________
>> 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

No audio for the 2nd RF input means there's a problem with the 2nd analog tuner 
can or a problem with the second CX25843 chip.

No audio for the 2nd S Video input usually means you don't have the proper 
extra audio cable/bracket installed.  There were at least two different 
versions of that cable/bracket for the 500 and 150 variants.

 v4l2-ctl -d /dev/videoN --log-status 

Should tell you what audio input is being used and if the RF broadcast audio 
decoding microcontroller is running or muted.  V4l2-ctl can also set the audio 
input explicitly different than the one normally paired with a particular video 
connector.

v4l2-ctl --help

Lists all the options.

-Andy

_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Reply via email to