RGB2HDMI Mod Pallet Help?

[Darklord]

Per suggestions, when I get the chance I'm going to pull it from my STacy
and use my phone to examine it. If there's something obvious (the only
"thing" I'm capable of finding), hopefully I can see it.

Is there any chance this could be due to settings alone? I've got a few
oddities (just IMHO) that might be perfectly normal.

For example, it always says "50mhz ST", even though I picked the option
that's supposed to give both 50 and 60mhz support, according to the guide.

Also, the OSD, always shows up partially scrolled off the left side of the screen.

To get the picture where I wanted it on the replacement LCD, that was the only
way I could get it to work.

Here's a picture of my current settings:

STacy - RGB2HDMI - OSD.JPG (155.17 KiB) Viewed 344 times

[Darklord]

BTW, here are 2 captures from the Pi:

Pi-Capture01.png (19.83 KiB) Viewed 334 times

Pi-Capture02.png (8.31 KiB) Viewed 334 times

Thanks.

[Steve]

Looks to me like there is an issue with the replacement LCD, since the Pi capture looks perfect (I assume you've set a blue background) the colour gradients look good. So that means the RGB going to the Pi from the Stacy is correct, but it's what happens on the output that seems to be the problem. How is that monitor plugged in to the rgbtohdmi? Does it have a native hdmi interface, or are you using a hdmi to VGA converter for it. It could be the converter or the screen.

[Darklord]

Looks to me like there is an issue with the replacement LCD, since the Pi capture looks perfect (I assume you've set a blue background) the colour gradients look good. So that means the RGB going to the Pi from the Stacy is correct, but it's what happens on the output that seems to be the problem. How is that monitor plugged in to the rgbtohdmi? Does it have a native hdmi interface, or are you using a hdmi to VGA converter for it. It could be the converter or the screen.

I'm using one of those "slim" HDMI cables like Derkom recommended in his STacy message thread here.

Sline Line HDMI Cables.JPG (87.21 KiB) Viewed 291 times

I could easily swap it out for a standard HDMI cable and see if that makes a difference. I'll report back
later.

[Steve]

So the LCD takes hdmi direct?

[Darklord]

So the LCD takes hdmi direct?

Yes, HDMI and VGA inputs. Oh, I think it might also have a DVI
input as well. You can see the setup here:

Capture.JPG (179.79 KiB) Viewed 264 times

When I swap cables for a "normal" HDMI cable, I'll also feed
the replacement LCD a different HDMI signal, from my Win10
desktop, just to see what that does (suggesed by Joska in
another forum).

I'll report back later this evening.

Thanks.

[Darklord]

Okay, some interesting results this evening. Here's the replacement STacy LCD panel
displaying a video feed from my Kubuntu Linux laptop. It seems to be just fine:

Kubuntu Linux on a STacy Screen.JPG (161.87 KiB) Viewed 242 times

Now, I took pictures of booting up with TOS v3.06, Pak board enabled and TOS v1.4, Pak board
disabled. You'll notice right away that, without me changing or doing anything else, it boots up
from the 50hz profile with TOS v3.06/Pak board enabled and 60hz with TOS v1.4/Pak disabled:

TOS v306 Bootup (50hz).JPG (122.48 KiB) Viewed 242 times

TOS v104 Bootup (60hz).JPG (144.04 KiB) Viewed 242 times

With TOS v1.4/Pak disabled and 60hz, the Timer_B software gives a better result (for some
reason, the red shows up much lighter and the black border is actually there but not showing):

TOS v104 or NVDI Capture.JPG (164 KiB) Viewed 242 times

It also shows up okay on the SC1224 monitor video output:

STacy - SC1224 Capture.JPG (185.32 KiB) Viewed 242 times

[Darklord]

I wanted to split up the rest of this because I'm leaning towards this all being a couple
of different issues. I think the different versions of TOS giving different 50/60hz is one
issue and then there's the color pallet problem.

I did a clean boot up, no hard drive, floppy only, all AUTO folder/ACC/CPX's disabled.
This is TOS v1.4, "About" menu option being shown:

TOS v104 (About).JPG (132.51 KiB) Viewed 243 times

Now here's TOS v3.06, with everything still disabled:

TOS v306 Clean Boot (No AUTO_ACC_CPX).JPG (137.92 KiB) Viewed 243 times

Here is what happens when I boot up with TOS v3.06 and everything enabled
again. Notice the pallet:

TOS v306 (Without NVDI).JPG (142.04 KiB) Viewed 243 times

Now here's something really interesting that I just discovered after playing
around with things a bit. If I enable NVDI, it clears up the pallet problem!

TOS v306 (With NVDI).JPG (136.28 KiB) Viewed 243 times

I'm sure there's a reason for that - I'm just not sure what it is...

[Steve]

@Darklord as far as I know it's normal for NVDI to change the palette like that. On my Ataris the desktop background always changes slightly, but I've never been bothered by it or felt the need to tweak the colours. Everything else always seems the same.

In MiNT there's different palette options inside XaAES, I think the options are palette=gem or palette=NVDI.

[Darklord]

@Darklord as far as I know it's normal for NVDI to change the palette like that. On my Ataris the desktop background always changes slightly, but I've never been bothered by it or felt the need to tweak the colours. Everything else always seems the same.

In MiNT there's different palette options inside XaAES, I think the options are palette=gem or palette=NVDI.

Okay, I'm sort of familiar with that - although NVDI doesn't change the pallet on my Mega ST or Mega STe.

Keep in mind, it's not that NVDI is changing the pallet. It's restoring the messed up pallet that I've been
seeing to normalcy.