Mailing List Archive

1 2  View All
Re: CX18 audio interference [ In reply to ]
On Sun, 2009-04-26 at 19:32 -0700, tbmail@hackthemainframe.com wrote:
> Hi,
>
> Just to confirm, the mono register hack thing worked for me too.

OK. That's the internal broadcast audio decoder and/or the internal
audio input mux not egtting set up properly.

Last night, I moved over a few patches from my cx18-init-debug repo to

http://linuxtv.org/hg/~awalls/v4l-dvb

and asked for them to be pulled to the main repository.

These changes do 2 things:

1. Verify the audio broadcast decoder firmware load (cx23418-v4l.dig),
by reading back every byte that was uploaded to the CX23418. An info
message will be logged if things were good, and an error message will be
logged if things were bad. No automatic corrective actions will be
taken on failure to verify the firmware load. (yet, at least).

2. Whenever the internal audio input mux is being set, the driver will
ensure the mux routing control bits change, even if that means
switching the mux away to some other audio input and then back. That
way we can reliably tell we made the audio input mux control bits
change.

Hopefully those changes help.



> I really
> do wish there was a way to fix that cs5345 volume control though, so that
> it's not so quiet.

On my TODO list. I need to do it for audio line in anyway.

-Andy

> -Terry



_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
Re: CX18 audio interference [ In reply to ]
Hi Andy,

I finally had a chance to test the cx18-init-debug repo. Unfortunately
it doesn't solve the audio static problem. In your reply to Terry, you said:

> Last night, I moved over a few patches from my cx18-init-debug repo to
>
> http://linuxtv.org/hg/~awalls/v4l-dvb
>
> and asked for them to be pulled to the main repository.
>
> These changes do 2 things:
>
> 1. Verify the audio broadcast decoder firmware load (cx23418-v4l.dig),
> by reading back every byte that was uploaded to the CX23418. An info
> message will be logged if things were good, and an error message will be
> logged if things were bad. No automatic corrective actions will be
> taken on failure to verify the firmware load. (yet, at least).

I think I see that verification message:
[10391.229402] cx18-0 843: verified load of v4l-cx23418-dig.fw firmware (16382 bytes)

> 2. Whenever the internal audio input mux is being set, the driver will
> ensure the mux routing control bits change, even if that means
> switching the mux away to some other audio input and then back. That
> way we can reliably tell we made the audio input mux control bits
> change.

I think you're referring here to the error messages in this patch:
http://linuxtv.org/hg/~awalls/cx18-init-debug/rev/93828c207b80

I see only one such message:
[10899.263227] cx18-0: cx18_writel failed to write 0x00000b05 to addr 0x02c72014

And I believe it's to be expected, because it occurred when I called:
v4l2-dbg -c host0 -s 0x2c72014 0xb05
and the value that's read back is 0x305, right?

The good news is that with that register set to 0xb05, sound is clear using the
cx-init-debug modules. I'm attaching dmesg output starting when I modprobe'd cx18.
Hope it helps.

FWIW, a while back, you asked Terry whether APU & CPU firmware were loaded twice.
What I see are two pairs of requests to load them. Only the first pair of requests
are followed with "loaded" messages. After the second pair of requests and some info
msgs I think are related to firmware loading, the DIG firmware is requested,
loaded and verified.

HTH,
Helen
Re: CX18 audio interference [ In reply to ]
On Thu, 2009-04-30 at 01:02 -0400, faginbagin wrote:
> Hi Andy,
>
> I finally had a chance to test the cx18-init-debug repo. Unfortunately
> it doesn't solve the audio static problem.

OK. I wasn't sure if it would. That narrows the problem to the '843
core in the CX23418 (I think).

Could you provide the output of

# v4l2-dbg -d /dev/video0 -c host0 --log-status -l

for when you are tuned to a channel with good sound and one with
consistent static (but good video).


> In your reply to Terry, you said:
>
> > Last night, I moved over a few patches from my cx18-init-debug repo to
> >
> > http://linuxtv.org/hg/~awalls/v4l-dvb
> >
> > and asked for them to be pulled to the main repository.

And they are in the main repo now too.


> > These changes do 2 things:
> >
> > 1. Verify the audio broadcast decoder firmware load (cx23418-v4l.dig),
> > by reading back every byte that was uploaded to the CX23418. An info
> > message will be logged if things were good, and an error message will be
> > logged if things were bad. No automatic corrective actions will be
> > taken on failure to verify the firmware load. (yet, at least).
>
> I think I see that verification message:
> [10391.229402] cx18-0 843: verified load of v4l-cx23418-dig.fw firmware (16382 bytes)

Yup. That's it. The audio standard autodetection firmware loaded OK.

BTW are using the firmware available from

http://dl.ivtvdriver.org/ivtv/firmware/cx18-firmware.tar.gz

?


> > 2. Whenever the internal audio input mux is being set, the driver will
> > ensure the mux routing control bits change, even if that means
> > switching the mux away to some other audio input and then back. That
> > way we can reliably tell we made the audio input mux control bits
> > change.
>
> I think you're referring here to the error messages in this patch:
> http://linuxtv.org/hg/~awalls/cx18-init-debug/rev/93828c207b80
>
> I see only one such message:
> [10899.263227] cx18-0: cx18_writel failed to write 0x00000b05 to addr 0x02c72014
>
> And I believe it's to be expected, because it occurred when I called:
> v4l2-dbg -c host0 -s 0x2c72014 0xb05
> and the value that's read back is 0x305, right?

Yup. The v4l2-dbg command can't tell the driver what value to expect to
read back. If that's the only message like that, then the driver is
setting all the registers as it intended .


> The good news is that with that register set to 0xb05, sound is clear using the
> cx-init-debug modules. I'm attaching dmesg output starting when I modprobe'd cx18.
> Hope it helps.
>
> FWIW, a while back, you asked Terry whether APU & CPU firmware were loaded twice.
> What I see are two pairs of requests to load them. Only the first pair of requests
> are followed with "loaded" messages.

Yes, that's by design. Without debugging enabled, we only log when
we're done loading the firmwares (twice). We load them twice to
overcome a firmware bug related to the digital TV TS not working every
other time the cx18 module is reloaded.



> After the second pair of requests and some info
> msgs I think are related to firmware loading,

Yes. The DEBUG_PEEK32 is a check to see the firmware is alive. The APU
commands are there to rest the APU due to a bug in the firmware
triggered by loading the firmwares twice. :) The first analog capture
will have a screwed up audio same rate if we don't do the APU resets.



> the DIG firmware is requested,
> loaded and verified.

Yup last.


OK. So it looks like everything is happening as the cx18 driver
intended. This means simply, that the cx18 driver is likely doing
*something* wrong that doesn't matter for many boards, but appears to
matter for yours. It is likely related to the setup of the '843 core in
the CX23418 front end. Hopefully differential analysis of the register
dumps will provide some insight.

