Hi, the 1st line of the tv picture is constantly dashed here, e.g. - - - -- - -- -- - - -- -- ---------------------- This is a cosmetic problem but nevertheless annoying ! I think this problem existed since the early days of bttv. Do others see this artefact, too? Any clueful hints on causes for this? Regards, Gunther P.S. Further data/Kind-of-Workaround: When switching to "grabdisplay" in the default size 384x288 the line is fine (and the pictures increases sligtly in size, both horizontal and vertical) ! This does not help as soon as vsize>288, so this could be a subtle scaling problem in the BTTV-Risc code or similar? Side note: With "grabdisplay" unfortunately the last line is wrong:-( | ------------------- | The artefacts combination depends on the tv channel selected: RTL (CH60) in the only channel without artefacts, here! dmesg-Output: bttv: driver version 0.7.61 loaded bttv: using 2 buffers with 2080k (4160k total) for capture bttv: Host bridge needs ETBF enabled. bttv: Bt8xx card found (0). PCI: Found IRQ 11 for device 00:0c.0 PCI: The same IRQ used for device 00:0c.1 bttv0: Bt878 (rev 2) at 00:0c.0, irq: 11, latency: 32, memory: 0xe2000000 bttv0: subsystem: 0070:13eb => Hauppauge WinTV => card=10 bttv0: model: BT878(Hauppauge new (bt878)) [autodetected] bttv0: enabling ETBF (430FX/VP3 compatibilty) bttv0: Hauppauge msp34xx: reset line init i2c-dev.o: Registered 'bt848 #0' as minor 0 msp34xx: init: chip=MSP3410D-B4, has NICAM support msp3410: daemon started bttv0: i2c attach [MSP3410D-B4] i2c-core.o: client [MSP3410D-B4] registered to adapter [bt848 #0](pos. 0). tuner: chip found @ 0x61 bttv0: i2c attach [(unset)] i2c-core.o: client [(unset)] registered to adapter [bt848 #0](pos. 1). i2c-core.o: adapter bt848 #0 registered as adapter 0. bttv0: Hauppauge eeprom: model=61334, tuner=Philips FM1216 (5), radio=yes bttv0: i2c: checking for MSP34xx @ 0x80... found bttv0: i2c: checking for TDA9875 @ 0xb0... not found bttv0: i2c: checking for TDA7432 @ 0x8a... not found
