Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: ivtv: devel

spontaneous muting

  

 
ivtv devel RSS feed   Index | Next | Previous | View Threaded


lists at rooseveltmedia

Jun 27, 2007, 8:08 AM

Post #1 of 25 (10224 views)
Permalink
spontaneous muting
After a few days of recording dozens of 1-hour programs on a PVR-500
(usually simultaneous and one-after-another), one of the ivtv devices
will go silent. It'll record a show (and all subsequent shows on that
tuner) with silent audio until the system is rebooted. The recordings on
the other device are unaffected.

Under a normal debug level, nothing shows up in the kernel logs that
would indicate a problem.

Here is my device status AFTER the bug:

(in this case, ivtv1 was the one that went silent, not ivtv0 -- not sure
if there's a pattern that it's always ivtv1)

[root [at] wtv cyrus]# v4l2-ctl --log-status --device=/dev/video0

Status Log:

ivtv0: ================= START STATUS CARD #0 =================
tveeprom 2-0050: Hauppauge model 23552, rev E587, serial# 8363157
tveeprom 2-0050: tuner model is Samsung TCPN 2121P30A (idx 87, type 70)
tveeprom 2-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 2-0050: second tuner model is Philips TEA5768HL FM Radio
(idx 101, type 62)
tveeprom 2-0050: audio processor is CX25843 (idx 37)
tveeprom 2-0050: decoder processor is CX25843 (idx 30)
tveeprom 2-0050: has radio, has no IR receiver, has no IR transmitter
tuner 2-0060: Tuner mode: undefined
tuner 2-0060: Frequency: 0.00 MHz
tuner 2-0060: Standard: 0x00000000
tuner 2-0061: Tuner mode: analog TV
tuner 2-0061: Frequency: 175.25 MHz
tuner 2-0061: Standard: 0x00001000
cx25840 2-0044: Video signal: present
cx25840 2-0044: Detected format: NTSC-M
cx25840 2-0044: Specified standard: NTSC-M
cx25840 2-0044: Specified video input: Composite 7
cx25840 2-0044: Specified audioclock freq: 48000 Hz
cx25840 2-0044: Detected audio mode: stereo
cx25840 2-0044: Detected audio standard: BTSC
cx25840 2-0044: Audio muted: no
cx25840 2-0044: Audio microcontroller: running
cx25840 2-0044: Configured audio standard: automatic detection
cx25840 2-0044: Configured audio system: BTSC
cx25840 2-0044: Specified audio input: Tuner (In8)
cx25840 2-0044: Preferred audio mode: stereo
wm8775 2-001b: Input: 2
ivtv0: Video Input: Tuner 1
ivtv0: Audio Input: Tuner 1
ivtv0: Tuner: TV
ivtv0: Stream: MPEG-2 Program Stream
ivtv0: VBI Format: No VBI
ivtv0: Video: 720x480, 30 fps
ivtv0: Video: MPEG-2, 4x3, Variable Bitrate, 6000000, Peak 8000000
ivtv0: Video: GOP Size 15, 2 B-Frames, GOP Closure, No 3:2 Pulldown
ivtv0: Audio: 48 kHz, Layer II, 224 kbps, Stereo, No Emphasis, No CRC
ivtv0: Spatial Filter: Manual, Luma 1D Horizontal, Chroma 1D
Horizontal, 0
ivtv0: Temporal Filter: Manual, 8
ivtv0: Median Filter: Off, Luma [0, 255], Chroma [0, 255]
ivtv0: Status flags: 0x00000000
ivtv0: Stream encoder MPEG: status 0x0000, 0% of 4096 KiB (128
buffers) in use
ivtv0: Stream encoder YUV: status 0x0000, 0% of 2046 KiB (194
buffers) in use
ivtv0: Stream encoder VBI: status 0x0000, 0% of 1023 KiB (60 buffers)
in use
ivtv0: Stream encoder PCM audio: status 0x0000, 0% of 1021 KiB (227
buffers) in use
ivtv0: Read MPEG/VBI: 2929000448/0 bytes
ivtv0: ================== END STATUS CARD #0 ==================

[root [at] wtv cyrus]# v4l2-ctl --log-status --device=/dev/video1

Status Log:

ivtv1: ================= START STATUS CARD #1 =================
tveeprom 3-0050: Hauppauge model 23552, rev E587, serial# 8363157
tveeprom 3-0050: tuner model is Samsung TCPN 2121P30A (idx 87, type 70)
tveeprom 3-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 3-0050: second tuner model is Philips TEA5768HL FM Radio
(idx 101, type 62)
tveeprom 3-0050: audio processor is CX25843 (idx 37)
tveeprom 3-0050: decoder processor is CX25843 (idx 30)
tveeprom 3-0050: has radio, has no IR receiver, has no IR transmitter
tuner 3-0061: Tuner mode: analog TV
tuner 3-0061: Frequency: 193.25 MHz
tuner 3-0061: Standard: 0x00001000
cx25840 3-0044: Video signal: present
cx25840 3-0044: Detected format: NTSC-M
cx25840 3-0044: Specified standard: NTSC-M
cx25840 3-0044: Specified video input: Composite 7
cx25840 3-0044: Specified audioclock freq: 48000 Hz
cx25840 3-0044: Detected audio mode: stereo
cx25840 3-0044: Detected audio standard: BTSC
cx25840 3-0044: Audio muted: yes
cx25840 3-0044: Audio microcontroller: running
cx25840 3-0044: Configured audio standard: automatic detection
cx25840 3-0044: Configured audio system: BTSC
cx25840 3-0044: Specified audio input: Tuner (In8)
cx25840 3-0044: Preferred audio mode: stereo
wm8775 3-001b: Input: 2
ivtv1: Video Input: Tuner 1
ivtv1: Audio Input: Tuner 1
ivtv1: Tuner: TV
ivtv1: Stream: MPEG-2 Program Stream
ivtv1: VBI Format: No VBI
ivtv1: Video: 720x480, 30 fps
ivtv1: Video: MPEG-2, 4x3, Variable Bitrate, 6000000, Peak 8000000
ivtv1: Video: GOP Size 15, 2 B-Frames, GOP Closure, No 3:2 Pulldown
ivtv1: Audio: 48 kHz, Layer II, 224 kbps, Stereo, No Emphasis, No CRC
ivtv1: Spatial Filter: Manual, Luma 1D Horizontal, Chroma 1D
Horizontal, 0
ivtv1: Temporal Filter: Manual, 8
ivtv1: Median Filter: Off, Luma [0, 255], Chroma [0, 255]
ivtv1: Status flags: 0x00000000
ivtv1: Stream encoder MPEG: status 0x0000, 0% of 4096 KiB (128
buffers) in use
ivtv1: Stream encoder YUV: status 0x0000, 0% of 2046 KiB (194
buffers) in use
ivtv1: Stream encoder VBI: status 0x0000, 0% of 1023 KiB (60 buffers)
in use
ivtv1: Stream encoder PCM audio: status 0x0000, 0% of 1021 KiB (227
buffers) in use
ivtv1: Read MPEG/VBI: 2928836608/0 bytes
ivtv1: ================== END STATUS CARD #1 ==================

After rebooting to fix the error, I diff'd the two:

[cyrus [at] wtv Desktop]$ diff ivtv0_after_error.txt ivtv0_before_error.txt
16c16
< tuner 2-0061: Frequency: 175.25 MHz
---
> tuner 2-0061: Frequency: 67.25 MHz
49c49
< ivtv0: Read MPEG/VBI: 2929000448/0 bytes
---
> ivtv0: Read MPEG/VBI: 0/0 bytes

[cyrus [at] wtv 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?

This is the error log, but the error started at June 26 23:00 so it
doesn't make sense. ivtv1 at 5:00, 12:00 and 18:00 on the 26th were all
fine. The only thing I see at the critical time (23:00 on the 26th) was
that ivtv0 and ivtv1 both messed up at the same time. I'll try to get
better error messages when I reboot and reset the debug level. Again,
ivtv1 at 5:00 and 6:00 on the 27th were also silent. Once it goes bad,
it stays bad, it would seem.

Jun 26 05:00:07 wtvq kernel: ivtv1: All encoder VBI stream buffers are
full. Dropping data.
Jun 26 05:00:07 wtvq kernel: ivtv1: Cause: the application is not
reading fast enough.
Jun 26 06:43:55 wtvq kernel: ivtv0 warning: Invalid PGM index 91164673
(>= 400)
Jun 26 06:43:55 wtvq kernel: ivtv0 warning: Invalid PGM index 178891441
(>= 400)
Jun 26 06:43:55 wtvq kernel: ivtv0 warning: Invalid PGM index 178891441
(>= 400)
Jun 26 12:00:07 wtvq kernel: ivtv1: All encoder VBI stream buffers are
full. Dropping data.
Jun 26 12:00:07 wtvq kernel: ivtv1: Cause: the application is not
reading fast enough.
Jun 26 18:00:06 wtvq kernel: ivtv1: All encoder VBI stream buffers are
full. Dropping data.
Jun 26 18:00:06 wtvq kernel: ivtv1: Cause: the application is not
reading fast enough.
Jun 26 23:00:07 wtvq kernel: ivtv0: All encoder VBI stream buffers are
full. Dropping data.
Jun 26 23:00:07 wtvq kernel: ivtv0: Cause: the application is not
reading fast enough.
Jun 26 23:00:07 wtvq kernel: ivtv1: All encoder VBI stream buffers are
full. Dropping data.
Jun 26 23:00:07 wtvq kernel: ivtv1: Cause: the application is not
reading fast enough.
Jun 27 05:00:07 wtvq kernel: ivtv1: All encoder VBI stream buffers are
full. Dropping data.
Jun 27 05:00:07 wtvq kernel: ivtv1: Cause: the application is not
reading fast enough.
Jun 27 06:00:06 wtvq kernel: ivtv0: All encoder VBI stream buffers are
full. Dropping data.
Jun 27 06:00:06 wtvq kernel: ivtv0: Cause: the application is not
reading fast enough.
Jun 27 06:00:06 wtvq kernel: ivtv1: All encoder VBI stream buffers are
full. Dropping data.
Jun 27 06:00:06 wtvq kernel: ivtv1: Cause: the application is not
reading fast enough.


Thanks for any help you can provide.

Cyrus





_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


hverkuil at xs4all

Jun 27, 2007, 8:21 AM

Post #2 of 25 (9789 views)
Permalink
Re: spontaneous muting [In reply to]
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).

Regards,

Hans

PS: Thank you for the donation! Much appreciated.