BTW, could you check if inhibiting the load of lirc_i2c makes things
better?

Regards,
Andy

>
> HTH,
> Helen
> plain text document attachment (dmesg-init-debug.txt)
> [10389.587304] Linux video capture interface: v2.00
> [10389.598425] cx18: Start initialization, version 1.1.0
> [10389.598488] cx18-0: Initializing card 0
> [10389.598491] cx18-0: Autodetected Hauppauge card
> [10389.599389] cx18-0: info: base addr: 0xf4000000
> [10389.599391] cx18-0: info: Enabling pci device
> [10389.599405] cx18 0000:01:09.0: PCI INT A -> Link[APC2] -> GSI 17 (level, low) -> IRQ 17
> [10389.599414] cx18-0: info: cx23418 (rev 0) at 01:09.0, irq: 17, latency: 64, memory: 0xf4000000
> [10389.599416] cx18-0: info: attempting ioremap at 0xf4000000 len 0x04000000
> [10389.602263] cx18-0: cx23418 revision 01010000 (B)
> [10389.697050] cx18-0: info: GPIO initial dir: 0000cffe/0000ffff out: 00003001/00000000
> [10389.697067] cx18-0: info: activating i2c...
> [10389.777682] lirc_i2c: chip 0x10020 found @ 0x71 (Hauppauge PVR150)
> [10389.777694] lirc_dev: lirc_register_plugin: sample_rate: 10
> [10389.821558] tveeprom 0-0050: Hauppauge model 74041, rev C6B2, serial# 5405623
> [10389.821562] tveeprom 0-0050: MAC address is 00-0D-FE-52-7B-B7
> [10389.821564] tveeprom 0-0050: tuner model is TCL M2523_5N_E (idx 112, type 50)
> [10389.821566] tveeprom 0-0050: TV standards NTSC(M) (eeprom 0x08)
> [10389.821568] tveeprom 0-0050: audio processor is CX23418 (idx 38)
> [10389.821569] tveeprom 0-0050: decoder processor is CX23418 (idx 31)
> [10389.821571] tveeprom 0-0050: has no radio, has IR receiver, has IR transmitter
> [10389.821573] cx18-0: Autodetected Hauppauge HVR-1600
> [10389.821575] cx18-0: info: NTSC tuner detected
> [10389.821576] cx18-0: Simultaneous Digital and Analog TV capture supported
> [10389.923705] tuner 1-0061: chip found @ 0xc2 (cx18 i2c driver #0-1)
> [10389.926671] cs5345 0-004c: chip found @ 0x98 (cx18 i2c driver #0-0)
> [10389.933877] tuner-simple 1-0061: creating new instance
> [10389.933880] tuner-simple 1-0061: type set to 50 (TCL 2002N)
> [10389.934577] cx18-0: info: Allocate encoder MPEG stream: 64 x 32768 buffers (2048kB total)
> [10389.934691] cx18-0: info: Allocate TS stream: 32 x 32768 buffers (1024kB total)
> [10389.934740] cx18-0: info: Allocate encoder YUV stream: 16 x 131072 buffers (2048kB total)
> [10389.934783] cx18-0: info: Allocate encoder VBI stream: 20 x 51984 buffers (1015kB total)
> [10389.934827] cx18-0: info: Allocate encoder PCM audio stream: 256 x 4096 buffers (1024kB total)
> [10389.935120] cx18-0: info: Allocate encoder IDX stream: 32 x 32768 buffers (1024kB total)
> [10389.935272] cx18-0: Registered device video0 for encoder MPEG (64 x 32 kB)
> [10389.935275] DVB: registering new adapter (cx18)
> [10389.982050] MXL5005S: Attached at address 0x63
> [10389.982056] DVB: registering adapter 0 frontend 0 (Samsung S5H1409 QAM/8VSB Frontend)...
> [10389.982126] cx18-0: DVB Frontend registered
> [10389.982128] cx18-0: Registered DVB adapter0 for TS (32 x 32 kB)
> [10389.982154] cx18-0: Registered device video32 for encoder YUV (16 x 128 kB)
> [10389.982170] cx18-0: Registered device vbi0 for encoder VBI (20 x 51984 bytes)
> [10389.982185] cx18-0: Registered device video24 for encoder PCM audio (256 x 4 kB)
> [10389.982187] cx18-0: Initialized card: Hauppauge HVR-1600
> [10389.982205] cx18: End initialization
> [10390.040778] cx18 0000:01:09.0: firmware: requesting v4l-cx23418-cpu.fw
> [10390.201917] cx18-0: loaded v4l-cx23418-cpu.fw firmware (158332 bytes)
> [10390.227449] cx18 0000:01:09.0: firmware: requesting v4l-cx23418-apu.fw
> [10390.258006] cx18-0: info: load segment a00000-a07fff
> [10390.280827] cx18-0: info: load segment ae0000-ae00ff
> [10390.281009] cx18-0: info: load segment b00000-b1a65f
> [10390.356125] cx18-0: loaded v4l-cx23418-apu.fw firmware V00120000 (141200 bytes)
> [10390.360910] cx18-0: info: 1 MiniMe Encoder Firmware 0.0.74.0 (Release 2007/03/12)
> [10390.360912] cx18-0: FW version: 0.0.74.0 (Release 2007/03/12)
> [10390.564020] cx18-0: api: CX18_CPU_DEBUG_PEEK32 cmd 0x20000003 args 0x00000000
> [10390.564076] cx18-0: api: CX18_APU_START cmd 0x10000001 args 0x000000b9 0x00000000
> [10390.565204] cx18-0: api: CX18_APU_RESETAI cmd 0x10000005 args
> [10390.565634] cx18-0: api: CX18_APU_STOP cmd 0x10000002 args 0x00000000
> [10390.568708] cx18 0000:01:09.0: firmware: requesting v4l-cx23418-cpu.fw
> [10390.708681] cx18 0000:01:09.0: firmware: requesting v4l-cx23418-apu.fw
> [10390.713813] cx18-0: info: load segment a00000-a07fff
> [10390.736492] cx18-0: info: load segment ae0000-ae00ff
> [10390.736689] cx18-0: info: load segment b00000-b1a65f
> [10390.817419] cx18-0: info: 1 MiniMe Encoder Firmware 0.0.74.0 (Release 2007/03/12)
> [10391.020020] cx18-0: api: CX18_CPU_DEBUG_PEEK32 cmd 0x20000003 args 0x00000000
> [10391.020077] cx18-0: api: CX18_APU_START cmd 0x10000001 args 0x000000b9 0x00000000
> [10391.021242] cx18-0: api: CX18_APU_RESETAI cmd 0x10000005 args
> [10391.021673] cx18-0: api: CX18_APU_STOP cmd 0x10000002 args 0x00000000
> [10391.021740] cx18 0000:01:09.0: firmware: requesting v4l-cx23418-dig.fw
> [10391.209180] cx18-0 843: loaded v4l-cx23418-dig.fw firmware (16382 bytes)
> [10391.229402] cx18-0 843: verified load of v4l-cx23418-dig.fw firmware (16382 bytes)
> [10391.229466] cx18-0: info: Changing input from 1 to 0
> [10391.229467] cx18-0: info: Mute
> [10391.229469] cx18-0 843: info: decoder set video input 7, audio input 8
> [10391.230396] cx18-0 843: info: decoder set video input 7, audio input 8
> [10391.230460] cx18-0: info: Unmute
> [10391.230462] cx18-0: info: Switching standard to 1000.
> [10391.230464] cx18-0 843: info: changing video std to fmt 1
> [10391.230479] cx18-0 843: info: PLL regs = int: 15, frac: 2876158, post: 4
> [10391.230480] cx18-0 843: info: PLL = 107.999999 MHz
> [10391.230482] cx18-0 843: info: PLL/8 = 13.499999 MHz
> [10391.230483] cx18-0 843: info: ADC Sampling freq = 14.317382 MHz
> [10391.230485] cx18-0 843: info: Chroma sub-carrier freq = 3.579545 MHz
> [10391.230487] cx18-0 843: info: hblank 122, hactive 720, vblank 26, vactive 481, vblank656 38, src_dec 543, burst 0x5b, luma_lpf 1, uv_lpf 1, comb 0x66, sc 0x087c1f
> [10391.231239] cx18-0: info: Mute
> [10391.231240] cx18-0: info: v4l2 ioctl: set frequency 1076
> [10391.232000] cx18-0: info: Unmute
> [10763.623147] cx18-0: info: Start encoder stream encoder MPEG
> [10763.623153] cx18-0: api: CX18_CREATE_TASK cmd 0x40000001 args 0x20020000
> [10763.623212] cx18-0: api: CX18_CPU_SET_CHANNEL_TYPE cmd 0x20020001 args 0x00000000 0x00000001
> [10763.623268] cx18-0: api: CX18_CPU_SET_VER_CROP_LINE cmd 0x2002001b args 0x00000000 0x00000000
> [10763.623324] cx18-0: api: CX18_CPU_SET_MISC_PARAMETERS cmd 0x20020015 args 0x00000000 0x00000003 0x00000001
> [10763.623386] cx18-0: api: CX18_CPU_SET_MISC_PARAMETERS cmd 0x20020015 args 0x00000000 0x00000008 0x00000000
> [10763.623443] cx18-0: api: CX18_CPU_SET_MISC_PARAMETERS cmd 0x20020015 args 0x00000000 0x00000004 0x00000001
> [10763.623499] cx18-0: api: CX18_CPU_SET_MISC_PARAMETERS cmd 0x20020015 args 0x00000000 0x0000000c
> [10763.623553] cx18-0: api: CX18_CPU_SET_CAPTURE_LINE_NO cmd 0x20020017 args 0x00000000 0x00000138 0x00000139
> [10763.623615] cx18-0 843: info: PLL regs = int: 15, frac: 2876158, post: 4
> [10763.623617] cx18-0 843: info: PLL = 107.999999 MHz
> [10763.623618] cx18-0 843: info: PLL/8 = 13.499999 MHz
> [10763.623620] cx18-0 843: info: ADC Sampling freq = 14.317382 MHz
> [10763.623621] cx18-0 843: info: Chroma sub-carrier freq = 3.579545 MHz
> [10763.623624] cx18-0 843: info: hblank 122, hactive 720, vblank 26, vactive 481, vblank656 38, src_dec 543, burst 0x5b, luma_lpf 1, uv_lpf 1, comb 0x66, sc 0x087c1f
> [10763.623671] cx18-0: info: Setup VBI h: 0 lines c000c bpl 1444 fr 1 20602060 307090d0
> [10763.623673] cx18-0: api: CX18_CPU_SET_RAW_VBI_PARAM cmd 0x20020016 args 0x00000000 0x000c000c 0x000005a4 0x00000001 0x20602060 0x307090d0
> [10763.920014] cx18-0: api: CX18_CPU_SET_INDEXTABLE cmd 0x20020010 args 0x00000000
> [10763.920081] cx18-0: api: CX18_CPU_SET_VIDEO_IN cmd 0x20020004 args 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
> [10763.920153] cx18-0: api: CX18_CPU_SET_VIDEO_RESOLUTION cmd 0x20020006 args 0x00000000 0x000002d0 0x000001e0
> [10763.920214] cx18-0: api: CX18_CPU_SET_STREAM_OUTPUT_TYPE cmd 0x20020012 args 0x00000000 0x00000000
> [10763.920269] cx18-0: api: CX18_CPU_SET_ASPECT_RATIO cmd 0x2002001e args 0x00000000 0x00000002
> [10763.920321] cx18-0: api: CX18_CPU_SET_GOP_STRUCTURE cmd 0x2002001c args 0x00000000 0x0000000f 0x00000003
> [10763.920373] cx18-0: api: CX18_CPU_SET_AUDIO_PARAMETERS cmd 0x20020011 args 0x00000000 0x000000b9
> [10763.920437] cx18-0: api: CX18_CPU_SET_AUDIO_MUTE cmd 0x20020014 args 0x00000000 0x00000000
> [10763.920512] cx18-0: api: CX18_CPU_SET_VIDEO_RATE cmd 0x20020005 args 0x00000000 0x00000000 0x005b8d80 0x00004e20 0x00000000
> [10763.920572] cx18-0: api: CX18_CPU_SET_FILTER_PARAM cmd 0x20020009 args 0x00000000 0x00000001 0x00000000 0x00000000
> [10763.920627] cx18-0: api: CX18_CPU_SET_FILTER_PARAM cmd 0x20020009 args 0x00000000 0x00000000 0x00000001 0x00000008
> [10763.920681] cx18-0: api: CX18_CPU_SET_FILTER_PARAM cmd 0x20020009 args 0x00000000 0x00000002 0x00000000 0x00000000
> [10763.920737] cx18-0: api: CX18_CPU_SET_MEDIAN_CORING cmd 0x2002000e args 0x00000000 0x00000000 0x000000ff 0x00000000 0x000000ff
> [10763.920798] cx18-0: api: CX18_CPU_SET_SPATIAL_FILTER_TYPE cmd 0x2002000c args 0x00000000 0x00000001 0x00000001
> [10763.920854] cx18-0: api: CX18_CPU_SET_FILTER_PARAM cmd 0x20020009 args 0x00000000 0x00000001 0x00000000 0x00000000
> [10763.920908] cx18-0: api: CX18_CPU_SET_FILTER_PARAM cmd 0x20020009 args 0x00000000 0x00000000 0x00000001 0x00000008
> [10763.920962] cx18-0: api: CX18_CPU_SET_FILTER_PARAM cmd 0x20020009 args 0x00000000 0x00000002 0x00000000 0x00000000
> [10763.921016] cx18-0: api: CX18_CPU_SET_SKIP_INPUT_FRAME cmd 0x2002001f args 0x00000000 0x00000000
> [10763.921068] cx18-0: api: CX18_CPU_SET_VIDEO_MUTE cmd 0x20020013 args 0x00000000 0x00808000
> [10763.921118] cx18-0: api: CX18_CPU_SET_MISC_PARAMETERS cmd 0x20020015 args 0x00000000 0x00000007 0x00000000 0x00000000
> [10763.921175] cx18-0: api: CX18_CPU_DE_SET_MDL_ACK cmd 0x20040002 args 0x00000000 0x00dc0c40 0x00dc0c48
> [10763.925329] cx18-0: api: CX18_CPU_CAPTURE_START cmd 0x20020002 args 0x00000000
> [10791.363323] cx18-0: api: CX18_CPU_SET_AUDIO_MUTE cmd 0x20020014 args 0x00000000 0x00000001
> [10791.363413] cx18-0: info: Mute
> [10791.363415] cx18-0: info: v4l2 ioctl: set frequency 4052
> [10791.460020] cx18-0: api: CX18_CPU_SET_MISC_PARAMETERS cmd 0x20020015 args 0x00000000 0x0000000c
> [10791.460092] cx18-0: api: CX18_CPU_SET_AUDIO_MUTE cmd 0x20020014 args 0x00000000 0x00000000
> [10791.460170] cx18-0: info: Unmute
> [10809.173110] cx18-0: info: User stopped encoder MPEG
> [10809.176269] cx18-0: info: close stopping capture
> [10809.176273] cx18-0: info: Stop Capture
> [10809.176276] cx18-0: api: CX18_CPU_CAPTURE_STOP cmd 0x20020003 args 0x00000000 0x00000001
> [10809.476020] cx18-0: api: CX18_CPU_DE_RELEASE_MDL cmd 0x20040006 args 0x00000000
> [10809.776017] cx18-0: api: CX18_DESTROY_TASK cmd 0x40000002 args 0x00000000
> [10899.263227] cx18-0: cx18_writel failed to write 0x00000b05 to addr 0x02c72014
> [10907.659654] cx18-0: info: Start encoder stream encoder MPEG
> [10907.659661] cx18-0: api: CX18_CREATE_TASK cmd 0x40000001 args 0x20020000
> [10907.659720] cx18-0: api: CX18_CPU_SET_CHANNEL_TYPE cmd 0x20020001 args 0x00000000 0x00000001
> [10907.659776] cx18-0: api: CX18_CPU_SET_VER_CROP_LINE cmd 0x2002001b args 0x00000000 0x00000000
> [10907.659830] cx18-0: api: CX18_CPU_SET_MISC_PARAMETERS cmd 0x20020015 args 0x00000000 0x00000003 0x00000001
> [10907.659893] cx18-0: api: CX18_CPU_SET_MISC_PARAMETERS cmd 0x20020015 args 0x00000000 0x00000008 0x00000000
> [10907.659949] cx18-0: api: CX18_CPU_SET_MISC_PARAMETERS cmd 0x20020015 args 0x00000000 0x00000004 0x00000001
> [10907.660018] cx18-0: api: CX18_CPU_SET_MISC_PARAMETERS cmd 0x20020015 args 0x00000000 0x0000000c
> [10907.660069] cx18-0: api: CX18_CPU_SET_CAPTURE_LINE_NO cmd 0x20020017 args 0x00000000 0x00000138 0x00000139
> [10907.660131] cx18-0 843: info: PLL regs = int: 15, frac: 2876158, post: 4
> [10907.660134] cx18-0 843: info: PLL = 107.999999 MHz
> [10907.660137] cx18-0 843: info: PLL/8 = 13.499999 MHz
> [10907.660139] cx18-0 843: info: ADC Sampling freq = 14.317382 MHz
> [10907.660141] cx18-0 843: info: Chroma sub-carrier freq = 3.579545 MHz
> [10907.660144] cx18-0 843: info: hblank 122, hactive 720, vblank 26, vactive 481, vblank656 38, src_dec 543, burst 0x5b, luma_lpf 1, uv_lpf 1, comb 0x66, sc 0x087c1f
> [10907.660192] cx18-0: info: Setup VBI h: 0 lines c000c bpl 1444 fr 1 20602060 307090d0
> [10907.660196] cx18-0: api: CX18_CPU_SET_RAW_VBI_PARAM cmd 0x20020016 args 0x00000000 0x000c000c 0x000005a4 0x00000001 0x20602060 0x307090d0
> [10907.960015] cx18-0: api: CX18_CPU_SET_INDEXTABLE cmd 0x20020010 args 0x00000000
> [10907.960078] cx18-0: api: CX18_CPU_SET_VIDEO_IN cmd 0x20020004 args 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
> [10907.960153] cx18-0: api: CX18_CPU_SET_VIDEO_RESOLUTION cmd 0x20020006 args 0x00000000 0x000002d0 0x000001e0
> [10907.960218] cx18-0: api: CX18_CPU_SET_STREAM_OUTPUT_TYPE cmd 0x20020012 args 0x00000000 0x00000000
> [10907.960272] cx18-0: api: CX18_CPU_SET_ASPECT_RATIO cmd 0x2002001e args 0x00000000 0x00000002
> [10907.960325] cx18-0: api: CX18_CPU_SET_GOP_STRUCTURE cmd 0x2002001c args 0x00000000 0x0000000f 0x00000003
> [10907.960377] cx18-0: api: CX18_CPU_SET_AUDIO_PARAMETERS cmd 0x20020011 args 0x00000000 0x000000b9
> [10907.960448] cx18-0: api: CX18_CPU_SET_AUDIO_MUTE cmd 0x20020014 args 0x00000000 0x00000000
> [10907.960520] cx18-0: api: CX18_CPU_SET_VIDEO_RATE cmd 0x20020005 args 0x00000000 0x00000000 0x005b8d80 0x00004e20 0x00000000
> [10907.961645] cx18-0: api: CX18_CPU_SET_FILTER_PARAM cmd 0x20020009 args 0x00000000 0x00000001 0x00000000 0x00000000
> [10907.961700] cx18-0: api: CX18_CPU_SET_FILTER_PARAM cmd 0x20020009 args 0x00000000 0x00000000 0x00000001 0x00000008
> [10907.961754] cx18-0: api: CX18_CPU_SET_FILTER_PARAM cmd 0x20020009 args 0x00000000 0x00000002 0x00000000 0x00000000
> [10907.961809] cx18-0: api: CX18_CPU_SET_MEDIAN_CORING cmd 0x2002000e args 0x00000000 0x00000000 0x000000ff 0x00000000 0x000000ff
> [10907.961868] cx18-0: api: CX18_CPU_SET_SPATIAL_FILTER_TYPE cmd 0x2002000c args 0x00000000 0x00000001 0x00000001
> [10907.961922] cx18-0: api: CX18_CPU_SET_FILTER_PARAM cmd 0x20020009 args 0x00000000 0x00000001 0x00000000 0x00000000
> [10907.961974] cx18-0: api: CX18_CPU_SET_FILTER_PARAM cmd 0x20020009 args 0x00000000 0x00000000 0x00000001 0x00000008
> [10907.962027] cx18-0: api: CX18_CPU_SET_FILTER_PARAM cmd 0x20020009 args 0x00000000 0x00000002 0x00000000 0x00000000
> [10907.962081] cx18-0: api: CX18_CPU_SET_SKIP_INPUT_FRAME cmd 0x2002001f args 0x00000000 0x00000000
> [10907.962131] cx18-0: api: CX18_CPU_SET_VIDEO_MUTE cmd 0x20020013 args 0x00000000 0x00808000
> [10907.962182] cx18-0: api: CX18_CPU_SET_MISC_PARAMETERS cmd 0x20020015 args 0x00000000 0x00000007 0x00000000 0x00000000
> [10907.962239] cx18-0: api: CX18_CPU_DE_SET_MDL_ACK cmd 0x20040002 args 0x00000000 0x00dc0c40 0x00dc0c48
> [10907.966313] cx18-0: api: CX18_CPU_CAPTURE_START cmd 0x20020002 args 0x00000000
> [10927.236560] cx18-0: info: User stopped encoder MPEG
> [10927.243350] cx18-0: info: close stopping capture
> [10927.243354] cx18-0: info: Stop Capture
> [10927.243358] cx18-0: api: CX18_CPU_CAPTURE_STOP cmd 0x20020003 args 0x00000000 0x00000001
> [10927.540025] cx18-0: api: CX18_CPU_DE_RELEASE_MDL cmd 0x20040006 args 0x00000000
> [10927.840018] cx18-0: api: CX18_DESTROY_TASK cmd 0x40000002 args 0x00000000
> [10951.556104] cx18-0: info: Start encoder stream encoder MPEG
> [10951.556110] cx18-0: api: CX18_CREATE_TASK cmd 0x40000001 args 0x20020000
> [10951.556167] cx18-0: api: CX18_CPU_SET_CHANNEL_TYPE cmd 0x20020001 args 0x00000000 0x00000001
> [10951.556220] cx18-0: api: CX18_CPU_SET_VER_CROP_LINE cmd 0x2002001b args 0x00000000 0x00000000
> [10951.556274] cx18-0: api: CX18_CPU_SET_MISC_PARAMETERS cmd 0x20020015 args 0x00000000 0x00000003 0x00000001
> [10951.556335] cx18-0: api: CX18_CPU_SET_MISC_PARAMETERS cmd 0x20020015 args 0x00000000 0x00000008 0x00000000
> [10951.556391] cx18-0: api: CX18_CPU_SET_MISC_PARAMETERS cmd 0x20020015 args 0x00000000 0x00000004 0x00000001
> [10951.556449] cx18-0: api: CX18_CPU_SET_MISC_PARAMETERS cmd 0x20020015 args 0x00000000 0x0000000c
> [10951.556504] cx18-0: api: CX18_CPU_SET_CAPTURE_LINE_NO cmd 0x20020017 args 0x00000000 0x00000138 0x00000139
> [10951.556573] cx18-0 843: info: PLL regs = int: 15, frac: 2876158, post: 4
> [10951.556576] cx18-0 843: info: PLL = 107.999999 MHz
> [10951.556578] cx18-0 843: info: PLL/8 = 13.499999 MHz
> [10951.556579] cx18-0 843: info: ADC Sampling freq = 14.317382 MHz
> [10951.556581] cx18-0 843: info: Chroma sub-carrier freq = 3.579545 MHz
> [10951.556584] cx18-0 843: info: hblank 122, hactive 720, vblank 26, vactive 481, vblank656 38, src_dec 543, burst 0x5b, luma_lpf 1, uv_lpf 1, comb 0x66, sc 0x087c1f
> [10951.556631] cx18-0: info: Setup VBI h: 0 lines c000c bpl 1444 fr 1 20602060 307090d0
> [10951.556635] cx18-0: api: CX18_CPU_SET_RAW_VBI_PARAM cmd 0x20020016 args 0x00000000 0x000c000c 0x000005a4 0x00000001 0x20602060 0x307090d0
> [10951.856511] cx18-0: api: CX18_CPU_SET_INDEXTABLE cmd 0x20020010 args 0x00000000
> [10951.856562] cx18-0: api: CX18_CPU_SET_VIDEO_IN cmd 0x20020004 args 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
> [10951.856633] cx18-0: api: CX18_CPU_SET_VIDEO_RESOLUTION cmd 0x20020006 args 0x00000000 0x000002d0 0x000001e0
> [10951.856699] cx18-0: api: CX18_CPU_SET_STREAM_OUTPUT_TYPE cmd 0x20020012 args 0x00000000 0x00000000
> [10951.856754] cx18-0: api: CX18_CPU_SET_ASPECT_RATIO cmd 0x2002001e args 0x00000000 0x00000002
> [10951.856806] cx18-0: api: CX18_CPU_SET_GOP_STRUCTURE cmd 0x2002001c args 0x00000000 0x0000000f 0x00000003
> [10951.856858] cx18-0: api: CX18_CPU_SET_AUDIO_PARAMETERS cmd 0x20020011 args 0x00000000 0x000000b9
> [10951.856923] cx18-0: api: CX18_CPU_SET_AUDIO_MUTE cmd 0x20020014 args 0x00000000 0x00000000
> [10951.856988] cx18-0: api: CX18_CPU_SET_VIDEO_RATE cmd 0x20020005 args 0x00000000 0x00000000 0x005b8d80 0x00004e20 0x00000000
> [10951.857047] cx18-0: api: CX18_CPU_SET_FILTER_PARAM cmd 0x20020009 args 0x00000000 0x00000001 0x00000000 0x00000000
> [10951.857102] cx18-0: api: CX18_CPU_SET_FILTER_PARAM cmd 0x20020009 args 0x00000000 0x00000000 0x00000001 0x00000008
> [10951.857156] cx18-0: api: CX18_CPU_SET_FILTER_PARAM cmd 0x20020009 args 0x00000000 0x00000002 0x00000000 0x00000000
> [10951.857210] cx18-0: api: CX18_CPU_SET_MEDIAN_CORING cmd 0x2002000e args 0x00000000 0x00000000 0x000000ff 0x00000000 0x000000ff
> [10951.857272] cx18-0: api: CX18_CPU_SET_SPATIAL_FILTER_TYPE cmd 0x2002000c args 0x00000000 0x00000001 0x00000001
> [10951.857328] cx18-0: api: CX18_CPU_SET_FILTER_PARAM cmd 0x20020009 args 0x00000000 0x00000001 0x00000000 0x00000000
> [10951.857381] cx18-0: api: CX18_CPU_SET_FILTER_PARAM cmd 0x20020009 args 0x00000000 0x00000000 0x00000001 0x00000008
> [10951.857433] cx18-0: api: CX18_CPU_SET_FILTER_PARAM cmd 0x20020009 args 0x00000000 0x00000002 0x00000000 0x00000000
> [10951.857487] cx18-0: api: CX18_CPU_SET_SKIP_INPUT_FRAME cmd 0x2002001f args 0x00000000 0x00000000
> [10951.857537] cx18-0: api: CX18_CPU_SET_VIDEO_MUTE cmd 0x20020013 args 0x00000000 0x00808000
> [10951.857587] cx18-0: api: CX18_CPU_SET_MISC_PARAMETERS cmd 0x20020015 args 0x00000000 0x00000007 0x00000000 0x00000000
> [10951.857643] cx18-0: api: CX18_CPU_DE_SET_MDL_ACK cmd 0x20040002 args 0x00000000 0x00dc0c40 0x00dc0c48
> [10951.861665] cx18-0: api: CX18_CPU_CAPTURE_START cmd 0x20020002 args 0x00000000
> [10959.248596] cx18-0: api: CX18_CPU_SET_AUDIO_MUTE cmd 0x20020014 args 0x00000000 0x00000001
> [10959.248716] cx18-0: info: Mute
> [10959.248718] cx18-0: info: v4l2 ioctl: set frequency 5204
> [10959.348023] cx18-0: api: CX18_CPU_SET_MISC_PARAMETERS cmd 0x20020015 args 0x00000000 0x0000000c
> [10959.348088] cx18-0: api: CX18_CPU_SET_AUDIO_MUTE cmd 0x20020014 args 0x00000000 0x00000000
> [10959.348156] cx18-0: info: Unmute
> [10967.520355] cx18-0: info: User stopped encoder MPEG
> [10967.523645] cx18-0: info: close stopping capture
> [10967.523649] cx18-0: info: Stop Capture
> [10967.523652] cx18-0: api: CX18_CPU_CAPTURE_STOP cmd 0x20020003 args 0x00000000 0x00000001
> [10967.820014] cx18-0: api: CX18_CPU_DE_RELEASE_MDL cmd 0x20040006 args 0x00000000
> [10968.120019] cx18-0: api: CX18_DESTROY_TASK cmd 0x40000002 args 0x00000000
> _______________________________________________
> ivtv-users mailing list
> ivtv-users@ivtvdriver.org
> http://ivtvdriver.org/mailman/listinfo/ivtv-users


_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
Re: CX18 audio interference [ In reply to ]
Hi Andy,

> OK. I wasn't sure if it would. That narrows the problem to the '843
> core in the CX23418 (I think).
>
> Could you provide the output of
>
> # v4l2-dbg -d /dev/video0 -c host0 --log-status -l
>
> for when you are tuned to a channel with good sound and one with
> consistent static (but good video).

Good sound: See attached dbg-after-mplayer-chan4.txt & dbg-tune-chan2.txt
dbg-after-mplayer-chan4.txt was captured after starting mplayer, default channel appears to be 4.
dbg-tune-chan2.txt was captured after tuning to channel 2.

Static but good video; See attached dbg-tune-chan41.txt
Channel 41 is one of the noisier channels.

> BTW are using the firmware available from
>
> http://dl.ivtvdriver.org/ivtv/firmware/cx18-firmware.tar.gz

Yes. The correct files are provided by the mythbuntu jaunty distro. I double checked it by downloading the above and cmp'ing each .fw file against the distro files.

>> I see only one such message:
>> [10899.263227] cx18-0: cx18_writel failed to write 0x00000b05 to addr 0x02c72014
>>
>> And I believe it's to be expected, because it occurred when I called:
>> v4l2-dbg -c host0 -s 0x2c72014 0xb05
>> and the value that's read back is 0x305, right?
>
> Yup. The v4l2-dbg command can't tell the driver what value to expect to
> read back. If that's the only message like that, then the driver is
> setting all the registers as it intended .

And during this latest test, there were no 'failed to write' messages in dmesg.

>> FWIW, a while back, you asked Terry whether APU & CPU firmware were loaded twice.
>> What I see are two pairs of requests to load them. Only the first pair of requests
>> are followed with "loaded" messages.
>
> Yes, that's by design. Without debugging enabled, we only log when
> we're done loading the firmwares (twice). We load them twice to
> overcome a firmware bug related to the digital TV TS not working every
> other time the cx18 module is reloaded.

Are there any other debug flags I should enable besides CONFIG_VIDEO_ADV_DEBUG? I was going to attach my .config file, but it caused thie email to exceed a 40K limit.

> OK. So it looks like everything is happening as the cx18 driver
> intended. This means simply, that the cx18 driver is likely doing
> *something* wrong that doesn't matter for many boards, but appears to
> matter for yours. It is likely related to the setup of the '843 core in
> the CX23418 front end. Hopefully differential analysis of the register
> dumps will provide some insight.
>
> BTW, could you check if inhibiting the load of lirc_i2c makes things
> better?

This time, I made sure to stop the lircd daemon and to rmmod lirc_i2c and lirc_dev before modprobing cx18. I made sure the lirc modules didn't automagically reappear after modprobing or after running mplayer. So I think it's safe to say they've got nothing to do with my problem. Although, to be certain, I could do a scan of all channels.

I also have a dmesg.txt that covers the time from when I unloaded & reloaded modules to when I stopped mplayer. I'm not attaching it as it would put this message over 40K. If you want it, and/or my .config file, perhaps I should send them to you off-list?

Regards,
Helen
Re: CX18 audio interference [ In reply to ]
On Fri, 2009-05-01 at 01:32 -0400, faginbagin wrote:
> Hi Andy,
>
> > OK. I wasn't sure if it would. That narrows the problem to the '843
> > core in the CX23418 (I think).
> >
> > Could you provide the output of
> >
> > # v4l2-dbg -d /dev/video0 -c host0 --log-status -l
> >
> > for when you are tuned to a channel with good sound and one with
> > consistent static (but good video).
>
> Good sound: See attached dbg-after-mplayer-chan4.txt & dbg-tune-chan2.txt
> dbg-after-mplayer-chan4.txt was captured after starting mplayer, default channel appears to be 4.
> dbg-tune-chan2.txt was captured after tuning to channel 2.
>
> Static but good video; See attached dbg-tune-chan41.txt
> Channel 41 is one of the noisier channels.

Helen,

Before I do a lot of clean-up on some code that I think is in error,
could you try the following.

When you are tuned to a channel with poor sound, like channel 41, please
try these commands:

# v4l2-dbg -d /dev/video0 -c host1 -g 0x104
ioctl: VIDIOC_DBG_G_REGISTER
Register 0x00000104 = 71b5c00h (119233536d 00000111 00011011 01011100 00000000b)

# v4l2-dbg -d /dev/video0 -c host1 -s 0x104 0x07005d80
Register 0x00000104 set to 0x7005d80


The cx18 driver is currently setting the AGC for the SIF audio input
amplifier to set the SIF input amplifier gain based on video signal
level. This register change (which is tailored for an HVR-1600 set to
the analog tuner) sets the AGC for the SIF audio input amplifier to be
controlled by the audio signal level.

Hopefully that will make things better.


> Are there any other debug flags I should enable besides
> CONFIG_VIDEO_ADV_DEBUG? I was going to attach my .config file, but it
> caused thie email to exceed a 40K limit.

No. That's the only one in the .config I really care about. There's
another .config variable to build debugging into the I2C subsystem, but
that requires a kernel rebuild and I don't think we need it set.

The other debug paramaters I'm referring to are the flags to the cx18's
debug module option.

$ modinfo cx18

will show you what the flags mean. The default is debug=0 of course.


> I also have a dmesg.txt that covers the time from when I unloaded &
> reloaded modules to when I stopped mplayer. I'm not attaching it as it
> would put this message over 40K. If you want it, and/or my .config
> file, perhaps I should send them to you off-list?

Don't bother.

Regards,
Andy

> Regards,
> Helen


_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
Re: CX18 audio interference [ In reply to ]
Hi Andy,

> Before I do a lot of clean-up on some code that I think is in error,
> could you try the following.
>
> When you are tuned to a channel with poor sound, like channel 41, please
> try these commands:
>
> # v4l2-dbg -d /dev/video0 -c host1 -g 0x104
> ioctl: VIDIOC_DBG_G_REGISTER
> Register 0x00000104 = 71b5c00h (119233536d 00000111 00011011 01011100 00000000b)

My output:
ioctl: VIDIOC_DBG_G_REGISTER
Register 0x00000104 = 71b5c00h (119233536d 00000111 00011011 01011100 00000000b)

> # v4l2-dbg -d /dev/video0 -c host1 -s 0x104 0x07005d80
> Register 0x00000104 set to 0x7005d80

My output:
Register 0x00000104 set to 0x7005d80

> The cx18 driver is currently setting the AGC for the SIF audio input
> amplifier to set the SIF input amplifier gain based on video signal
> level. This register change (which is tailored for an HVR-1600 set to
> the analog tuner) sets the AGC for the SIF audio input amplifier to be
> controlled by the audio signal level.
>
> Hopefully that will make things better.

Yes, it seems to do the trick! I also tuned a handful of other troublesome channels and they sound good too. Hopefully it will survive when I start mythbackend. I've got a recording scheduled at 10pm and I'll be sure to check it soon after it starts.

Thanks,
Helen

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
Re: CX18 audio interference [ In reply to ]
On Fri, 2009-05-01 at 21:41 -0400, faginbagin wrote:

> > # v4l2-dbg -d /dev/video0 -c host1 -s 0x104 0x07005d80
> > Register 0x00000104 set to 0x7005d80
>
> My output:
> Register 0x00000104 set to 0x7005d80
>
> > The cx18 driver is currently setting the AGC for the SIF audio input
> > amplifier to set the SIF input amplifier gain based on video signal
> > level. This register change (which is tailored for an HVR-1600 set to
> > the analog tuner) sets the AGC for the SIF audio input amplifier to be
> > controlled by the audio signal level.
> >
> > Hopefully that will make things better.
>
> Yes, it seems to do the trick!

Good!

Now I have lots of confusing code borrowed from the cx25840 module to
straighten up. Ugh! Don't look for a patch worth testing until next
weekend.


> I also tuned a handful of other troublesome channels and they sound
> good too. Hopefully it will survive when I start mythbackend. I've got
> a recording scheduled at 10pm and I'll be sure to check it soon after
> it starts.

It should persist until you switch analog input sources: radio, svideo,
or composite. When you go back to tuner after that, the driver will
write bad values back in.

Regards,
Andy


> Thanks,
> Helen



_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
Re: CX18 audio interference [ In reply to ]
Hi Andy,

Andy Walls wrote:
> On Fri, 2009-05-01 at 21:41 -0400, faginbagin wrote:
>
>>> # v4l2-dbg -d /dev/video0 -c host1 -s 0x104 0x07005d80
>>> Register 0x00000104 set to 0x7005d80
>> My output:
>> Register 0x00000104 set to 0x7005d80
>>
>>> The cx18 driver is currently setting the AGC for the SIF audio input
>>> amplifier to set the SIF input amplifier gain based on video signal
>>> level. This register change (which is tailored for an HVR-1600 set to
>>> the analog tuner) sets the AGC for the SIF audio input amplifier to be
>>> controlled by the audio signal level.
>>>
>>> Hopefully that will make things better.
>> Yes, it seems to do the trick!
>
> Good!
>
> Now I have lots of confusing code borrowed from the cx25840 module to
> straighten up. Ugh! Don't look for a patch worth testing until next
> weekend.

No problem. I've put that set register command in my /etc/rc.local so I've got a workaround that should survive a reboot. And another bit of good news with this setting is the volume is higher than it was with the other register setting. But you probably knew that.

>> I also tuned a handful of other troublesome channels and they sound
>> good too. Hopefully it will survive when I start mythbackend. I've got
>> a recording scheduled at 10pm and I'll be sure to check it soon after
>> it starts.
>
> It should persist until you switch analog input sources: radio, svideo,
> or composite. When you go back to tuner after that, the driver will
> write bad values back in.

I haven't had occasion to switch analog inputs, only NTSC <-> ATSC/QAM tuners, which work simultaneously.

Thanks,
Helen


_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
Re: CX18 audio interference [ In reply to ]
On Sat, 2009-05-02 at 16:52 -0400, faginbagin wrote:

> Andy Walls wrote:

> >>> The cx18 driver is currently setting the AGC for the SIF audio input
> >>> amplifier to set the SIF input amplifier gain based on video signal
> >>> level. This register change (which is tailored for an HVR-1600 set to
> >>> the analog tuner) sets the AGC for the SIF audio input amplifier to be
> >>> controlled by the audio signal level.
> >>>
> >>> Hopefully that will make things better.
> >> Yes, it seems to do the trick!
> >
> > Good!
> >
> > Now I have lots of confusing code borrowed from the cx25840 module to
> > straighten up. Ugh! Don't look for a patch worth testing until next
> > weekend.
>
> No problem. I've put that set register command in my /etc/rc.local so
> I've got a workaround that should survive a reboot.

Helen,

I have a patch for testing at:

http://linuxtv.org/hg/~awalls/cx18-av-core/
http://linuxtv.org/hg/~awalls/cx18-av-core/rev/9beb99150ab1


Helen and ivtv-devel list readers,

This patch needs some tests run:

1. Check that sound is better with the NTSC tuner
2. Check that S-Video and/or Composite in with NTSC didn't break
3. Check that switching back to the tuner, sound is still OK.
4. Check that PAL & SECAM still work on SVideo and/or Composite
5. Check that PAL and/or SECAM tuner sound is OK.

I'll try and test what I can during the course of this week. I have
high confidence that nothing is working worse than before :), but I
can't check OTA PAL or SECAM (Maybe someone with a Compro H900 can
check?).


