[Coco] Current Status of the "Help Send A Fellow CoCoNut To This Year's CoCoFEST" Campaign

[embsys dev]

I have no problem with the assertion that coco NTSC output completely
sucks. I got a coco2 a few weeks ago (hadn't used one since 1984 or so when
I got a PC Jr haha). Took a look at it on the scope and went "ho lee
sheeeeeeit".  So much is wrong-  black level, white level, porch widths,
color phase, etc. It's really kind of amazing that it works at all.  I
guess sync and burst are good enough, but color and noise, omfg.

Sorry for going on. What say we bury this poor dead horse, eh?



On Sat, Feb 14, 2015 at 5:53 PM, Arthur Flexser <flexser at fiu.edu> wrote:

> On Sat, Feb 14, 2015 at 7:46 PM, embsys dev <embsysdev at gmail.com> wrote:
>
> > Ah yes, RGB input, sorry. I know, NTSC = Never Twice the Same Color, heh.
> > But since the coco3 max resolution is 640x192x4, and 320x192x16 is as
> good
> > "full color" as you can get, I don't see any benefit to using RGB
> through a
> > fancy FPGA scan doubler, no matter how good it is, the source signal is
> the
> > limiting factor.
> >
>
> You wouldn't say the source resolution was the limiting factor if you had
> ever directly compared the CoCo 3's RGB output to its composite.  I had
> a Sony KV1311CR that could switch between the two with the push of a
> button, and there was no comparison.  Hugely sharper with the RGB.
>
> Art
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>