Hi. Sorry for butting in, but i have to give the famous "me too". I watch mostly digital tv nowdays, but i used to have a pvr150 and a pvr350. I still use the pvr350 for X, and some analogue channels i rarely watch.
Anyway, i also have spontaneous muting on the pvr350 card. I just wanted to point this out that the 350 most likely also is included here. /Br Fredrik On Thu, 2007-06-28 at 08:46 +0200, Hans Verkuil wrote: > > Hans Verkuil wrote: > >>> 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 > >> > >> > > At 22:00, both ivtv1 and ivtv0 went mute. > > > > [EMAIL PROTECTED] ~]$ v4l2-ctl -C mute --device=/dev/video0 > > mute: 1 > > [EMAIL PROTECTED] ~]$ v4l2-ctl -C mute --device=/dev/video1 > > mute: 1 > > [EMAIL PROTECTED] ~]$ v4l2-ctl -C mute --device=/dev/video2 > > mute: 0 > > > > Unmuting doesn't work: > > [EMAIL PROTECTED] cyrus]# v4l2-ctl -c mute=0 --device=/dev/video0 > > [EMAIL PROTECTED] cyrus]# v4l2-ctl -C mute --device=/dev/video0 > > mute: 1 > > > > The error log shows: > > Jun 27 21:59:41 newkoala kernel: ivtv0 info: read 32768 from encoder > > MPEG, got 32768 > > Jun 27 21:59:41 newkoala kernel: ivtv0 info: read 34560 from encoder > > VBI, got 34560 > > Jun 27 21:59:41 newkoala kernel: ivtv0 info: read 32768 from encoder > > MPEG, got 32768 > > Jun 27 21:59:41 newkoala kernel: ivtv0 info: read 34560 from encoder > > VBI, got 34560 > > Jun 27 21:59:41 newkoala kernel: ivtv0 info: read 34560 from encoder > > VBI, got 34560 > > Jun 27 21:59:41 newkoala kernel: ivtv0 info: read 32768 from encoder > > MPEG, got 32768 > > Jun 27 21:59:41 newkoala last message repeated 3 times > > Jun 27 21:59:41 newkoala kernel: ivtv0 info: read 34560 from encoder > > VBI, got 34560 > > Jun 27 21:59:41 newkoala kernel: ivtv0 info: read 32768 from encoder > > MPEG, got 32768 > > Jun 27 21:59:41 newkoala kernel: ivtv0 info: read 34560 from encoder > > VBI, got 34560 > > Jun 27 21:59:41 newkoala kernel: ivtv0 info: close stopping capture > > Jun 27 21:59:41 newkoala kernel: ivtv0 info: Stop Capture > > Jun 27 21:59:41 newkoala kernel: ivtv0 info: read 32768 from encoder > > MPEG, got 32768 > > Jun 27 21:59:42 newkoala last message repeated 17 times > > Jun 27 21:59:42 newkoala kernel: ivtv0 info: close stopping capture > > Jun 27 21:59:42 newkoala kernel: ivtv0 info: Stop Capture > > *** new show starts *** > > Jun 27 22:00:01 newkoala kernel: ivtv0 info: Mute > > Jun 27 22:00:01 newkoala kernel: ivtv0 info: v4l2 ioctl: set frequency > > 8468 > > Jun 27 22:00:01 newkoala kernel: ivtv1 info: Mute > > Jun 27 22:00:01 newkoala kernel: ivtv1 info: v4l2 ioctl: set frequency > > 3764 > > Jun 27 22:00:02 newkoala kernel: ivtv0 info: Start encoder stream > > encoder VBI > > Jun 27 22:00:02 newkoala kernel: ivtv0 info: Unmute > > Jun 27 22:00:02 newkoala kernel: ivtv1 info: Unmute > > Jun 27 22:00:02 newkoala kernel: ivtv1 info: Start encoder stream > > encoder MPEG > > Jun 27 22:00:02 newkoala kernel: ivtv0 info: Setup VBI API header > > 0x0000bd03 pkts 1 buffs 4 ln 24 sz 1456 > > Jun 27 22:00:02 newkoala kernel: ivtv0 info: Setup VBI start 0x002fea04 > > frames 4 fpi 1 lines 0x00000140 > > Jun 27 22:00:02 newkoala kernel: ivtv1 info: Setup VBI API header > > 0x0000bd03 pkts 1 buffs 4 ln 24 sz 1456 > > Jun 27 22:00:02 newkoala kernel: ivtv1 info: Setup VBI start 0x002fea04 > > frames 4 fpi 1 lines 0x00000140 > > Jun 27 22:00:02 newkoala kernel: ivtv0 info: PGM Index at 0x00180150 > > with 400 elements > > Jun 27 22:00:02 newkoala kernel: ivtv1 info: PGM Index at 0x00180150 > > with 400 elements > > Jun 27 22:00:02 newkoala kernel: ivtv0 info: Start encoder stream > > encoder MPEG > > Jun 27 22:00:02 newkoala kernel: ivtv1 info: Start encoder stream > > encoder VBI > > Jun 27 22:00:03 newkoala kernel: ivtv0 info: read 34560 from encoder > > VBI, got 34560 > > Jun 27 22:00:03 newkoala kernel: ivtv0 info: read 32768 from encoder > > MPEG, got 32768 > > Jun 27 22:00:03 newkoala kernel: ivtv0 info: read 34560 from encoder > > VBI, got 34560 > > Jun 27 22:00:03 newkoala kernel: ivtv0 info: read 32768 from encoder > > MPEG, got 32768 > > Jun 27 22:00:03 newkoala kernel: ivtv0 info: read 32768 from encoder > > MPEG, got 32768 > > Jun 27 22:00:03 newkoala kernel: ivtv1 info: read 34560 from encoder > > VBI, got 34560 > > Jun 27 22:00:03 newkoala kernel: ivtv1 info: read 34560 from encoder > > VBI, got 34560 > > Jun 27 22:00:03 newkoala kernel: ivtv1 info: read 32768 from encoder > > MPEG, got 32768 > > Jun 27 22:00:03 newkoala kernel: ivtv1 info: read 32768 from encoder > > MPEG, got 32768 > > Jun 27 22:00:03 newkoala kernel: ivtv0 info: read 34560 from encoder > > VBI, got 34560 > > Jun 27 22:00:03 newkoala kernel: ivtv0 info: read 32768 from encoder > > MPEG, got 32768 > > Jun 27 22:00:03 newkoala kernel: ivtv1 info: read 32768 from encoder > > MPEG, got 32768 > > Jun 27 22:00:03 newkoala kernel: ivtv1 info: read 34560 from encoder > > VBI, got 34560 > > Jun 27 22:00:03 newkoala kernel: ivtv1 info: read 32768 from encoder > > MPEG, got 32768 > > Jun 27 22:00:03 newkoala kernel: ivtv0 info: read 34560 from encoder > > VBI, got 34560 > > Jun 27 22:00:03 newkoala kernel: ivtv1 info: read 32768 from encoder > > MPEG, got 32768 > > Jun 27 22:00:03 newkoala kernel: ivtv1 info: read 34560 from encoder > > VBI, got 34560 > > Jun 27 22:00:03 newkoala kernel: ivtv0 info: read 32768 from encoder > > MPEG, got 32768 > > Jun 27 22:00:03 newkoala kernel: ivtv0 info: read 34560 from encoder > > VBI, got 34560 > > Jun 27 22:00:03 newkoala kernel: ivtv0 info: read 34560 from encoder > > VBI, got 34560 > > Jun 27 22:00:03 newkoala kernel: ivtv0 info: read 32768 from encoder > > MPEG, got 32768 > > ... > > > > Both cards were tuned to different channels and this phenomenon happens > > on all frequencies. It has always happened when there have been lots of > > recordings on lots of devices... i.e. a full slate of recordings. > > Happens more often the more "stuff" is going on. > > > > Aren't you glad I'm pushing ivtv so hard?!? Let me know what you can > > make of this. > > > > Cyrus > > > > p.s. unloading and loading ivtv fixes the mute issue. > > Interesting results. But it will have to wait until Friday or Saturday > before I can look at it. I wonder if this might be another case where > there is perhaps insufficient locking. It certainly 'smells' of a driver > bug. > > And yes, I'm glad your pushing ivtv so hard :-) Very good stress tests! > > Thanks, > > Hans > > > _______________________________________________ > ivtv-devel mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-devel _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