Since this bug was inhereted from the cx25840 module, I'm wondering if
this is the cause of the PVR-150 tinny audio. If I can reproduce the
tinny audio with my PVR-150MCE, I'll try to experiment with having the
SIF gain controlled by the audio decoder (the correct thing todo) versus
the video decoder (the wrong thing todo) of the CX2584x. This change
can, with some difficulty, be ported to the cx25840 module, if that
fixes the tinny audio.

Regards,
Andy



_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
Re: CX18 audio interference [ In reply to ]
Hi Andy,

> I have a patch for testing at:
>
> http://linuxtv.org/hg/~awalls/cx18-av-core/
> http://linuxtv.org/hg/~awalls/cx18-av-core/rev/9beb99150ab1
>
>
> Helen and ivtv-devel list readers,
>
> This patch needs some tests run:
>
> 1. Check that sound is better with the NTSC tuner
> 2. Check that S-Video and/or Composite in with NTSC didn't break
> 3. Check that switching back to the tuner, sound is still OK.
> 4. Check that PAL & SECAM still work on SVideo and/or Composite
> 5. Check that PAL and/or SECAM tuner sound is OK.
>
> I'll try and test what I can during the course of this week. I have
> high confidence that nothing is working worse than before :), but I
> can't check OTA PAL or SECAM (Maybe someone with a Compro H900 can
> check?).
>
>
> Since this bug was inhereted from the cx25840 module, I'm wondering if
> this is the cause of the PVR-150 tinny audio. If I can reproduce the
> tinny audio with my PVR-150MCE, I'll try to experiment with having the
> SIF gain controlled by the audio decoder (the correct thing todo) versus
> the video decoder (the wrong thing todo) of the CX2584x. This change
> can, with some difficulty, be ported to the cx25840 module, if that
> fixes the tinny audio.
>
> Regards,
> Andy

