Re: Color fringe hires behavior

["Bryan Parkoff" <nospam@nospam.com>]

"Michael J. Mahon" <mjmahon@aol.com> wrote in message 
puOdnSegHN1A_sfYnZ2dnUVZ_vqdnZ2d@comcast.com">news:puOdnSegHN1A_sfYnZ2dnUVZ_vqdnZ2d@comcast.com...
> BLuRry wrote:
>>>The independence of these two problems strongly suggests that any
>>>emulation should layer the display rendering into a "system-dependent"
>>>part and a "display-dependent" part, so that users could select the
>>>emulated display that they would like to "attach" to the system
>>>emulator, and so that new "displays" could be easily emulated.
>>
>>
>> I agree 100%.  The approach I'm taking is to generate everything in the
>> form of a monochrome 560x192 bit pattern.  From there it can be copied
>> to the screen as-is for monochrome, or via some form of translation
>> (simple 4-bit rgb conversion, ntsc approximation, etc)  The ntsc part
>> will wait, but I think I have a handle on the "convert to a 560x192 bit
>> pattern" part.
>
> Sounds great!
>
> IIRC, the MAME project is doing an NTSC emulation, or was...

    I can tell that MAME and MESS are doing an attempt to emulate NTSC, but 
it does not look great.  You want solid white pixel.  Emulated NTSC looks 
like four vertical lines.  First and third vertical lines are white and 
second and fourth vertical lines are less than white like little light gray. 
When you try to convert from NTSC signal to RGB signal using conventor 
device, you try to look at the RGB monitor closely, you may notice vertical 
lines.

Bryan Parkoff