Well, I did a "yum update" on my myth machine, and my captions are no longer garbled. The ivtv version is the same (I compile my own ivtv modules from svn). The only thing that I think was relevant is the kernel. It seems odd to me that the kernel version affected this, however. I double- and triple-checked to make sure that only the ivtv modules were being used, no kernel versions of tveeprom or the like.
current ivtv dmesg dump follows - thanks for all the suggestions, and I may send another update after I try booting back to the old kernel to verify that it is just the kernel version that makes the difference. ivtv: ==================== START INIT IVTV ==================== ivtv: version 0.4.0 (tagged release) loading ivtv: Linux version: 2.6.12-1.1381_FC3 686 REGPARM 4KSTACKS gcc-3.4 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. ivtv0: Autodetected WinTV PVR 350 card (iTVC15 based) PCI: Found IRQ 11 for device 0000:00:0d.0 tveeprom: ivtv version tveeprom: Hauppauge: model = 48132, rev = K268, serial# = 7875535 tveeprom: tuner = LG TAPE H001F MK3 (idx = 68, type = 47) tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000) tveeprom: audio processor = MSP4448 (type = 1b) tveeprom: decoder processor = SAA7115 (type = 13) ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50] tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #0 ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61] saa7115 1-0021: saa7115 found @ 0x42 (ivtv i2c driver #0) ivtv0: i2c attach to card #0 ok [client=saa7115, addr=21] saa7127 1-0044: saa7129 found @ 0x88 (ivtv i2c driver #0) ivtv0: i2c attach to card #0 ok [client=saa7127, addr=44] msp34xx: ivtv version msp34xx: init: chip=MSP3448W-A2, has NICAM support, simple (D) mode, simpler (G) no-thread mode msp34xx: $Id$ compiled on: Dec 18 2005 19:13:11 ivtv0: i2c attach to card #0 ok [client=MSP3448W-A2, addr=40] tda9885/6/7: (ivtv) chip found @ 0x86 ivtv0: i2c attach to card #0 ok [client=tda9887, addr=43] ivtv0: loading /lib/modules/ivtv-fw-enc.bin ivtv0: loading /lib/modules/ivtv-fw-dec.bin ivtv0: Encoder revision: 0x02050032 ivtv0: Decoder revision: 0x02020023 ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total) ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total) ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total) ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total) ivtv0: Create encoder radio stream ivtv0: Allocate DMA decoder MPEG stream: 16 x 65536 buffers (1024KB total) ivtv0: Allocate DMA decoder VBI stream: 512 x 2048 buffers (1024KB total) ivtv0: Create decoder VOUT stream ivtv0: Allocate DMA decoder YUV stream: 24 x 43200 buffers (1024KB total) ivtv0: loading /lib/modules/ivtv_init_mpeg.bin tuner: type set to 47 (LG NTSC (TAPE series)) by ivtv i2c driver #0 spurious 8259A interrupt: IRQ7. ivtv0: Initialized WinTV PVR 350, card #0 ivtv: ==================== END INIT IVTV ==================== On 12/14/05, Scott Reynolds <[EMAIL PROTECTED]> wrote: > I manually imported this file into MythTV. The captions display just > fine on my system. This confirms that your encoding is OK -- it's just > playback that's a problem. > > We have the same card, we're running the same firmware versions. The > cards are configured virtually identically. I'm using ACPI to > configure PCI interrupts, and a newer kernel. I'm not sure if either > of those could actually make a difference. > > --scott > > On 12/13/05, Mike Shields <[EMAIL PROTECTED]> wrote: > > I have a 45 mb mpg file (renamed .nuv from mythtv) at > > > > http://shieldsworld.com/files/testvideo.zip > > > > (zipped just so browsers will download instead of trying to play in place) > > > > captured by mythtv 0.18.1 on FC3 at 640x480, using ivtvctl -x 1 -b cc -w cc > > _______________________________________________ > ivtv-devel mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-devel > _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