I downloaded the cx18-av-core repo and tested 1-3. Sound was good on a
couple of the previously bad channels, 29 & 41. Switching to input 1,
sound was still good, switching back to input 0, sound was still good on
channels 41 & 29.

Let me know if there's more I should do. I'll keep this version
installed & make sure all is still well with mythtv.

Helen

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
Re: CX18 audio interference [ In reply to ]
On Mon, 2009-05-04 at 13:38 -0400, faginbagin wrote:
> Hi Andy,
>
> > I have a patch for testing at:
> >
> > http://linuxtv.org/hg/~awalls/cx18-av-core/
> > http://linuxtv.org/hg/~awalls/cx18-av-core/rev/9beb99150ab1
> >
> >
> > Helen and ivtv-devel list readers,
> >
> > This patch needs some tests run:
> >
> > 1. Check that sound is better with the NTSC tuner
> > 2. Check that S-Video and/or Composite in with NTSC didn't break
> > 3. Check that switching back to the tuner, sound is still OK.
> > 4. Check that PAL & SECAM still work on SVideo and/or Composite
> > 5. Check that PAL and/or SECAM tuner sound is OK.
> >
> > I'll try and test what I can during the course of this week. I have
> > high confidence that nothing is working worse than before :), but I
> > can't check OTA PAL or SECAM (Maybe someone with a Compro H900 can
> > check?).
> >
> >
> > Since this bug was inhereted from the cx25840 module, I'm wondering if
> > this is the cause of the PVR-150 tinny audio. If I can reproduce the
> > tinny audio with my PVR-150MCE, I'll try to experiment with having the
> > SIF gain controlled by the audio decoder (the correct thing todo) versus
> > the video decoder (the wrong thing todo) of the CX2584x. This change
> > can, with some difficulty, be ported to the cx25840 module, if that
> > fixes the tinny audio.
> >
> > Regards,
> > Andy
>
> I downloaded the cx18-av-core repo and tested 1-3. Sound was good on a
> couple of the previously bad channels, 29 & 41. Switching to input 1,
> sound was still good, switching back to input 0, sound was still good on
> channels 41 & 29.

