[mythtv] green tint on bt8x8 caused by automatic 'adjust' filter

Torbjörn Jansson torbjorn.jansson at mbox200.swipnet.se
Thu Aug 19 12:04:31 EDT 2004

mythtv-dev-bounces at mythtv.org <> wrote:
> Can you try to figure out when this started happening, (ie, when did
> you check it out from CVS, have you been playing with cflags, etc)?
> My last build from CVS was 6/30, and there is no visible tint in
> recordings since then.  I would also suggest you try disabling the MMX
> code (simple to do, look at the filter init function).  It may be that
> something about your compiler or cflags has broken the MMX code, which
> is probably a bit more fragile than the LUT-based C version.
> On Thu, 19 Aug 2004 05:43:37 +0100, Andy McMullan
> <andy at andymcm.com> wrote:
>> I've been having a problem where sometimes recordings have a green
>> tint to them. Others have reported the same problem recently (e.g.
>> Chris Petersen) 
>> I've tracked down the problem to the automatic use of the 'adjust'
>> filter for bt8x8 cards in NuppelVideoRecorder.cpp. If I disable
>> this, the problem goes away. 
>> I don't know whether the problem is with the adjust filter itself, or
>> the code that invokes it in NuppelVideoRecorder.cpp, but I'd guess
>> the former. 
>> I suggest that until the problem is resolved the automatic use of
>> the filter is retracted. 
>> My system details are: Fedora Core 1, Athlon 1700+, Hauppauge bt878
>> (composite input, PAL). 
>> Andy Mc

I also get green colored recordings, but i'm also seeing messages like:

kernel: bttv0: SCERR @ 077c101c,bits: HSYNC OFLOW SCERR*
last message repeated 12 times
kernel: bttv0: timeout: drop=0 irq=1919422/1919422, risc=077c101c, bits:
kernel: bttv0: reset, reinitialize
kernel: bttv0: PLL: 28636363 => 35468950 . Ok


kernel: bttv0: SCERR @ 077c101c,bits: HSYNC OFLOW FBUS SCERR*
kernel: bttv0: SCERR @ 077c101c,bits: HSYNC OFLOW FBUS SCERR*

>From the kernel log.
Sometimes the recordings gets recorded all black, sometimes it's green
I've never figured out why it happends, but i'm suspecting my crappy
mainboard, a crapy via kt266a chipset, the one with pci hardware problems.

I've had theese problems more or less all the time, when i used linux 2.4
kernel it usualy lockedup, requiering a reset, instead of recording in

More information about the mythtv-dev mailing list