I just tested the new 0.3.3e and it looks nice. I haven't had much trouble getting my 150mce pal working on releases since the tuner 58 got introduced. I noticed something in 0.3.3e though, but it only appears when I use ptune.pl. The sound that it makes when changing channels has become worse. It used to be a small tick or some high freq peak, but now it sounds more like when you're changing channels on an old fm radio with mechanical buttons... at least some of the changes make this noice - I think tuning changes between channels that very close to each other doesn't make this noice. Unfortunately I don't know what version introduced this sound because I use mythtv, which turns down the volume when changing channels, but if it's of any interrest I would look into the matter.

BTW: I use no options to "modprobe ivtv"

ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.3.3 (e) loading
ivtv: Linux version: 2.6.11 preempt PENTIUM4 gcc-3.3
ivtv: In case of problems please include the debug info
ivtv: between the START INIT IVTV and END INIT IVTV lines when
ivtv: mailing the ivtv-devel mailinglist.
ivtv: Autodetected WinTV PVR 150 card
ivtv: Found an iTVC16 based chip
ACPI: PCI interrupt 0000:00:0d.0[A] -> GSI 17 (level, low) -> IRQ 17
ivtv: Unreasonably low latency timer, setting to 64 (was 32)
ivtv: XXX PCI device: 0x0648 vendor: 0x1039
tveeprom: Hauppauge: model = 26559, rev = C260, serial# = 7705475
tveeprom: tuner = LG S001D MK3 (idx = 60, type = 58)
tveeprom: tuner fmt = PAL(B/G) PAL(I) SECAM(L/L) PAL(D/K) (eeprom = 0x74, v4l2 = 0x00400e17)
tveeprom: audio_processor = MSP3410D (type = 5)
ivtv: i2c attach [client=tveeprom[50],ok]
ivtv: Tuner Type 58, Tuner formats 0x00400e17, Radio: yes, Model 0x008d2590, Revision 0x00000001
ivtv: PAL tuner detected
ivtv: SECAM tuner detected
ivtv: Radio detected
tuner: Ignoring new-style parameters in presence of obsolete ones
tuner: chip found at addr 0xc2 i2c-bus ivtv i2c driver #0
ivtv: i2c attach [client=(tuner unset),ok]
cx25840: starting probe for adapter ivtv i2c driver #0 (0x10005)
cx25840: detecting client on address 0x88
cx25840: writing init values
cx25840: FW image '/lib/modules/HcwMakoA.ROM' of size 14264 loaded.
cx25840: FW image md5 digest: 3a4803384f749d644ee1f1ca9dcb12fa
cx25840: FW image sha1 digest: 2b5e6292b7391c980b93d156cf6b34178ce770f6
cx25840: Status: cx258433 (DEVICE_ID)
ivtv: i2c attach [client=cx25840[50],ok]
ivtv: i2c attach [client=wm8775[50],ok]
ivtv: Encoder revision: 0x02040011
ivtv: Configuring WinTV PVR 150 card with 5 streams
ivtv: Registered v4l2 device, streamtype 0 minor 0
ivtv: Create DMA stream 0 using 1024 16384 byte buffers 0 kbytes total
ivtv: Allocate DMA stream 0 using 1024 16384 byte buffers 16777216 kbytes total
ivtv: Registered v4l2 device, streamtype 1 minor 32
ivtv: Create DMA stream 1
ivtv: Allocate DMA stream 1
ivtv: Registered v4l2 device, streamtype 2 minor 224
ivtv: Create DMA stream 2 using 40 52224 byte buffers 0 kbytes total
ivtv: Allocate DMA stream 2 using 40 52224 byte buffers 2097152 kbytes total
ivtv: Registered v4l2 device, streamtype 3 minor 24
ivtv: Create DMA stream 3 using 455 4608 byte buffers 0 kbytes total
ivtv: Allocate DMA stream 3 using 455 4608 byte buffers 2097152 kbytes total
ivtv: Registered v4l2 device, streamtype 4 minor 64
ivtv: Create stream 4
ivtv: Allocate stream 4
ivtv: Setting Tuner 58
tuner: type set to 58 (LG PAL TAPE-S001D) by ivtv i2c driver #0
cx25840: decoder set input (6)
cx25840: Tuner Input
ivtv: ivtv_enc_thread: pid = 3945, itv = 0xe0dd86a0
cx25840: set audio: 0x01
ivtv: Switching standard to PAL.
cx25840: decoder set norm PAL
cx25840: set audio: 0x01
ivtv: Initialized WinTV PVR 150, card #0
ivtv: ==================== END INIT IVTV ====================



On Tue, 19 Apr 2005, Chris Kennedy wrote:

I became aware of a problem in the cx25840 digitizer which we had
hit since changing the code from Ulfs original setup, where we would
reset the registers upon starting a capture.  It seems if we don't
do this just right, then the chip doesn't setup itself to a good
state for things like the proc-amp and possibly other settings.  I had
to figure out the best way to keep from losing other settings we manually
set but still give it this reset.  So this attempts that, seems like it
should work, please test this if you've had problems with pvr150/500 cards
since the version 0.3.2u or so, and also if you are currently doing fine
with these cards, so we can make sure this is a good overall global solution
for everyone (and really the right thing to do).  Video proc-amp settings
would be dark and red without these changes, and this could also be why
some don't have sound anymore and various other things (like no capture).

#0.3.3e: http://www.ivtv.tv/releases/ivtv-0.3/


Thanks, Chris -- --- Chris Kennedy / [EMAIL PROTECTED] Engineer KMOS-TV/KTBG-FM Broadcasting Services Department Central Missouri State University


------------------------------------------------------- This SF.Net email is sponsored by: New Crystal Reports XI. Version 11 adds new functionality designed to reduce time involved in creating, integrating, and deploying reporting solutions. Free runtime info, new features, or free trial, at: http://www.businessobjects.com/devxi/728 _______________________________________________ ivtv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel



-------------------------------------------------------
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

Reply via email to