Tivo Input RGB settings

Advertisements

The black & white crushing on my tivo when in RGB has been annoying me for some time, and after much searching I came across LJ's page which mentions 0x42 on the i2c bus.

Having read the manual for the chip thats at this address, it seems to me that the correct values for the input side of the Tivo should be as follows (the ITU settings in the docs):

0x2a = 128
0x2b = 64 (or 68 possibly)
0x2c = 64

So setting them as ./iicsetw 0x42 0x2a 128 etc

I rebooted to wipe out my existing iicsetw settings for the output side and tried this from a telnet prompt and it looks to me as if the blacks are being preserved correctly. I personally found 0x2a to be nicer with 136 as its value, but that might depend on the levels being output by the device attached. In this case a Samsung STB.

Reading around the forum, it looks like the common feeling is that the settings in LJ's patch are ignored and so the only way to apply these is with iicsetw from a telnet prompt. Of course this gets wiped out on every channel change which makes it useless.

Has anyone found a way to set these settings correctly without manually resetting them every single time you change channel? I saw mention of a modified palmod which might do that, but I was unable to find this.

Now we have an iicsetw which doesn't lock the Tivo up, is there another way we could do this?

 

For a long time I was under the impression that changing the output was the right way to do it simply because the UI and in particular the SKY One logo in the UI was so bright.

I have since decided that the UI is bright simply because Tivo chose colours which looked good on the composite output. When in RGB mode the colours appear brighter. I suspect they also changed the input settings to try and compensate for losses caused by composite input into the tivo.

A file from my Tivo found its way onto my PC and the black & white crushing is still present, so to me that suggests the input side is where we need to correct it. My manual changes produce results which look vastly better on my TV.

It makes sense to me that we should set the input & output chips to the default ITU setttings.