Good. I'm assuming your audio issues are resolved.

I was able to run tests 1-3 with Composite as the alternate input (I
need to dig up an S-Video cable), and test 4 with PAL as output by a
PVR-350 into the HVR-1600's composite. Things were all OK - so I don't
think I broke anything.

Daniel provided positive feedback on the ivtv-devel list as well. I'll
probably ask this to get pulled to the main v4l-dvb repo soon.

Regards,
Andy


> Let me know if there's more I should do. I'll keep this version
> installed & make sure all is still well with mythtv.
>
> Helen
>


_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
Re: CX18 audio interference [ In reply to ]
Hi Andy,

>>> I have a patch for testing at:
>>>
>>> http://linuxtv.org/hg/~awalls/cx18-av-core/
>>> http://linuxtv.org/hg/~awalls/cx18-av-core/rev/9beb99150ab1
>>>
>>> Helen and ivtv-devel list readers,
>>>
>>> This patch needs some tests run:
>>>
>>> 1. Check that sound is better with the NTSC tuner
>>> 2. Check that S-Video and/or Composite in with NTSC didn't break
>>> 3. Check that switching back to the tuner, sound is still OK.
>>> 4. Check that PAL & SECAM still work on SVideo and/or Composite
>>> 5. Check that PAL and/or SECAM tuner sound is OK.
>>>
>>> I'll try and test what I can during the course of this week. I have
>>> high confidence that nothing is working worse than before :), but I
>>> can't check OTA PAL or SECAM (Maybe someone with a Compro H900 can
>>> check?).
>>>
>>> Since this bug was inhereted from the cx25840 module, I'm wondering if
>>> this is the cause of the PVR-150 tinny audio. If I can reproduce the
>>> tinny audio with my PVR-150MCE, I'll try to experiment with having the
>>> SIF gain controlled by the audio decoder (the correct thing todo) versus
>>> the video decoder (the wrong thing todo) of the CX2584x. This change
>>> can, with some difficulty, be ported to the cx25840 module, if that
>>> fixes the tinny audio.
>>>
>>> Regards,
>>> Andy

>> I downloaded the cx18-av-core repo and tested 1-3. Sound was good on a
>> couple of the previously bad channels, 29 & 41. Switching to input 1,
>> sound was still good, switching back to input 0, sound was still good on
>> channels 41 & 29.
>
> Good. I'm assuming your audio issues are resolved.

Yes, and sounds good on mythtv, too.

> I was able to run tests 1-3 with Composite as the alternate input (I
> need to dig up an S-Video cable), and test 4 with PAL as output by a
> PVR-350 into the HVR-1600's composite. Things were all OK - so I don't
> think I broke anything.
>
> Daniel provided positive feedback on the ivtv-devel list as well. I'll
> probably ask this to get pulled to the main v4l-dvb repo soon.

Many thanks,
Helen


_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

1 2  View All