TV.spin colorgrid
ericball
Posts: 774
One of the items of discussion in my colorbars topic is what colors the Propeller is capable of, particularly using TV.spin.· I have attached a simple program which displays all 128 possibilities (including $x9 and $xF).· Rows are $x8 (top) through $xF and columns are $0x (left) through $Fx.
The reason $x8 and $xF don't match the other rows is the color phase is inverted.· So $08 is the same as $8C with three times the color saturation and $0F is the same as $8B with three times the color saturation.
On my NTSC TV, $x9 is distorted but it's fine on my capture card.· The default is NTSC & Demoboard, but settings for PAL, Hydra & Hybrid are also included (just change which lines are commented out).
Note: these colors are using TV.spin.· If the driver uses a different colorburst phase the colors will be shifted.· But the colors will be the same, just a starting color.· (For NTSC at least, it might be possible to get tricky with PAL and change the colors slightly.)
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Composite NTSC sprite driver: http://forums.parallax.com/showthread.php?p=800114
NTSC color bars (template): http://forums.parallax.com/showthread.php?p=803904
Post Edited (ericball) : 5/17/2009 2:25:23 PM GMT
The reason $x8 and $xF don't match the other rows is the color phase is inverted.· So $08 is the same as $8C with three times the color saturation and $0F is the same as $8B with three times the color saturation.
On my NTSC TV, $x9 is distorted but it's fine on my capture card.· The default is NTSC & Demoboard, but settings for PAL, Hydra & Hybrid are also included (just change which lines are commented out).
Note: these colors are using TV.spin.· If the driver uses a different colorburst phase the colors will be shifted.· But the colors will be the same, just a starting color.· (For NTSC at least, it might be possible to get tricky with PAL and change the colors slightly.)
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Composite NTSC sprite driver: http://forums.parallax.com/showthread.php?p=800114
NTSC color bars (template): http://forums.parallax.com/showthread.php?p=803904
Post Edited (ericball) : 5/17/2009 2:25:23 PM GMT
Comments
I've a capture device, old Zenith TV, and a SONY WEGA that I test on. The older Zenith will buzz if the high intensity + color combination is present on screen.
Capture cards are more forgiving for sync level signals and or goofy timing. Most TV's will lose it far earlier than a capture card will. At least that is true for the capture devices I have (and had --I gave up the SGI last year.)
On the wiki, I've posted up a color set using values directly sent to waitvid, no phase flip, no correction, no masking. Just put the value into the waitvid and write out a pixel. There are actually 135 values that produce pixels, with 6 of them being intensity, with some out of spec. http://propeller.wikispaces.com/Colors That image actually displays well on most any display device, as the outta spec stuff is limited to a small fraction of the overall screen display. This appears to matter on older devices. The lighter grey background helps. I produced it when trying to sort out what did what on a waitvid color wise.
On that screenie, the bottom row of colors are the standard propeller colors. The strip along the right side are a few that I missed when building the CLUT table. They didn't fit in my scheme well, so I just drew them outright. The multi-color section in the middle is a mixture of those standard propeller colors on a non-color interlaced (fixed chroma phase), non vertically interlaced, NTSC signal. Pixel resolution is 160 horizontal for the safe area. If NTSC alternating color phase is used, the square set of mixed colors is not possible, but horizontal resolution improves to 320 pixels.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Propeller Wiki: Share the coolness!
Chat in real time with other Propellerheads on IRC #propeller @ freenode.net
Safety Tip: Life is as good as YOU think it is!