So I take it that AspiringSquire's palette is absolutely final at this point? Perhaps BootGod would like to post his preferred palette?
As for the core issue: We already decided that if we were to continue working on this palette, we would need separate palettes for the composite-cable and RF-modulator cases...and that's just for NTSC. Would it be advisable for a qualified person to get to work looking at the output of a PAL NES?
grinvader wrote:They are *incredibly* different, especially direct broadcast signal.
Well, I'm pretty sure that Nintendo designed the palette for the PAL NES to alleviate the differences between the NTSC and PAL color gamuts, rather than just using a common reference point and letting the differences stand out. Does somebody have both NTSC and PAL TV sets and NES units so we can do a side-by-side comparison?
What this means is that we have to make *some* compromises. Although most NES emulator users play mostly NTSC games, I'm sure there are quite a few "important" PAL NES games out there. To minimize the inconvenience to the emulator user, we should create as few different palettes as possible (although the NTSC vs. PAL distinction is probably unavoidable). I don't mean to sound too pushy, but I would just like to clarify the issues at hand.
Oh, and one last thing: I originally suggested Loopy's palette demo as a hardware test. I just realized that Chris Covell's "RGB Demo" might be a little easier mapper-wise to get working on the hardware. Of course, no one seems to have the proper facilities to do this, but I may as well mention it for reference...
One more thing:
http://nesdev.parodius.com/NESTechFAQ.htm#ispalettergb *IS* the document I was talking about. Guess I didn't look closely enough...
In summary, if we want to continue working on our palettes, we ought to:
*Take a closer look at a PAL NES
*Decide how many different palettes we want to create
This signature intentionally contains no text other than this sentence.