[Coco] Stable colours

[S Klammer]

With regards to SG6, the Coco3 will actually allow holding either F1 or F2
to select red/orange or blue shift...

Although different pixel patterns can elicit different shades, it is
whether the pixel is odd or even numbered that determines the red/orange or
blue... so 01 is red, 10 is blue whereas 11 would be white.  Would that be
workable with just the one variable for the previous pixel?

Shain
On Sep 30, 2014 1:19 PM, "Luis Antoniosi (CoCoDemus)" <
retrocanada76 at gmail.com> wrote:

> well I'm using the 2-port RAM which is one read and one write. I guess
> there is one with both. But it would add more and more wires, more and more
> LE's for a crappy result.
>
>
> Luis Felipe Antoniosi
>
>
>
> On Tue, Sep 30, 2014 at 1:15 PM, Luis Antoniosi (CoCoDemus) <
> retrocanada76 at gmail.com> wrote:
>
> >
> > On Tue, Sep 30, 2014 at 12:48 PM, Frank Swygert <farna at amc-mag.com>
> wrote:
> >
> >> artificial artifacts
> >
> >
> > You are talking about the coco1 SG6, the infamous red that is in fact
> > orange but if you are luck you get it blue...
> >
> > VCC emlator does a crap job emulating them. I prefer the MESS which is
> > close to the NTSC but the mess is much more complex.
> >
> > Also, I use internal RAM for 2 lines only. I have one incoming line (from
> > genlock) and one outgoing line (vga output). Those lines are stored/load
> > from/into the main SDRAM (which is slow and must be loaded/stored in
> burst
> > mode).
> >
> > In one clock cycle I can only have one pixel. I cannot get the next. The
> > maximum I can keep the previous pixel in a variable. So at best case it
> > would look like VCC, shifted because the first pixel wont the artifacted,
> > suppose:
> >
> > 00 10 10 10 00 00
> >
> >
> > The first 1 would remain black as the 0 would be blue, or red, or
> > orange...what would create hard edges.. :P
> >
> >
> >
> >
> >
> >
> > Luis Felipe Antoniosi
> >
> >
> >
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>