> After a few days of recording dozens of 1-hour programs on a PVR-500
> (usually simultaneous and one-after-another), one of the ivtv devices
> will go silent. It'll record a show (and all subsequent shows on that
> tuner) with silent audio until the system is rebooted. The recordings on
> the other device are unaffected.
>
> Under a normal debug level, nothing shows up in the kernel logs that
> would indicate a problem.
>
> Here is my device status AFTER the bug:
>
> (in this case, ivtv1 was the one that went silent, not ivtv0 -- not sure
> if there's a pattern that it's always ivtv1)
>
> [root [at] wtv cyrus]# v4l2-ctl --log-status --device=/dev/video0
>
> Status Log:
>
> ivtv0: ================= START STATUS CARD #0 =================
> tveeprom 2-0050: Hauppauge model 23552, rev E587, serial# 8363157
> tveeprom 2-0050: tuner model is Samsung TCPN 2121P30A (idx 87, type 70)
> tveeprom 2-0050: TV standards NTSC(M) (eeprom 0x08)
> tveeprom 2-0050: second tuner model is Philips TEA5768HL FM Radio
> (idx 101, type 62)
> tveeprom 2-0050: audio processor is CX25843 (idx 37)
> tveeprom 2-0050: decoder processor is CX25843 (idx 30)
> tveeprom 2-0050: has radio, has no IR receiver, has no IR transmitter
> tuner 2-0060: Tuner mode: undefined
> tuner 2-0060: Frequency: 0.00 MHz
> tuner 2-0060: Standard: 0x00000000
> tuner 2-0061: Tuner mode: analog TV
> tuner 2-0061: Frequency: 175.25 MHz
> tuner 2-0061: Standard: 0x00001000
> cx25840 2-0044: Video signal: present
> cx25840 2-0044: Detected format: NTSC-M
> cx25840 2-0044: Specified standard: NTSC-M
> cx25840 2-0044: Specified video input: Composite 7
> cx25840 2-0044: Specified audioclock freq: 48000 Hz
> cx25840 2-0044: Detected audio mode: stereo
> cx25840 2-0044: Detected audio standard: BTSC
> cx25840 2-0044: Audio muted: no
> cx25840 2-0044: Audio microcontroller: running
> cx25840 2-0044: Configured audio standard: automatic detection
> cx25840 2-0044: Configured audio system: BTSC
> cx25840 2-0044: Specified audio input: Tuner (In8)
> cx25840 2-0044: Preferred audio mode: stereo
> wm8775 2-001b: Input: 2
> ivtv0: Video Input: Tuner 1
> ivtv0: Audio Input: Tuner 1
> ivtv0: Tuner: TV
> ivtv0: Stream: MPEG-2 Program Stream
> ivtv0: VBI Format: No VBI
> ivtv0: Video: 720x480, 30 fps
> ivtv0: Video: MPEG-2, 4x3, Variable Bitrate, 6000000, Peak 8000000
> ivtv0: Video: GOP Size 15, 2 B-Frames, GOP Closure, No 3:2 Pulldown
> ivtv0: Audio: 48 kHz, Layer II, 224 kbps, Stereo, No Emphasis, No CRC
> ivtv0: Spatial Filter: Manual, Luma 1D Horizontal, Chroma 1D
> Horizontal, 0
> ivtv0: Temporal Filter: Manual, 8
> ivtv0: Median Filter: Off, Luma [0, 255], Chroma [0, 255]
> ivtv0: Status flags: 0x00000000
> ivtv0: Stream encoder MPEG: status 0x0000, 0% of 4096 KiB (128
> buffers) in use
> ivtv0: Stream encoder YUV: status 0x0000, 0% of 2046 KiB (194
> buffers) in use
> ivtv0: Stream encoder VBI: status 0x0000, 0% of 1023 KiB (60 buffers)
> in use
> ivtv0: Stream encoder PCM audio: status 0x0000, 0% of 1021 KiB (227
> buffers) in use
> ivtv0: Read MPEG/VBI: 2929000448/0 bytes
> ivtv0: ================== END STATUS CARD #0 ==================
>
> [root [at] wtv cyrus]# v4l2-ctl --log-status --device=/dev/video1
>
> Status Log:
>
> ivtv1: ================= START STATUS CARD #1 =================
> tveeprom 3-0050: Hauppauge model 23552, rev E587, serial# 8363157
> tveeprom 3-0050: tuner model is Samsung TCPN 2121P30A (idx 87, type 70)
> tveeprom 3-0050: TV standards NTSC(M) (eeprom 0x08)
> tveeprom 3-0050: second tuner model is Philips TEA5768HL FM Radio
> (idx 101, type 62)
> tveeprom 3-0050: audio processor is CX25843 (idx 37)
> tveeprom 3-0050: decoder processor is CX25843 (idx 30)
> tveeprom 3-0050: has radio, has no IR receiver, has no IR transmitter
> tuner 3-0061: Tuner mode: analog TV
> tuner 3-0061: Frequency: 193.25 MHz
> tuner 3-0061: Standard: 0x00001000
> cx25840 3-0044: Video signal: present
> cx25840 3-0044: Detected format: NTSC-M
> cx25840 3-0044: Specified standard: NTSC-M
> cx25840 3-0044: Specified video input: Composite 7
> cx25840 3-0044: Specified audioclock freq: 48000 Hz
> cx25840 3-0044: Detected audio mode: stereo
> cx25840 3-0044: Detected audio standard: BTSC
> cx25840 3-0044: Audio muted: yes
> cx25840 3-0044: Audio microcontroller: running
> cx25840 3-0044: Configured audio standard: automatic detection
> cx25840 3-0044: Configured audio system: BTSC
> cx25840 3-0044: Specified audio input: Tuner (In8)
> cx25840 3-0044: Preferred audio mode: stereo
> wm8775 3-001b: Input: 2
> ivtv1: Video Input: Tuner 1
> ivtv1: Audio Input: Tuner 1
> ivtv1: Tuner: TV
> ivtv1: Stream: MPEG-2 Program Stream
> ivtv1: VBI Format: No VBI
> ivtv1: Video: 720x480, 30 fps
> ivtv1: Video: MPEG-2, 4x3, Variable Bitrate, 6000000, Peak 8000000
> ivtv1: Video: GOP Size 15, 2 B-Frames, GOP Closure, No 3:2 Pulldown
> ivtv1: Audio: 48 kHz, Layer II, 224 kbps, Stereo, No Emphasis, No CRC
> ivtv1: Spatial Filter: Manual, Luma 1D Horizontal, Chroma 1D
> Horizontal, 0
> ivtv1: Temporal Filter: Manual, 8
> ivtv1: Median Filter: Off, Luma [0, 255], Chroma [0, 255]
> ivtv1: Status flags: 0x00000000
> ivtv1: Stream encoder MPEG: status 0x0000, 0% of 4096 KiB (128
> buffers) in use
> ivtv1: Stream encoder YUV: status 0x0000, 0% of 2046 KiB (194
> buffers) in use
> ivtv1: Stream encoder VBI: status 0x0000, 0% of 1023 KiB (60 buffers)
> in use
> ivtv1: Stream encoder PCM audio: status 0x0000, 0% of 1021 KiB (227
> buffers) in use
> ivtv1: Read MPEG/VBI: 2928836608/0 bytes
> ivtv1: ================== END STATUS CARD #1 ==================
>
> After rebooting to fix the error, I diff'd the two:
>
> [cyrus [at] wtv Desktop]$ diff ivtv0_after_error.txt ivtv0_before_error.txt
> 16c16
> < tuner 2-0061: Frequency: 175.25 MHz
> ---
> > tuner 2-0061: Frequency: 67.25 MHz
> 49c49
> < ivtv0: Read MPEG/VBI: 2929000448/0 bytes
> ---
> > ivtv0: Read MPEG/VBI: 0/0 bytes
>
> [cyrus [at] wtv 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?
>
> This is the error log, but the error started at June 26 23:00 so it
> doesn't make sense. ivtv1 at 5:00, 12:00 and 18:00 on the 26th were all
> fine. The only thing I see at the critical time (23:00 on the 26th) was
> that ivtv0 and ivtv1 both messed up at the same time. I'll try to get
> better error messages when I reboot and reset the debug level. Again,
> ivtv1 at 5:00 and 6:00 on the 27th were also silent. Once it goes bad,
> it stays bad, it would seem.
>
> Jun 26 05:00:07 wtvq kernel: ivtv1: All encoder VBI stream buffers are
> full. Dropping data.
> Jun 26 05:00:07 wtvq kernel: ivtv1: Cause: the application is not
> reading fast enough.
> Jun 26 06:43:55 wtvq kernel: ivtv0 warning: Invalid PGM index 91164673
> (>= 400)
> Jun 26 06:43:55 wtvq kernel: ivtv0 warning: Invalid PGM index 178891441
> (>= 400)
> Jun 26 06:43:55 wtvq kernel: ivtv0 warning: Invalid PGM index 178891441
> (>= 400)
> Jun 26 12:00:07 wtvq kernel: ivtv1: All encoder VBI stream buffers are
> full. Dropping data.
> Jun 26 12:00:07 wtvq kernel: ivtv1: Cause: the application is not
> reading fast enough.
> Jun 26 18:00:06 wtvq kernel: ivtv1: All encoder VBI stream buffers are
> full. Dropping data.
> Jun 26 18:00:06 wtvq kernel: ivtv1: Cause: the application is not
> reading fast enough.
> Jun 26 23:00:07 wtvq kernel: ivtv0: All encoder VBI stream buffers are
> full. Dropping data.
> Jun 26 23:00:07 wtvq kernel: ivtv0: Cause: the application is not
> reading fast enough.
> Jun 26 23:00:07 wtvq kernel: ivtv1: All encoder VBI stream buffers are
> full. Dropping data.
> Jun 26 23:00:07 wtvq kernel: ivtv1: Cause: the application is not
> reading fast enough.
> Jun 27 05:00:07 wtvq kernel: ivtv1: All encoder VBI stream buffers are
> full. Dropping data.
> Jun 27 05:00:07 wtvq kernel: ivtv1: Cause: the application is not
> reading fast enough.
> Jun 27 06:00:06 wtvq kernel: ivtv0: All encoder VBI stream buffers are
> full. Dropping data.
> Jun 27 06:00:06 wtvq kernel: ivtv0: Cause: the application is not
> reading fast enough.
> Jun 27 06:00:06 wtvq kernel: ivtv1: All encoder VBI stream buffers are
> full. Dropping data.
> Jun 27 06:00:06 wtvq kernel: ivtv1: Cause: the application is not
> reading fast enough.
>
>
> Thanks for any help you can provide.
>
> Cyrus
>
>
>
>
>
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel
>



_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


lists at rooseveltmedia

Jun 27, 2007, 8:48 AM

Post #3 of 25 (9770 views)
Permalink
Re: spontaneous muting [In reply to]
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).
>
> Regards,
>
> Hans
>
> PS: Thank you for the donation! Much appreciated.
>
>
>> After a few days of recording dozens of 1-hour programs on a PVR-500
>> (usually simultaneous and one-after-another), one of the ivtv devices
>> will go silent. It'll record a show (and all subsequent shows on that
>> tuner) with silent audio until the system is rebooted. The recordings on
>> the other device are unaffected.
>>
>> Under a normal debug level, nothing shows up in the kernel logs that
>> would indicate a problem.
>>
>> Here is my device status AFTER the bug:
>>
>> (in this case, ivtv1 was the one that went silent, not ivtv0 -- not sure
>> if there's a pattern that it's always ivtv1)
>>
>> [root [at] wtv cyrus]# v4l2-ctl --log-status --device=/dev/video0
>>
>> Status Log:
>>
>> ivtv0: ================= START STATUS CARD #0 =================
>> tveeprom 2-0050: Hauppauge model 23552, rev E587, serial# 8363157
>> tveeprom 2-0050: tuner model is Samsung TCPN 2121P30A (idx 87, type 70)
>> tveeprom 2-0050: TV standards NTSC(M) (eeprom 0x08)
>> tveeprom 2-0050: second tuner model is Philips TEA5768HL FM Radio
>> (idx 101, type 62)
>> tveeprom 2-0050: audio processor is CX25843 (idx 37)
>> tveeprom 2-0050: decoder processor is CX25843 (idx 30)
>> tveeprom 2-0050: has radio, has no IR receiver, has no IR transmitter
>> tuner 2-0060: Tuner mode: undefined
>> tuner 2-0060: Frequency: 0.00 MHz
>> tuner 2-0060: Standard: 0x00000000
>> tuner 2-0061: Tuner mode: analog TV
>> tuner 2-0061: Frequency: 175.25 MHz
>> tuner 2-0061: Standard: 0x00001000
>> cx25840 2-0044: Video signal: present
>> cx25840 2-0044: Detected format: NTSC-M
>> cx25840 2-0044: Specified standard: NTSC-M
>> cx25840 2-0044: Specified video input: Composite 7
>> cx25840 2-0044: Specified audioclock freq: 48000 Hz
>> cx25840 2-0044: Detected audio mode: stereo
>> cx25840 2-0044: Detected audio standard: BTSC
>> cx25840 2-0044: Audio muted: no
>> cx25840 2-0044: Audio microcontroller: running
>> cx25840 2-0044: Configured audio standard: automatic detection
>> cx25840 2-0044: Configured audio system: BTSC
>> cx25840 2-0044: Specified audio input: Tuner (In8)
>> cx25840 2-0044: Preferred audio mode: stereo
>> wm8775 2-001b: Input: 2
>> ivtv0: Video Input: Tuner 1
>> ivtv0: Audio Input: Tuner 1
>> ivtv0: Tuner: TV
>> ivtv0: Stream: MPEG-2 Program Stream
>> ivtv0: VBI Format: No VBI
>> ivtv0: Video: 720x480, 30 fps
>> ivtv0: Video: MPEG-2, 4x3, Variable Bitrate, 6000000, Peak 8000000
>> ivtv0: Video: GOP Size 15, 2 B-Frames, GOP Closure, No 3:2 Pulldown
>> ivtv0: Audio: 48 kHz, Layer II, 224 kbps, Stereo, No Emphasis, No CRC
>> ivtv0: Spatial Filter: Manual, Luma 1D Horizontal, Chroma 1D
>> Horizontal, 0
>> ivtv0: Temporal Filter: Manual, 8
>> ivtv0: Median Filter: Off, Luma [0, 255], Chroma [0, 255]
>> ivtv0: Status flags: 0x00000000
>> ivtv0: Stream encoder MPEG: status 0x0000, 0% of 4096 KiB (128
>> buffers) in use
>> ivtv0: Stream encoder YUV: status 0x0000, 0% of 2046 KiB (194
>> buffers) in use
>> ivtv0: Stream encoder VBI: status 0x0000, 0% of 1023 KiB (60 buffers)
>> in use
>> ivtv0: Stream encoder PCM audio: status 0x0000, 0% of 1021 KiB (227
>> buffers) in use
>> ivtv0: Read MPEG/VBI: 2929000448/0 bytes
>> ivtv0: ================== END STATUS CARD #0 ==================
>>
>> [root [at] wtv cyrus]# v4l2-ctl --log-status --device=/dev/video1
>>
>> Status Log:
>>
>> ivtv1: ================= START STATUS CARD #1 =================
>> tveeprom 3-0050: Hauppauge model 23552, rev E587, serial# 8363157
>> tveeprom 3-0050: tuner model is Samsung TCPN 2121P30A (idx 87, type 70)
>> tveeprom 3-0050: TV standards NTSC(M) (eeprom 0x08)
>> tveeprom 3-0050: second tuner model is Philips TEA5768HL FM Radio
>> (idx 101, type 62)
>> tveeprom 3-0050: audio processor is CX25843 (idx 37)
>> tveeprom 3-0050: decoder processor is CX25843 (idx 30)
>> tveeprom 3-0050: has radio, has no IR receiver, has no IR transmitter
>> tuner 3-0061: Tuner mode: analog TV
>> tuner 3-0061: Frequency: 193.25 MHz
>> tuner 3-0061: Standard: 0x00001000
>> cx25840 3-0044: Video signal: present
>> cx25840 3-0044: Detected format: NTSC-M
>> cx25840 3-0044: Specified standard: NTSC-M
>> cx25840 3-0044: Specified video input: Composite 7
>> cx25840 3-0044: Specified audioclock freq: 48000 Hz
>> cx25840 3-0044: Detected audio mode: stereo
>> cx25840 3-0044: Detected audio standard: BTSC
>> cx25840 3-0044: Audio muted: yes
>> cx25840 3-0044: Audio microcontroller: running
>> cx25840 3-0044: Configured audio standard: automatic detection
>> cx25840 3-0044: Configured audio system: BTSC
>> cx25840 3-0044: Specified audio input: Tuner (In8)
>> cx25840 3-0044: Preferred audio mode: stereo
>> wm8775 3-001b: Input: 2
>> ivtv1: Video Input: Tuner 1
>> ivtv1: Audio Input: Tuner 1
>> ivtv1: Tuner: TV
>> ivtv1: Stream: MPEG-2 Program Stream
>> ivtv1: VBI Format: No VBI
>> ivtv1: Video: 720x480, 30 fps
>> ivtv1: Video: MPEG-2, 4x3, Variable Bitrate, 6000000, Peak 8000000
>> ivtv1: Video: GOP Size 15, 2 B-Frames, GOP Closure, No 3:2 Pulldown
>> ivtv1: Audio: 48 kHz, Layer II, 224 kbps, Stereo, No Emphasis, No CRC
>> ivtv1: Spatial Filter: Manual, Luma 1D Horizontal, Chroma 1D
>> Horizontal, 0
>> ivtv1: Temporal Filter: Manual, 8
>> ivtv1: Median Filter: Off, Luma [0, 255], Chroma [0, 255]
>> ivtv1: Status flags: 0x00000000
>> ivtv1: Stream encoder MPEG: status 0x0000, 0% of 4096 KiB (128
>> buffers) in use
>> ivtv1: Stream encoder YUV: status 0x0000, 0% of 2046 KiB (194
>> buffers) in use
>> ivtv1: Stream encoder VBI: status 0x0000, 0% of 1023 KiB (60 buffers)
>> in use
>> ivtv1: Stream encoder PCM audio: status 0x0000, 0% of 1021 KiB (227
>> buffers) in use
>> ivtv1: Read MPEG/VBI: 2928836608/0 bytes
>> ivtv1: ================== END STATUS CARD #1 ==================
>>
>> After rebooting to fix the error, I diff'd the two:
>>
>> [cyrus [at] wtv Desktop]$ diff ivtv0_after_error.txt ivtv0_before_error.txt
>> 16c16
>> < tuner 2-0061: Frequency: 175.25 MHz
>> ---
>> > tuner 2-0061: Frequency: 67.25 MHz
>> 49c49
>> < ivtv0: Read MPEG/VBI: 2929000448/0 bytes
>> ---
>> > ivtv0: Read MPEG/VBI: 0/0 bytes
>>
>> [cyrus [at] wtv 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?

Cyrus


>> This is the error log, but the error started at June 26 23:00 so it
>> doesn't make sense. ivtv1 at 5:00, 12:00 and 18:00 on the 26th were all
>> fine. The only thing I see at the critical time (23:00 on the 26th) was
>> that ivtv0 and ivtv1 both messed up at the same time. I'll try to get
>> better error messages when I reboot and reset the debug level. Again,
>> ivtv1 at 5:00 and 6:00 on the 27th were also silent. Once it goes bad,
>> it stays bad, it would seem.
>>
>> Jun 26 05:00:07 wtvq kernel: ivtv1: All encoder VBI stream buffers are
>> full. Dropping data.
>> Jun 26 05:00:07 wtvq kernel: ivtv1: Cause: the application is not
>> reading fast enough.
>> Jun 26 06:43:55 wtvq kernel: ivtv0 warning: Invalid PGM index 91164673
>> (>= 400)
>> Jun 26 06:43:55 wtvq kernel: ivtv0 warning: Invalid PGM index 178891441
>> (>= 400)
>> Jun 26 06:43:55 wtvq kernel: ivtv0 warning: Invalid PGM index 178891441
>> (>= 400)
>> Jun 26 12:00:07 wtvq kernel: ivtv1: All encoder VBI stream buffers are
>> full. Dropping data.
>> Jun 26 12:00:07 wtvq kernel: ivtv1: Cause: the application is not
>> reading fast enough.
>> Jun 26 18:00:06 wtvq kernel: ivtv1: All encoder VBI stream buffers are
>> full. Dropping data.
>> Jun 26 18:00:06 wtvq kernel: ivtv1: Cause: the application is not
>> reading fast enough.
>> Jun 26 23:00:07 wtvq kernel: ivtv0: All encoder VBI stream buffers are
>> full. Dropping data.
>> Jun 26 23:00:07 wtvq kernel: ivtv0: Cause: the application is not
>> reading fast enough.
>> Jun 26 23:00:07 wtvq kernel: ivtv1: All encoder VBI stream buffers are
>> full. Dropping data.
>> Jun 26 23:00:07 wtvq kernel: ivtv1: Cause: the application is not
>> reading fast enough.
>> Jun 27 05:00:07 wtvq kernel: ivtv1: All encoder VBI stream buffers are
>> full. Dropping data.
>> Jun 27 05:00:07 wtvq kernel: ivtv1: Cause: the application is not
>> reading fast enough.
>> Jun 27 06:00:06 wtvq kernel: ivtv0: All encoder VBI stream buffers are
>> full. Dropping data.
>> Jun 27 06:00:06 wtvq kernel: ivtv0: Cause: the application is not
>> reading fast enough.
>> Jun 27 06:00:06 wtvq kernel: ivtv1: All encoder VBI stream buffers are
>> full. Dropping data.
>> Jun 27 06:00:06 wtvq kernel: ivtv1: Cause: the application is not
>> reading fast enough.
>>
>>
>> Thanks for any help you can provide.
>>
>> Cyrus
>>
>>
>>
>>
>>
>> _______________________________________________
>> ivtv-devel mailing list
>> ivtv-devel [at] ivtvdriver
>> http://ivtvdriver.org/mailman/listinfo/ivtv-devel
>>
>>
>
>
>
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel
>
>
>


_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


hverkuil at xs4all

Jun 27, 2007, 8:52 AM

Post #4 of 25 (9766 views)
Permalink
Re: spontaneous muting [In reply to]
> 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 ...

>>> [cyrus [at] wtv 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
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


lists at rooseveltmedia

Jun 27, 2007, 7:33 PM

Post #5 of 25 (9751 views)
Permalink
Re: spontaneous muting [In reply to]
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 ...
>
>
>>>> [cyrus [at] wtv 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.

[cyrus [at] newkoal ~]$ v4l2-ctl -C mute --device=/dev/video0
mute: 1
[cyrus [at] newkoal ~]$ v4l2-ctl -C mute --device=/dev/video1
mute: 1
[cyrus [at] newkoal ~]$ v4l2-ctl -C mute --device=/dev/video2
mute: 0

Unmuting doesn't work:
[root [at] newkoal cyrus]# v4l2-ctl -c mute=0 --device=/dev/video0
[root [at] newkoal 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.



_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


hverkuil at xs4all

Jun 27, 2007, 11:46 PM

Post #6 of 25 (9735 views)
Permalink
Re: spontaneous muting [In reply to]
> 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 ...
>>
>>
>>>>> [cyrus [at] wtv 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.
>
> [cyrus [at] newkoal ~]$ v4l2-ctl -C mute --device=/dev/video0
> mute: 1
> [cyrus [at] newkoal ~]$ v4l2-ctl -C mute --device=/dev/video1
> mute: 1
> [cyrus [at] newkoal ~]$ v4l2-ctl -C mute --device=/dev/video2
> mute: 0
>
> Unmuting doesn't work:
> [root [at] newkoal cyrus]# v4l2-ctl -c mute=0 --device=/dev/video0
> [root [at] newkoal 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
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


ivshade at bredband

Jun 28, 2007, 1:21 PM

Post #7 of 25 (9736 views)
Permalink
Re: spontaneous muting [In reply to]
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 ...
> >>
> >>
> >>>>> [cyrus [at] wtv 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.
> >
> > [cyrus [at] newkoal ~]$ v4l2-ctl -C mute --device=/dev/video0
> > mute: 1
> > [cyrus [at] newkoal ~]$ v4l2-ctl -C mute --device=/dev/video1
> > mute: 1
> > [cyrus [at] newkoal ~]$ v4l2-ctl -C mute --device=/dev/video2
> > mute: 0
> >
> > Unmuting doesn't work:
> > [root [at] newkoal cyrus]# v4l2-ctl -c mute=0 --device=/dev/video0
> > [root [at] newkoal 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
> ivtv-devel [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel


_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


j at bitron

Jul 8, 2007, 12:30 PM

Post #8 of 25 (9662 views)
Permalink
Re: spontaneous muting [In reply to]
On Thu, 2007-06-28 at 22:21 +0200, ivshade wrote:
> 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.

The same here, also with a PVR-350 card - never had the issue with the
PVR-150 in the same computer, if I remember correctly. I don't see
anything suspicious in the log and the mute setting is not enabled.

# v4l2-ctl -d /dev/video1 -C mute
mute: 0

Only a restart seems to help. I'm using ivtv 0.10.3 on a 2.6.21.5 x86
system here with MythTV.

Jürg


_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


hverkuil at xs4all

Jul 10, 2007, 2:21 PM

Post #9 of 25 (9629 views)
Permalink
Re: spontaneous muting [In reply to]
On Thursday 28 June 2007 22:21:00 ivshade wrote:
> 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

Fredrik,

When you have a muted channel, can you post the output
of 'v4l2-ctl --log-status'? Since the pvr350 has a completely different
chip to handle audio compared to the pvr500 this is rather surprising.

Are there certain circumstances where this happens?

Thanks,

Hans

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


ivshade at bredband

Aug 13, 2007, 1:19 AM

Post #10 of 25 (9425 views)
Permalink
Re: spontaneous muting [In reply to]
Hi.
Hope this is still an topic.
I finally got another mute, so here is the requested output.

tux ~ # v4l2-ctl -d /dev/video2 --log-status

Status Log:

ivtv0: ================= START STATUS CARD #0 =================
tveeprom 4-0050: Hauppauge model 48134, rev I121, serial# 6183422
tveeprom 4-0050: tuner model is Philips FM1216 (idx 21, type 5)
tveeprom 4-0050: TV standards PAL(B/G) (eeprom 0x04)
tveeprom 4-0050: audio processor is MSP4418 (idx 25)
tveeprom 4-0050: decoder processor is SAA7115 (idx 19)
tveeprom 4-0050: has radio, has IR receiver, has no IR transmitter
tuner 4-0061: Tuner mode: analog TV
tuner 4-0061: Frequency: 217.25 MHz
tuner 4-0061: Standard: 0x000000ff
saa7115 4-0021: Audio frequency: 48000 Hz
saa7115 4-0021: Input: Composite 4
saa7115 4-0021: Video signal: broadcast/DVD
saa7115 4-0021: Frequency: 50 Hz
saa7115 4-0021: Detected format: PAL
saa7115 4-0021: Width, Height: 720, 576
saa7127 4-0044: Standard: 50 Hz
saa7127 4-0044: Input: normal
saa7127 4-0044: Output: S-Video + Composite
saa7127 4-0044: WSS: disabled
saa7127 4-0044: VPS: disabled
saa7127 4-0044: CC: disabled
msp3400 4-0040: MSP4418G-A2 rev1 = 0x0117 rev2 = 0x1242
msp3400 4-0040: Audio: volume 58950
msp3400 4-0040: Standard: 5.5/5.74 B/G Dual FM-Stereo (mono)
msp3400 4-0040: Audmode: 0x0003
msp3400 4-0040: Routing: 0x00000000 (input) 0x00000044 (output)
msp3400 4-0040: ACB: 0x0c00
ivtv0: Video Input: Tuner 1
ivtv0: Audio Input: Tuner 1
ivtv0: Video Output: S-Video + Composite
ivtv0: Audio Output: A/V Audio Out
ivtv0: Output Mode: None
ivtv0: Tuner: TV
ivtv0: Stream: MPEG-2 Program Stream
ivtv0: VBI Format: Private packet, IVTV format
ivtv0: Video: 720x576, 25 fps
ivtv0: Video: MPEG-2, 4x3, Variable Bitrate, 6000000, Peak 7200000
ivtv0: Video: GOP Size 12, 2 B-Frames, GOP Closure
ivtv0: Audio: 48 kHz, Layer II, 384 kbps, Stereo, No Emphasis, No
CRC
ivtv0: Spatial Filter: Manual, Luma 1D Horizontal, Chroma 1D
Horizontal, 0
ivtv0: Temporal Filter: Manual, 8
ivtv0: Median Filter: Off, Luma [0, 255], Chroma [0, 255]
ivtv0: Status flags: 0x000110c0
ivtv0: Stream encoder MPEG: status 0x0118, 1% of 4096 KiB (128
buffers) in use
ivtv0: Stream encoder YUV: status 0x0000, 0% of 2037 KiB (161
buffers) in use
ivtv0: Stream encoder VBI: status 0x0038, 5% of 1023 KiB (40 buffers)
in use
ivtv0: Stream encoder PCM audio: status 0x0000, 0% of 1021 KiB (227
buffers) in use
ivtv0: Stream decoder MPEG: status 0x0000, 0% of 1024 KiB (16
buffers) in use
ivtv0: Stream decoder VBI: status 0x0000, 0% of 1023 KiB (455
buffers) in use
ivtv0: Stream decoder YUV: status 0x0008, 0% of 1012 KiB (20 buffers)
in use
ivtv0: Read MPEG/VBI: 239087136/7878780 bytes
ivtv0: ================== END STATUS CARD #0 ==================


Br Fredrik


On Tue, 2007-07-10 at 23:21 +0200, Hans Verkuil wrote:
> On Thursday 28 June 2007 22:21:00 ivshade wrote:
> > 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
>
> Fredrik,
>
> When you have a muted channel, can you post the output
> of 'v4l2-ctl --log-status'? Since the pvr350 has a completely different
> chip to handle audio compared to the pvr500 this is rather surprising.
>
> Are there certain circumstances where this happens?
>
> Thanks,
>
> Hans


_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


ivshade at bredband

Aug 28, 2007, 12:11 PM

Post #11 of 25 (9338 views)
Permalink
Re: spontaneous muting [In reply to]
Hi.
Here another mute caught in the middle of the act.
What happend? I switched tuner in mythtv. Myth had a bit of thinking and
then decided not to display the pvr-350, but jumped to next one.
After i jumped tuners back to pvr-350, the sound was gone, but picture
with bad ghosting, and i made the dumps below.
Perhaps this is not valid anymore due to old driver? 0.10.3

#dmesg
ivtv0 warning: CX2341X_ENC_STOP_CAPTURE took 38 jiffies (250 per HZ)
ivtv0 warning: Enable video output
ivtv0 warning: Need to adjust to width 544 src_w 544 dst_w 662 src_x 0
dst_x 28
ivtv0 warning: Need to adjust to height 576 src_h 576 dst_h 530 src_y 0
dst_y 22
ivtv0 warning: Source video: Interlaced
ivtv0 warning: Could not get result (CX2341X_ENC_MISC)
ivtv0 warning: Enable video output
ivtv0 warning: Need to adjust to width 720 src_w 720 dst_w 662 src_x 0
dst_x 28
ivtv0 warning: Need to adjust to height 576 src_h 576 dst_h 530 src_y 0
dst_y 22
ivtv0 warning: Source video: Interlaced
ivtv0 warning: CX2341X_ENC_MUTE_AUDIO took 36 jiffies (250 per HZ)
ivtv0 warning: Could not get result (CX2341X_ENC_MISC)
ivtv0 warning: encoder VBI: Couldn't find start of buffer within the
first 256 bytes
ivtv0 warning: CX2341X_ENC_STOP_CAPTURE took 36 jiffies (250 per HZ)

# v4l2-ctl -d /dev/video2 --log-status
Status Log:

ivtv0: ================= START STATUS CARD #0 =================
tveeprom 4-0050: Hauppauge model 48134, rev I121, serial# 6183422
tveeprom 4-0050: tuner model is Philips FM1216 (idx 21, type 5)
tveeprom 4-0050: TV standards PAL(B/G) (eeprom 0x04)
tveeprom 4-0050: audio processor is MSP4418 (idx 25)
tveeprom 4-0050: decoder processor is SAA7115 (idx 19)
tveeprom 4-0050: has radio, has IR receiver, has no IR transmitter
tuner 4-0061: Tuner mode: analog TV
tuner 4-0061: Frequency: 217.25 MHz
tuner 4-0061: Standard: 0x000000ff
saa7115 4-0021: Audio frequency: 48000 Hz
saa7115 4-0021: Input: Composite 4
saa7115 4-0021: Video signal: broadcast/DVD
saa7115 4-0021: Frequency: 50 Hz
saa7115 4-0021: Detected format: PAL
saa7115 4-0021: Width, Height: 720, 576
saa7127 4-0044: Standard: 50 Hz
saa7127 4-0044: Input: normal
saa7127 4-0044: Output: S-Video + Composite
saa7127 4-0044: WSS: disabled
saa7127 4-0044: VPS: disabled
saa7127 4-0044: CC: disabled
msp3400 4-0040: MSP4418G-A2 rev1 = 0x0117 rev2 = 0x1242
msp3400 4-0040: Audio: volume 58950
msp3400 4-0040: Standard: 5.5/5.74 B/G Dual FM-Stereo (mono)
msp3400 4-0040: Audmode: 0x0003
msp3400 4-0040: Routing: 0x00000000 (input) 0x00000044 (output)
msp3400 4-0040: ACB: 0x0c00
ivtv0: Video Input: Tuner 1
ivtv0: Audio Input: Tuner 1
ivtv0: Video Output: S-Video + Composite
ivtv0: Audio Output: A/V Audio Out
ivtv0: Output Mode: None
ivtv0: Tuner: TV
ivtv0: Stream: MPEG-2 Program Stream
ivtv0: VBI Format: Private packet, IVTV format
ivtv0: Video: 720x576, 25 fps
ivtv0: Video: MPEG-2, 4x3, Variable Bitrate, 6000000, Peak 7200000
ivtv0: Video: GOP Size 12, 2 B-Frames, GOP Closure
ivtv0: Audio: 48 kHz, Layer II, 384 kbps, Stereo, No Emphasis, No
CRC
ivtv0: Spatial Filter: Manual, Luma 1D Horizontal, Chroma 1D
Horizontal, 0
ivtv0: Temporal Filter: Manual, 8
ivtv0: Median Filter: Off, Luma [0, 255], Chroma [0, 255]
ivtv0: Status flags: 0x00010080
ivtv0: Stream encoder MPEG: status 0x0000, 0% of 4096 KiB (128
buffers) in use
ivtv0: Stream encoder YUV: status 0x0000, 0% of 2037 KiB (161
buffers) in use
ivtv0: Stream encoder VBI: status 0x0000, 0% of 1023 KiB (40 buffers)
in use
ivtv0: Stream encoder PCM audio: status 0x0000, 0% of 1021 KiB (227
buffers) in use
ivtv0: Stream decoder MPEG: status 0x0000, 0% of 1024 KiB (16
buffers) in use
ivtv0: Stream decoder VBI: status 0x0000, 0% of 1023 KiB (455
buffers) in use
ivtv0: Stream decoder YUV: status 0x0000, 0% of 1012 KiB (20 buffers)
in use
ivtv0: Read MPEG/VBI: 9354688/311380 bytes
ivtv0: ================== END STATUS CARD #0 ==================

/Br Fredrik


On Mon, 2007-08-13 at 10:19 +0200, ivshade wrote:
> Hi.
> Hope this is still an topic.
> I finally got another mute, so here is the requested output.
>
> tux ~ # v4l2-ctl -d /dev/video2 --log-status
>
> Status Log:
>
> ivtv0: ================= START STATUS CARD #0 =================
> tveeprom 4-0050: Hauppauge model 48134, rev I121, serial# 6183422
> tveeprom 4-0050: tuner model is Philips FM1216 (idx 21, type 5)
> tveeprom 4-0050: TV standards PAL(B/G) (eeprom 0x04)
> tveeprom 4-0050: audio processor is MSP4418 (idx 25)
> tveeprom 4-0050: decoder processor is SAA7115 (idx 19)
> tveeprom 4-0050: has radio, has IR receiver, has no IR transmitter
> tuner 4-0061: Tuner mode: analog TV
> tuner 4-0061: Frequency: 217.25 MHz
> tuner 4-0061: Standard: 0x000000ff
> saa7115 4-0021: Audio frequency: 48000 Hz
> saa7115 4-0021: Input: Composite 4
> saa7115 4-0021: Video signal: broadcast/DVD
> saa7115 4-0021: Frequency: 50 Hz
> saa7115 4-0021: Detected format: PAL
> saa7115 4-0021: Width, Height: 720, 576
> saa7127 4-0044: Standard: 50 Hz
> saa7127 4-0044: Input: normal
> saa7127 4-0044: Output: S-Video + Composite
> saa7127 4-0044: WSS: disabled
> saa7127 4-0044: VPS: disabled
> saa7127 4-0044: CC: disabled
> msp3400 4-0040: MSP4418G-A2 rev1 = 0x0117 rev2 = 0x1242
> msp3400 4-0040: Audio: volume 58950
> msp3400 4-0040: Standard: 5.5/5.74 B/G Dual FM-Stereo (mono)
> msp3400 4-0040: Audmode: 0x0003
> msp3400 4-0040: Routing: 0x00000000 (input) 0x00000044 (output)
> msp3400 4-0040: ACB: 0x0c00
> ivtv0: Video Input: Tuner 1
> ivtv0: Audio Input: Tuner 1
> ivtv0: Video Output: S-Video + Composite
> ivtv0: Audio Output: A/V Audio Out
> ivtv0: Output Mode: None
> ivtv0: Tuner: TV
> ivtv0: Stream: MPEG-2 Program Stream
> ivtv0: VBI Format: Private packet, IVTV format
> ivtv0: Video: 720x576, 25 fps
> ivtv0: Video: MPEG-2, 4x3, Variable Bitrate, 6000000, Peak 7200000
> ivtv0: Video: GOP Size 12, 2 B-Frames, GOP Closure
> ivtv0: Audio: 48 kHz, Layer II, 384 kbps, Stereo, No Emphasis, No
> CRC
> ivtv0: Spatial Filter: Manual, Luma 1D Horizontal, Chroma 1D
> Horizontal, 0
> ivtv0: Temporal Filter: Manual, 8
> ivtv0: Median Filter: Off, Luma [0, 255], Chroma [0, 255]
> ivtv0: Status flags: 0x000110c0
> ivtv0: Stream encoder MPEG: status 0x0118, 1% of 4096 KiB (128
> buffers) in use
> ivtv0: Stream encoder YUV: status 0x0000, 0% of 2037 KiB (161
> buffers) in use
> ivtv0: Stream encoder VBI: status 0x0038, 5% of 1023 KiB (40 buffers)
> in use
> ivtv0: Stream encoder PCM audio: status 0x0000, 0% of 1021 KiB (227
> buffers) in use
> ivtv0: Stream decoder MPEG: status 0x0000, 0% of 1024 KiB (16
> buffers) in use
> ivtv0: Stream decoder VBI: status 0x0000, 0% of 1023 KiB (455
> buffers) in use
> ivtv0: Stream decoder YUV: status 0x0008, 0% of 1012 KiB (20 buffers)
> in use
> ivtv0: Read MPEG/VBI: 239087136/7878780 bytes
> ivtv0: ================== END STATUS CARD #0 ==================
>
>
> Br Fredrik
>
>
> On Tue, 2007-07-10 at 23:21 +0200, Hans Verkuil wrote:
> > On Thursday 28 June 2007 22:21:00 ivshade wrote:
> > > 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
> >
> > Fredrik,
> >
> > When you have a muted channel, can you post the output
> > of 'v4l2-ctl --log-status'? Since the pvr350 has a completely different
> > chip to handle audio compared to the pvr500 this is rather surprising.
> >
> > Are there certain circumstances where this happens?
> >
> > Thanks,
> >
> > Hans
>
>
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel


_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


hverkuil at xs4all

Aug 28, 2007, 12:54 PM

Post #12 of 25 (9320 views)
Permalink
Re: spontaneous muting [In reply to]
On Tuesday 28 August 2007 21:11:56 ivshade wrote:
> Hi.
> Here another mute caught in the middle of the act.
> What happend? I switched tuner in mythtv. Myth had a bit of thinking
> and then decided not to display the pvr-350, but jumped to next one.
> After i jumped tuners back to pvr-350, the sound was gone, but
> picture with bad ghosting, and i made the dumps below.
> Perhaps this is not valid anymore due to old driver? 0.10.3

I afraid it's hard for me to do anything with this. You would have to
upgrade to the latest v4l-dvb repository to test this. There have been
so many changes and fixes lately that it is perfectly possible that
this issue has been solved.

Regards,

Hans

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


rich.kadel at appeligo

Aug 28, 2007, 3:41 PM

Post #13 of 25 (9327 views)
Permalink
Re: spontaneous muting [In reply to]
I'm seeing this as well. In fact, I'm seeing two problems that seem to
develop over time. From what I've seen, first I lose color. After
several hours (maybe a day or so...I'm not sure), I start getting
nothing but B&W video with a little red ghosting on the left edge. Then
after a while longer (days?) I lose sound. I'm using a PVR-500 (ivtv2
and ivtv3) for this. I noticed the color problem on both devices, but
the muting seemed to be a problem only on ivtv3. I rebooted and got my
color and sound back.

Because this takes so long to develop, I don't have well established
pattern yet, but since this problem was reported, I thought I should go
ahead and tell you about the color loss issue if related.

Aug 28 13:17:26 appeligo2 kernel: ivtv: Start initialization, version 1.1.0
Aug 28 13:17:27 appeligo2 kernel: ivtv0: Initializing card #0
Aug 28 13:17:28 appeligo2 kernel: ivtv0: Autodetected Hauppauge card
(cx23416 based)
Aug 28 13:17:29 appeligo2 kernel: ACPI: PCI Interrupt 0000:02:03.0[A] ->
GSI 19 (level, low) -> IRQ 18
Aug 28 13:17:29 appeligo2 kernel: ivtv0: Unreasonably low latency timer,
setting to 64 (was 32)
Aug 28 13:17:30 appeligo2 kernel: tveeprom 1-0050: Hauppauge model
26032, rev C199, serial# 8358972
Aug 28 13:17:30 appeligo2 kernel: tveeprom 1-0050: tuner model is TCL
2002N 5H (idx 99, type 50)
Aug 28 13:17:31 appeligo2 kernel: tveeprom 1-0050: TV standards NTSC(M)
(eeprom 0x08)
Aug 28 13:17:32 appeligo2 kernel: tveeprom 1-0050: audio processor is
CX25841 (idx 35)
Aug 28 13:17:33 appeligo2 kernel: tveeprom 1-0050: decoder processor is
CX25841 (idx 28)
Aug 28 13:17:33 appeligo2 kernel: tveeprom 1-0050: has no radio, has IR
receiver, has IR transmitter
Aug 28 13:17:34 appeligo2 kernel: ivtv0: Autodetected Hauppauge WinTV
PVR-150
Aug 28 13:17:35 appeligo2 kernel: ivtv0: Reopen i2c bus for IR-blaster
support
Aug 28 13:17:35 appeligo2 kernel: tuner 1-0061: chip found @ 0xc2 (ivtv
i2c driver #0)
Aug 28 13:17:36 appeligo2 kernel: nvidia: module license 'NVIDIA' taints
kernel.
Aug 28 13:17:37 appeligo2 kernel: cx25840 1-0044: cx25841-23 found @
0x88 (ivtv i2c driver #0)
Aug 28 13:17:37 appeligo2 kernel: wm8775 1-001b: chip found @ 0x36 (ivtv
i2c driver #0)
Aug 28 13:17:38 appeligo2 kernel: tuner 1-0061: type set to 50 (TCL 2002N)
Aug 28 13:17:38 appeligo2 kernel: ivtv0: Registered device video0 for
encoder MPEG (4 MB)
Aug 28 13:17:39 appeligo2 kernel: ivtv0: Registered device video32 for
encoder YUV (2 MB)
Aug 28 13:17:40 appeligo2 kernel: ivtv0: Registered device vbi0 for
encoder VBI (1 MB)
Aug 28 13:17:41 appeligo2 kernel: ivtv0: Registered device video24 for
encoder PCM audio (1 MB)
Aug 28 13:17:42 appeligo2 kernel: ivtv0: Initialized card #0: Hauppauge
WinTV PVR-150
Aug 28 13:17:43 appeligo2 kernel: ivtv1: Initializing card #1
Aug 28 13:17:45 appeligo2 kernel: ivtv1: Autodetected Hauppauge card
(cx23416 based)
Aug 28 13:17:45 appeligo2 kernel: ACPI: PCI Interrupt 0000:02:04.0[A] ->
GSI 16 (level, low) -> IRQ 16
Aug 28 13:17:46 appeligo2 kernel: ivtv1: Unreasonably low latency timer,
setting to 64 (was 32)
Aug 28 13:17:47 appeligo2 kernel: tuner 2-0061: chip found @ 0xc2 (ivtv
i2c driver #1)
Aug 28 13:17:47 appeligo2 kernel: tveeprom 2-0050: Hauppauge model
32062, rev C382, serial# 7812069
Aug 28 13:17:48 appeligo2 kernel: tveeprom 2-0050: tuner model is LG
TAPC H791F (idx 82, type 39)
Aug 28 13:17:48 appeligo2 kernel: tveeprom 2-0050: TV standards NTSC(M)
(eeprom 0x08)
Aug 28 13:17:49 appeligo2 kernel: tveeprom 2-0050: audio processor is
MSP3445 (idx 12)
Aug 28 13:17:49 appeligo2 kernel: tveeprom 2-0050: decoder processor is
SAA7115 (idx 19)
Aug 28 13:17:50 appeligo2 kernel: tveeprom 2-0050: has no radio, has IR
receiver, has no IR transmitter
Aug 28 13:17:50 appeligo2 kernel: ivtv1: Autodetected Hauppauge WinTV
PVR-250
Aug 28 13:17:50 appeligo2 kernel: saa7115 2-0021: saa7115 found
(1f7115d0e100000) @ 0x42 (ivtv i2c driver #1)
Aug 28 13:17:51 appeligo2 kernel: msp3400 2-0040: MSP3445G-B8 found @
0x80 (ivtv i2c driver #1)
Aug 28 13:17:52 appeligo2 kernel: msp3400 2-0040: MSP3445G-B8 supports
radio, mode is autodetect and autoselect
Aug 28 13:17:52 appeligo2 kernel: tuner 2-0061: type set to 39 (LG NTSC
(newer TAPC series))
Aug 28 13:17:53 appeligo2 avahi-daemon[3126]: Found user 'avahi' (UID
70) and group 'avahi' (GID 70).
Aug 28 13:17:53 appeligo2 kernel: ivtv1: Registered device video1 for
encoder MPEG (4 MB)
Aug 28 13:17:53 appeligo2 avahi-daemon[3126]: Successfully dropped root
privileges.
Aug 28 13:17:54 appeligo2 kernel: ivtv1: Registered device video33 for
encoder YUV (2 MB)
Aug 28 13:17:54 appeligo2 avahi-daemon[3126]: avahi-daemon 0.6.16
starting up.
Aug 28 13:17:56 appeligo2 kernel: ivtv1: Registered device vbi1 for
encoder VBI (1 MB)
Aug 28 13:17:56 appeligo2 avahi-daemon[3126]: WARNING: No NSS support
for mDNS detected, consider installing nss-mdns!
Aug 28 13:17:57 appeligo2 kernel: ivtv1: Registered device video25 for
encoder PCM audio (1 MB)
Aug 28 13:17:57 appeligo2 avahi-daemon[3126]: dbus_bus_get(): Failed to
connect to socket /usr/local/var/run/dbus/system_bus_socket: No such
file or directory
Aug 28 13:17:59 appeligo2 kernel: ivtv1: Initialized card #1: Hauppauge
WinTV PVR-250
Aug 28 13:18:00 appeligo2 avahi-daemon[3126]: WARNING: Failed to contact
D-Bus daemon.
Aug 28 13:18:02 appeligo2 kernel: ivtv2: Initializing card #2
Aug 28 13:18:04 appeligo2 kernel: ivtv2: Autodetected Hauppauge card
(cx23416 based)
Aug 28 13:18:06 appeligo2 kernel: ACPI: PCI Interrupt 0000:01:00.0[A] ->
GSI 16 (level, low) -> IRQ 16
Aug 28 13:18:09 appeligo2 kernel: ACPI: PCI Interrupt 0000:00:1b.0[A] ->
GSI 16 (level, low) -> IRQ 16
Aug 28 13:18:10 appeligo2 kernel: ACPI: PCI Interrupt 0000:03:08.0[A] ->
GSI 17 (level, low) -> IRQ 21
Aug 28 13:18:10 appeligo2 kernel: ivtv2: Unreasonably low latency timer,
setting to 64 (was 32)
Aug 28 13:18:11 appeligo2 kernel: tuner 3-0043: chip found @ 0x86 (ivtv
i2c driver #2)
Aug 28 13:18:12 appeligo2 kernel: tda9887 3-0043: tda988[5/6/7] found @
0x43 (tuner)
Aug 28 13:18:12 appeligo2 kernel: tuner 3-0060: TEA5767 detected.
Aug 28 13:18:13 appeligo2 kernel: tuner 3-0060: chip found @ 0xc0 (ivtv
i2c driver #2)
Aug 28 13:18:13 appeligo2 kernel: tuner 3-0060: type set to 62 (Philips
TEA5767HN FM Radio)
Aug 28 13:18:14 appeligo2 kernel: tuner 3-0061: chip found @ 0xc2 (ivtv
i2c driver #2)
Aug 28 13:18:14 appeligo2 kernel: cx25840 3-0044: cx25843-24 found @
0x88 (ivtv i2c driver #2)
Aug 28 13:18:14 appeligo2 kernel: wm8775 3-001b: chip found @ 0x36 (ivtv
i2c driver #2)
Aug 28 13:18:14 appeligo2 kernel: hda_codec: Unknown model for ALC882,
trying auto-probe from BIOS...
Aug 28 13:18:15 appeligo2 kernel: tveeprom 3-0050: Hauppauge model
23552, rev E692, serial# 10324397
Aug 28 13:18:15 appeligo2 kernel: tveeprom 3-0050: tuner model is
Philips FQ1236A MK4 (idx 92, type 57)
Aug 28 13:18:15 appeligo2 kernel: tveeprom 3-0050: TV standards NTSC(M)
(eeprom 0x08)
Aug 28 13:18:15 appeligo2 kernel: tveeprom 3-0050: second tuner model is
Philips TEA5768HL FM Radio (idx 101, type 62)
Aug 28 13:18:15 appeligo2 kernel: tveeprom 3-0050: audio processor is
CX25843 (idx 37)
Aug 28 13:18:15 appeligo2 kernel: tveeprom 3-0050: decoder processor is
CX25843 (idx 30)
Aug 28 13:18:15 appeligo2 kernel: tveeprom 3-0050: has radio, has no IR
receiver, has no IR transmitter
Aug 28 13:18:15 appeligo2 kernel: ivtv2: Autodetected WinTV PVR 500
(unit #1)
Aug 28 13:18:15 appeligo2 kernel: tuner 3-0061: type set to 57 (Philips
FQ1236A MK4)
Aug 28 13:18:15 appeligo2 kernel: ivtv2: Registered device video2 for
encoder MPEG (4 MB)
Aug 28 13:18:15 appeligo2 kernel: ivtv2: Registered device video34 for
encoder YUV (2 MB)
Aug 28 13:18:15 appeligo2 kernel: ivtv2: Registered device vbi2 for
encoder VBI (1 MB)
Aug 28 13:18:15 appeligo2 kernel: ivtv2: Registered device video26 for
encoder PCM audio (1 MB)
Aug 28 13:18:15 appeligo2 kernel: ivtv2: Registered device radio2 for
encoder radio
Aug 28 13:18:15 appeligo2 kernel: ivtv2: Initialized card #2: WinTV PVR
500 (unit #1)
Aug 28 13:18:15 appeligo2 kernel: ivtv3: Initializing card #3
Aug 28 13:18:15 appeligo2 kernel: ivtv3: Autodetected Hauppauge card
(cx23416 based)
Aug 28 13:18:15 appeligo2 kernel: ACPI: PCI Interrupt 0000:03:09.0[A] ->
GSI 18 (level, low) -> IRQ 19
Aug 28 13:18:15 appeligo2 kernel: ivtv3: Unreasonably low latency timer,
setting to 64 (was 32)
Aug 28 13:18:15 appeligo2 kernel: tuner 4-0043: chip found @ 0x86 (ivtv
i2c driver #3)
Aug 28 13:18:15 appeligo2 kernel: tda9887 4-0043: tda988[5/6/7] found @
0x43 (tuner)
Aug 28 13:18:15 appeligo2 kernel: tuner 4-0061: chip found @ 0xc2 (ivtv
i2c driver #3)
Aug 28 13:18:15 appeligo2 kernel: cx25840 4-0044: cx25843-24 found @
0x88 (ivtv i2c driver #3)
Aug 28 13:18:15 appeligo2 kernel: wm8775 4-001b: chip found @ 0x36 (ivtv
i2c driver #3)
Aug 28 13:18:15 appeligo2 kernel: tveeprom 4-0050: Hauppauge model
23552, rev E692, serial# 10324397
Aug 28 13:18:15 appeligo2 kernel: tveeprom 4-0050: tuner model is
Philips FQ1236A MK4 (idx 92, type 57)
Aug 28 13:18:15 appeligo2 kernel: tveeprom 4-0050: TV standards NTSC(M)
(eeprom 0x08)
Aug 28 13:18:15 appeligo2 kernel: tveeprom 4-0050: second tuner model is
Philips TEA5768HL FM Radio (idx 101, type 62)
Aug 28 13:18:15 appeligo2 kernel: tveeprom 4-0050: audio processor is
CX25843 (idx 37)
Aug 28 13:18:15 appeligo2 kernel: tveeprom 4-0050: decoder processor is
CX25843 (idx 30)
Aug 28 13:18:15 appeligo2 kernel: tveeprom 4-0050: has radio, has no IR
receiver, has no IR transmitter
Aug 28 13:18:15 appeligo2 kernel: ivtv3: Correcting tveeprom data: no
radio present on second unit
Aug 28 13:18:15 appeligo2 kernel: ivtv3: Autodetected WinTV PVR 500
(unit #2)
Aug 28 13:18:15 appeligo2 kernel: tuner 4-0061: type set to 57 (Philips
FQ1236A MK4)
Aug 28 13:18:15 appeligo2 kernel: ivtv3: Registered device video3 for
encoder MPEG (4 MB)
Aug 28 13:18:15 appeligo2 kernel: ivtv3: Registered device video35 for
encoder YUV (2 MB)
Aug 28 13:18:15 appeligo2 kernel: ivtv3: Registered device vbi3 for
encoder VBI (1 MB)
Aug 28 13:18:15 appeligo2 kernel: ivtv3: Registered device video27 for
encoder PCM audio (1 MB)
Aug 28 13:18:15 appeligo2 kernel: ivtv3: Initialized card #3: WinTV PVR
500 (unit #2)
Aug 28 13:18:15 appeligo2 kernel: ivtv: End initialization


ivshade wrote:
> Hi.
> Here another mute caught in the middle of the act.
> What happend? I switched tuner in mythtv. Myth had a bit of thinking and
> then decided not to display the pvr-350, but jumped to next one.
> After i jumped tuners back to pvr-350, the sound was gone, but picture
> with bad ghosting, and i made the dumps below.
> Perhaps this is not valid anymore due to old driver? 0.10.3
>
>

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


hverkuil at xs4all

Aug 29, 2007, 3:09 AM

Post #14 of 25 (9339 views)
Permalink
Re: spontaneous muting [In reply to]
> I'm seeing this as well. In fact, I'm seeing two problems that seem to
> develop over time. From what I've seen, first I lose color. After
> several hours (maybe a day or so...I'm not sure), I start getting
> nothing but B&W video with a little red ghosting on the left edge. Then
> after a while longer (days?) I lose sound. I'm using a PVR-500 (ivtv2
> and ivtv3) for this. I noticed the color problem on both devices, but
> the muting seemed to be a problem only on ivtv3. I rebooted and got my
> color and sound back.
>
> Because this takes so long to develop, I don't have well established
> pattern yet, but since this problem was reported, I thought I should go
> ahead and tell you about the color loss issue if related.

Could this be a cooling problem? Especially since it develops over time.

Regards,

Hans


_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


rich.kadel at appeligo

Aug 29, 2007, 8:55 AM

Post #15 of 25 (9310 views)
Permalink
Re: spontaneous muting [In reply to]
No, I'm certain it's not heat related. I started collecting video about a
week ago on two servers that have been up 24/7 for months in a controlled
colocation facility, and the problem developed over the next few days. I
was using tuners that had been used for VBI collection up until that point.

FYI, I'm trying a couple of things now to see if I get better results. Both
of my production servers have multiple PVR-500s (3 in one and 4 in the
other), with most recording VBI. Now I dedicate one tuner per server to
video capture (and no VBI). I saw the color problem on both servers plus on
my development server. So here's what I'm trying:

1. Moving the video from ivtv5 and ivtv7 to ivtv0. (Cyrus A reported muting
problems with the second tuner on a PVR-500, but not the first, and I THINK
that's what I noticed)
2. Closing the device when I don't need to capture video. (Previously, my
software continually read from the device and piped output only when
needed.) I'm only recording short clips based on an algorithm, so this will
open and close the device many times per hour. I don't know if this will
help, but the problem only developed after I started reading from the video
device continually for hours or days, which I've never done before.
3. Creating a convenient way for me to monitor the results by server and
time. I should be able to provide clearer information on the symptoms if
this occurs again.

It's been 12 hours, and so far it still looks good. But I need a few days
to be sure.

--

Rich Kadel
Appeligo, Inc.
(858) 433-1747
www.appeligo.com


-----Original Message-----
From: ivtv-devel-bounces [at] ivtvdriver
[mailto:ivtv-devel-bounces [at] ivtvdriver] On Behalf Of Hans Verkuil
Sent: Wednesday, August 29, 2007 3:09 AM
To: Discussion list for development of the IVTV driver
Subject: Re: [ivtv-devel] spontaneous muting

> I'm seeing this as well. In fact, I'm seeing two problems that seem to
> develop over time. From what I've seen, first I lose color. After
> several hours (maybe a day or so...I'm not sure), I start getting
> nothing but B&W video with a little red ghosting on the left edge. Then
> after a while longer (days?) I lose sound. I'm using a PVR-500 (ivtv2
> and ivtv3) for this. I noticed the color problem on both devices, but
> the muting seemed to be a problem only on ivtv3. I rebooted and got my
> color and sound back.
>
> Because this takes so long to develop, I don't have well established
> pattern yet, but since this problem was reported, I thought I should go
> ahead and tell you about the color loss issue if related.

Could this be a cooling problem? Especially since it develops over time.

Regards,

Hans


_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


frank at prumbaum

Aug 31, 2007, 10:03 AM

Post #16 of 25 (9300 views)
Permalink
Re: spontaneous muting [In reply to]
Helo,

just add me, too.
My card (pvr350) has been running fine for over a year (24x7), until
I updated my SuSE with standard updates a few weeks ago. I'm pretty sure
the problem did not exist with kernel 2.6.18.0.1, but now with 2.6.18.0.5 the
sound breaks after 3-15min into recording. It turns on again by
rmmod'ing/modprobing the driver again, but never long enought to record a show
(I was recording daily shows for the last year or so).

I have been using the latest driver releases since and for testing purposes even
reverted to older driver versions (10->9->8) until I was sure it wasn't the last
updates that broke my card's recording abilities.

Since SuSE will soon reach 10.3 with kernel 2.6.22, I am hoping for a stable
system not to far away in the future.

Greetings
Frank Prumbaum

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


rich.kadel at appeligo

Sep 3, 2007, 2:11 PM

Post #17 of 25 (9278 views)
Permalink
Re: spontaneous muting [In reply to]
This seems to be working OK, now that I implemented the changes I described
below.

I do suspect (no certain proof) that reading video from the device
continuously for several hours or days may not be robust. But I don't need
to do that right now.

Thanks,
Rich

--

Rich Kadel
Appeligo, Inc.
(858) 433-1747
www.appeligo.com


-----Original Message-----
From: ivtv-devel-bounces [at] ivtvdriver
[mailto:ivtv-devel-bounces [at] ivtvdriver] On Behalf Of Rich Kadel
Sent: Wednesday, August 29, 2007 8:55 AM
To: 'Discussion list for development of the IVTV driver'
Subject: Re: [ivtv-devel] spontaneous muting

No, I'm certain it's not heat related. I started collecting video about a
week ago on two servers that have been up 24/7 for months in a controlled
colocation facility, and the problem developed over the next few days. I
was using tuners that had been used for VBI collection up until that point.

FYI, I'm trying a couple of things now to see if I get better results. Both
of my production servers have multiple PVR-500s (3 in one and 4 in the
other), with most recording VBI. Now I dedicate one tuner per server to
video capture (and no VBI). I saw the color problem on both servers plus on
my development server. So here's what I'm trying:

1. Moving the video from ivtv5 and ivtv7 to ivtv0. (Cyrus A reported muting
problems with the second tuner on a PVR-500, but not the first, and I THINK
that's what I noticed)
2. Closing the device when I don't need to capture video. (Previously, my
software continually read from the device and piped output only when
needed.) I'm only recording short clips based on an algorithm, so this will
open and close the device many times per hour. I don't know if this will
help, but the problem only developed after I started reading from the video
device continually for hours or days, which I've never done before.
3. Creating a convenient way for me to monitor the results by server and
time. I should be able to provide clearer information on the symptoms if
this occurs again.

It's been 12 hours, and so far it still looks good. But I need a few days
to be sure.

--

Rich Kadel
Appeligo, Inc.
(858) 433-1747
www.appeligo.com


_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


hverkuil at xs4all

Sep 16, 2007, 4:44 AM

Post #18 of 25 (9165 views)
Permalink
Re: spontaneous muting [In reply to]
On Wednesday 29 August 2007 17:55:02 Rich Kadel wrote:
> No, I'm certain it's not heat related. I started collecting video
> about a week ago on two servers that have been up 24/7 for months in
> a controlled colocation facility, and the problem developed over the
> next few days. I was using tuners that had been used for VBI
> collection up until that point.
>
> FYI, I'm trying a couple of things now to see if I get better
> results. Both of my production servers have multiple PVR-500s (3 in
> one and 4 in the other), with most recording VBI. Now I dedicate one
> tuner per server to video capture (and no VBI). I saw the color
> problem on both servers plus on my development server. So here's
> what I'm trying:
>
> 1. Moving the video from ivtv5 and ivtv7 to ivtv0. (Cyrus A reported
> muting problems with the second tuner on a PVR-500, but not the
> first, and I THINK that's what I noticed)
> 2. Closing the device when I don't need to capture video.
> (Previously, my software continually read from the device and piped
> output only when needed.) I'm only recording short clips based on an
> algorithm, so this will open and close the device many times per
> hour. I don't know if this will help, but the problem only developed
> after I started reading from the video device continually for hours
> or days, which I've never done before. 3. Creating a convenient way
> for me to monitor the results by server and time. I should be able
> to provide clearer information on the symptoms if this occurs again.
>
> It's been 12 hours, and so far it still looks good. But I need a few
> days to be sure.

Have you ever tried switching the channel to another frequency and back
again when the audio/video problems develop? I wonder if the tuner
frequency might be drifting over time. Besides going to B&W does the
amount of noise in the video also increase? I mean, the whole chain of
losing color, then audio muting suggests a tuner issue.

Note that the latest v4l-dvb has better status reporting (you might
already be using it, I don't know). If the cx25841 cannot lock onto a
proper audio signal you'll get this line:

Audio microcontroller: detecting

If after changing the frequency (try just setting the same frequency) it
changes to 'running', then it is almost certainly a tuner issue.

You can also try using the S-Video or composite input: if you get the
same problems there, then it must be a cx25841 problem instead (since
the tuner is not used in that scenario).

Regards,

Hans

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


rich.kadel at appeligo

Sep 17, 2007, 11:00 AM

Post #19 of 25 (9149 views)
Permalink
Re: spontaneous muting [In reply to]
I put a test together to exercise this. I don't know if I have the version
you are referring to with the "Audio microcontroller" messages, but I'll
watch /var/log/messages for that.

Rich

--

Rich Kadel
Appeligo, Inc.
(858) 433-1747
www.appeligo.com

-----Original Message-----
From: ivtv-devel-bounces [at] ivtvdriver
[mailto:ivtv-devel-bounces [at] ivtvdriver] On Behalf Of Hans Verkuil
Sent: Sunday, September 16, 2007 4:44 AM
To: Discussion list for development of the IVTV driver
Subject: Re: [ivtv-devel] spontaneous muting

On Wednesday 29 August 2007 17:55:02 Rich Kadel wrote:
> No, I'm certain it's not heat related. I started collecting video
> about a week ago on two servers that have been up 24/7 for months in
> a controlled colocation facility, and the problem developed over the
> next few days. I was using tuners that had been used for VBI
> collection up until that point.
>
> FYI, I'm trying a couple of things now to see if I get better
> results. Both of my production servers have multiple PVR-500s (3 in
> one and 4 in the other), with most recording VBI. Now I dedicate one
> tuner per server to video capture (and no VBI). I saw the color
> problem on both servers plus on my development server. So here's
> what I'm trying:
>
> 1. Moving the video from ivtv5 and ivtv7 to ivtv0. (Cyrus A reported
> muting problems with the second tuner on a PVR-500, but not the
> first, and I THINK that's what I noticed)
> 2. Closing the device when I don't need to capture video.
> (Previously, my software continually read from the device and piped
> output only when needed.) I'm only recording short clips based on an
> algorithm, so this will open and close the device many times per
> hour. I don't know if this will help, but the problem only developed
> after I started reading from the video device continually for hours
> or days, which I've never done before. 3. Creating a convenient way
> for me to monitor the results by server and time. I should be able
> to provide clearer information on the symptoms if this occurs again.
>
> It's been 12 hours, and so far it still looks good. But I need a few
> days to be sure.

Have you ever tried switching the channel to another frequency and back
again when the audio/video problems develop? I wonder if the tuner
frequency might be drifting over time. Besides going to B&W does the
amount of noise in the video also increase? I mean, the whole chain of
losing color, then audio muting suggests a tuner issue.

Note that the latest v4l-dvb has better status reporting (you might
already be using it, I don't know). If the cx25841 cannot lock onto a
proper audio signal you'll get this line:

Audio microcontroller: detecting

If after changing the frequency (try just setting the same frequency) it
changes to 'running', then it is almost certainly a tuner issue.

You can also try using the S-Video or composite input: if you get the
same problems there, then it must be a cx25841 problem instead (since
the tuner is not used in that scenario).

Regards,

Hans

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel



_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


hverkuil at xs4all

Oct 12, 2007, 6:26 AM

Post #20 of 25 (8872 views)
Permalink
Re: spontaneous muting [In reply to]
Rich,

Any progress on this issue?

Hans

On Monday 17 September 2007 20:00:22 Rich Kadel wrote:
> I put a test together to exercise this. I don't know if I have the
> version you are referring to with the "Audio microcontroller"
> messages, but I'll watch /var/log/messages for that.
>
> Rich
>
> --
>
> Rich Kadel
> Appeligo, Inc.
> (858) 433-1747
> www.appeligo.com
>
> -----Original Message-----
> From: ivtv-devel-bounces [at] ivtvdriver
> [mailto:ivtv-devel-bounces [at] ivtvdriver] On Behalf Of Hans Verkuil
> Sent: Sunday, September 16, 2007 4:44 AM
> To: Discussion list for development of the IVTV driver
> Subject: Re: [ivtv-devel] spontaneous muting
>
> On Wednesday 29 August 2007 17:55:02 Rich Kadel wrote:
> > No, I'm certain it's not heat related. I started collecting video
> > about a week ago on two servers that have been up 24/7 for months
> > in a controlled colocation facility, and the problem developed over
> > the next few days. I was using tuners that had been used for VBI
> > collection up until that point.
> >
> > FYI, I'm trying a couple of things now to see if I get better
> > results. Both of my production servers have multiple PVR-500s (3
> > in one and 4 in the other), with most recording VBI. Now I
> > dedicate one tuner per server to video capture (and no VBI). I saw
> > the color problem on both servers plus on my development server.
> > So here's what I'm trying:
> >
> > 1. Moving the video from ivtv5 and ivtv7 to ivtv0. (Cyrus A
> > reported muting problems with the second tuner on a PVR-500, but
> > not the first, and I THINK that's what I noticed)
> > 2. Closing the device when I don't need to capture video.
> > (Previously, my software continually read from the device and piped
> > output only when needed.) I'm only recording short clips based on
> > an algorithm, so this will open and close the device many times per
> > hour. I don't know if this will help, but the problem only
> > developed after I started reading from the video device continually
> > for hours or days, which I've never done before. 3. Creating a
> > convenient way for me to monitor the results by server and time. I
> > should be able to provide clearer information on the symptoms if
> > this occurs again.
> >
> > It's been 12 hours, and so far it still looks good. But I need a
> > few days to be sure.
>
> Have you ever tried switching the channel to another frequency and
> back again when the audio/video problems develop? I wonder if the
> tuner frequency might be drifting over time. Besides going to B&W
> does the amount of noise in the video also increase? I mean, the
> whole chain of losing color, then audio muting suggests a tuner
> issue.
>
> Note that the latest v4l-dvb has better status reporting (you might
> already be using it, I don't know). If the cx25841 cannot lock onto a
> proper audio signal you'll get this line:
>
> Audio microcontroller: detecting
>
> If after changing the frequency (try just setting the same frequency)
> it changes to 'running', then it is almost certainly a tuner issue.
>
> You can also try using the S-Video or composite input: if you get the
> same problems there, then it must be a cx25841 problem instead (since
> the tuner is not used in that scenario).
>
> Regards,
>
> Hans
>
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel
>
>
>
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel



_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


rich.kadel at appeligo

Oct 12, 2007, 7:30 AM

Post #21 of 25 (8890 views)
Permalink
Re: spontaneous muting [In reply to]
Hans,

I tried to reproduce this with a different test (since I had already changed
my software that had caused this problem before) and I couldn't reproduce
the problem.

Things are working for me though, as long as I close the device when I don't
need to use the video stream.

If I run into this again, I'll let you know and try some of the things you
suggested.

Thanks,
Rich

--

Rich Kadel
Appeligo, Inc.
(858) 433-1747
www.appeligo.com


-----Original Message-----
From: ivtv-devel-bounces [at] ivtvdriver
[mailto:ivtv-devel-bounces [at] ivtvdriver] On Behalf Of Hans Verkuil
Sent: Friday, October 12, 2007 6:26 AM
To: Discussion list for development of the IVTV driver
Subject: Re: [ivtv-devel] spontaneous muting

Rich,

Any progress on this issue?

Hans

On Monday 17 September 2007 20:00:22 Rich Kadel wrote:
> I put a test together to exercise this. I don't know if I have the
> version you are referring to with the "Audio microcontroller"
> messages, but I'll watch /var/log/messages for that.
>
> Rich
>
> --
>
> Rich Kadel
> Appeligo, Inc.
> (858) 433-1747
> www.appeligo.com
>
> -----Original Message-----
> From: ivtv-devel-bounces [at] ivtvdriver
> [mailto:ivtv-devel-bounces [at] ivtvdriver] On Behalf Of Hans Verkuil
> Sent: Sunday, September 16, 2007 4:44 AM
> To: Discussion list for development of the IVTV driver
> Subject: Re: [ivtv-devel] spontaneous muting
>
> On Wednesday 29 August 2007 17:55:02 Rich Kadel wrote:
> > No, I'm certain it's not heat related. I started collecting video
> > about a week ago on two servers that have been up 24/7 for months
> > in a controlled colocation facility, and the problem developed over
> > the next few days. I was using tuners that had been used for VBI
> > collection up until that point.
> >
> > FYI, I'm trying a couple of things now to see if I get better
> > results. Both of my production servers have multiple PVR-500s (3
> > in one and 4 in the other), with most recording VBI. Now I
> > dedicate one tuner per server to video capture (and no VBI). I saw
> > the color problem on both servers plus on my development server.
> > So here's what I'm trying:
> >
> > 1. Moving the video from ivtv5 and ivtv7 to ivtv0. (Cyrus A
> > reported muting problems with the second tuner on a PVR-500, but
> > not the first, and I THINK that's what I noticed)
> > 2. Closing the device when I don't need to capture video.
> > (Previously, my software continually read from the device and piped
> > output only when needed.) I'm only recording short clips based on
> > an algorithm, so this will open and close the device many times per
> > hour. I don't know if this will help, but the problem only
> > developed after I started reading from the video device continually
> > for hours or days, which I've never done before. 3. Creating a
> > convenient way for me to monitor the results by server and time. I
> > should be able to provide clearer information on the symptoms if
> > this occurs again.
> >
> > It's been 12 hours, and so far it still looks good. But I need a
> > few days to be sure.
>
> Have you ever tried switching the channel to another frequency and
> back again when the audio/video problems develop? I wonder if the
> tuner frequency might be drifting over time. Besides going to B&W
> does the amount of noise in the video also increase? I mean, the
> whole chain of losing color, then audio muting suggests a tuner
> issue.
>
> Note that the latest v4l-dvb has better status reporting (you might
> already be using it, I don't know). If the cx25841 cannot lock onto a
> proper audio signal you'll get this line:
>
> Audio microcontroller: detecting
>
> If after changing the frequency (try just setting the same frequency)
> it changes to 'running', then it is almost certainly a tuner issue.
>
> You can also try using the S-Video or composite input: if you get the
> same problems there, then it must be a cx25841 problem instead (since
> the tuner is not used in that scenario).
>
> Regards,
>
> Hans
>
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel
>
>
>
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel



_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel



_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


faure at kde

Feb 2, 2008, 6:34 AM

Post #22 of 25 (8041 views)
Permalink
Re: spontaneous muting [In reply to]
Sorry for breaking the thread, I just subscribed.
A thread on ivtv-users pointed me to this thread here so I'm jumping in :)

I too have been experiencing loss of sound during recording with a PVR-350.

frank wrote on 31 Aug 2007:
> My card (pvr350) has been running fine for over a year (24x7), until
> I updated my SuSE with standard updates a few weeks ago. I'm pretty sure
> the problem did not exist with kernel 2.6.18.0.1, but now with 2.6.18.0.5 the
> sound breaks after 3-15min into recording.

I just wanted to add that I don't believe it's kernel-upgrade related. I have the problems
with linux 2.6.17-10-386 + ivtv-0.7.1. I am very interested in finding out which other package to upgrade
or downgrade to solve this very annoying problem, though :)

Has this problem been solved meanwhile?

If not, I will definitely watch for v4l2-ctl -C mute when the sound drops to see
if it's spontaneous muting or not; anything else I should watch for?
(PS: I'm clueless about drivers and other lowlevel stuff but I can write C/C++ code, so
if there's any part of the driver code where debug output would give more info, I can hack it in...)

--
David Faure, faure [at] kde, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


hverkuil at xs4all

Feb 20, 2008, 1:33 PM

Post #23 of 25 (7903 views)
Permalink
Re: spontaneous muting [In reply to]
On Saturday 02 February 2008 15:34:30 David Faure wrote:
> Sorry for breaking the thread, I just subscribed.
> A thread on ivtv-users pointed me to this thread here so I'm jumping
> in :)
>
> I too have been experiencing loss of sound during recording with a
> PVR-350.
>
> frank wrote on 31 Aug 2007:
> > My card (pvr350) has been running fine for over a year (24x7),
> > until I updated my SuSE with standard updates a few weeks ago. I'm
> > pretty sure the problem did not exist with kernel 2.6.18.0.1, but
> > now with 2.6.18.0.5 the sound breaks after 3-15min into recording.
>
> I just wanted to add that I don't believe it's kernel-upgrade
> related. I have the problems with linux 2.6.17-10-386 + ivtv-0.7.1. I
> am very interested in finding out which other package to upgrade or
> downgrade to solve this very annoying problem, though :)
>
> Has this problem been solved meanwhile?
>
> If not, I will definitely watch for v4l2-ctl -C mute when the sound
> drops to see if it's spontaneous muting or not; anything else I
> should watch for? (PS: I'm clueless about drivers and other lowlevel
> stuff but I can write C/C++ code, so if there's any part of the
> driver code where debug output would give more info, I can hack it
> in...)

It's a bit of a fuzzy problem and it is not clear to me whether there is
a real driver bug somewhere, or if it is really a hardware issue or
something like that.

But if you want to get this fixed then you first need to upgrade to a
kernel >= 2.6.22, and then install the bleeding edge drivers on top
(see http://www.ivtvdriver.org/index.php/Download#Bleeding_Edge_driver)

If you can reproduce it with that setup, and in particular if you can do
something as simple as 'cat /dev/video0 >foo.mpg' and the sound
disappears after X minutes, then please report back. A setup like that
will enable me to trace the problem.

Regards,

Hans

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


faure at kde

May 5, 2008, 2:47 PM

Post #24 of 25 (7297 views)
Permalink
Re: spontaneous muting [In reply to]
On Wednesday 20 February 2008, Hans Verkuil wrote:
> On Saturday 02 February 2008 15:34:30 David Faure wrote:
> > Sorry for breaking the thread, I just subscribed.
> > A thread on ivtv-users pointed me to this thread here so I'm jumping
> > in :)
> >
> > I too have been experiencing loss of sound during recording with a
> > PVR-350.
> >
> > frank wrote on 31 Aug 2007:
> > > My card (pvr350) has been running fine for over a year (24x7),
> > > until I updated my SuSE with standard updates a few weeks ago. I'm
> > > pretty sure the problem did not exist with kernel 2.6.18.0.1, but
> > > now with 2.6.18.0.5 the sound breaks after 3-15min into recording.
> >
> > I just wanted to add that I don't believe it's kernel-upgrade
> > related. I have the problems with linux 2.6.17-10-386 + ivtv-0.7.1. I
> > am very interested in finding out which other package to upgrade or
> > downgrade to solve this very annoying problem, though :)
> >
> > Has this problem been solved meanwhile?
> >
> > If not, I will definitely watch for v4l2-ctl -C mute when the sound
> > drops to see if it's spontaneous muting or not; anything else I
> > should watch for? (PS: I'm clueless about drivers and other lowlevel
> > stuff but I can write C/C++ code, so if there's any part of the
> > driver code where debug output would give more info, I can hack it
> > in...)
>
> It's a bit of a fuzzy problem and it is not clear to me whether there is
> a real driver bug somewhere, or if it is really a hardware issue or
> something like that.

I think it was a hardware issue after all. Without changing anything in my setup,
it hasn't happened anymore for 3 months now. All I did was to be careful about
the temperature of the computer, e.g. not turning it on too long before recording time.
I think the machine has air flow issues and overheats, and this must be what caused
the sound recording to break in the PVR.

--
David Faure, faure [at] kde, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


vsnine at vsnine

May 6, 2008, 8:25 AM

Post #25 of 25 (7238 views)
Permalink
Re: spontaneous muting [In reply to]
<quote who="David Faure">
> On Wednesday 20 February 2008, Hans Verkuil wrote:
>> On Saturday 02 February 2008 15:34:30 David Faure wrote:
>> > Sorry for breaking the thread, I just subscribed.
>> > A thread on ivtv-users pointed me to this thread here so I'm jumping
>> > in :)
>> >
>> > I too have been experiencing loss of sound during recording with a
>> > PVR-350.
>> >
>> > frank wrote on 31 Aug 2007:
>> > > My card (pvr350) has been running fine for over a year (24x7),
>> > > until I updated my SuSE with standard updates a few weeks ago. I'm
>> > > pretty sure the problem did not exist with kernel 2.6.18.0.1, but
>> > > now with 2.6.18.0.5 the sound breaks after 3-15min into recording.
>> >
>> > I just wanted to add that I don't believe it's kernel-upgrade
>> > related. I have the problems with linux 2.6.17-10-386 + ivtv-0.7.1. I
>> > am very interested in finding out which other package to upgrade or
>> > downgrade to solve this very annoying problem, though :)
>> >
>> > Has this problem been solved meanwhile?
>> >
>> > If not, I will definitely watch for v4l2-ctl -C mute when the sound
>> > drops to see if it's spontaneous muting or not; anything else I
>> > should watch for? (PS: I'm clueless about drivers and other lowlevel
>> > stuff but I can write C/C++ code, so if there's any part of the
>> > driver code where debug output would give more info, I can hack it
>> > in...)
>>
>> It's a bit of a fuzzy problem and it is not clear to me whether there is
>> a real driver bug somewhere, or if it is really a hardware issue or
>> something like that.
>
> I think it was a hardware issue after all. Without changing anything in my
> setup,
> it hasn't happened anymore for 3 months now. All I did was to be careful
> about
> the temperature of the computer, e.g. not turning it on too long before
> recording time.
> I think the machine has air flow issues and overheats, and this must be
> what caused
> the sound recording to break in the PVR.
>

Try putting a floor fan near the case's open sides...Also see if your
machine supports lm_sensors or the like. I have a few machines that get
absolutely buggy if run too hot.

Josh Becigneul


_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

ivtv devel RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.