> Hans Verkuil wrote:
>> Hi Cyrus,
>>
>> Very weird. Did this happen before or did this pop up only recently?
>>
>> Anyway, you can get the current mute setting with:
>>
>> v4l2-ctl -C mute
>>
>> and set it with:
>>
>> v4l2-ctl -c mute=0 (or mute=1)
>>
>> I'm very interested to know what the mute setting is once the capture
>> mutes: it is partially controlled by the audio digitizer: if it cannot
>> detect the tuner audio signal it will mute automatically. This is
>> independent of the mute control setting. So if the status log says
>> muted,
>> but the control setting is still unmuted, then it is likely to be
>> related
>> to the audio detection.
>>
>> The 'app not reading fast enough' errors mean just that, you are not
>> reading fast enough. It has no relation to this mute problem. The
>> Invalid
>> PGM index warnings are harmless and also have no relationship to this
>> problem (AFAIK).
... cut ...
>>> [EMAIL PROTECTED] Desktop]$ diff ivtv1_after_error.txt
>>> ivtv1_before_error.txt
>>> 13c13
>>> < tuner 3-0061: Frequency: 193.25 MHz
>>> ---
>>> > tuner 3-0061: Frequency: 67.25 MHz
>>> 22c22
>>> < cx25840 3-0044: Audio muted: yes
>>> ---
>>> > cx25840 3-0044: Audio muted: no
>>> 46c46
>>> < ivtv1: Read MPEG/VBI: 2928836608/0 bytes
>>> ---
>>> > ivtv1: Read MPEG/VBI: 0/0 bytes
>>>
>>> ****Notice the audio muted... Why would it mute the audio
>>> spontaneously?***** Definitely seems like this is the problem. What's
>>> the command for "unmute" so I can make a workaround?
>>>
> I think it does say the audio has been muted (see above).
>
> What are your thoughts on that?
Unfortunately this doesn't tell me why it is muted: because of problems
detecting the audio signal, or due to a control setting. Of course, it
might also be a driver bug (the audio is muted/unmuted sometimes as well
in the driver).
So testing what the control setting is, and then trying to unmute the
audio by changing the control is a good test case.
Also try changing the channel of the still working card to the same
channel: see if that also mutes the audio. If it does, then that points to
a detection problem. If not, then it is either a driver bug or a mute
control issue.
Turning on debug level 3 (ivtvctl -D3) can also be very useful in case of
a driver bug.
Regards,
Hans
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
