[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Best LCD for IIGS
On Nov 9, 9:24 am, Drew <GoggleD...@gmail.com> wrote:
> > I got the best results having the converter output at 640x480 (least
> > amount of processing), then letting my LCD do the upconversion to it's
> > native resolution, or better, letting my multisync CRT just slow down
> > to a natural rate of 640x480. These results might not hold true for
> > everyone -- just depends on whether their monitor's video handling
> > exceeds the converter's abilities.
>
> On my 20 inch Dell widescreen LCD results seem best using Aspect and
> 1024 by 768 for a larger picture, but if i switch to 1:1 640 seems
> best, but not sure if this is just because the picture is smaller. I
> wonder if trying a 15inch LCD and running at 640by 480 will be
> better...I am sure my work has a spare one ;-)
>
> > I tried the Amiga monitor approach also, but remember, not only is the
> > screen really small (too small for my eyes these days), but your video
> > won't be nearly as nice looking: the other big advantage to the
> > converter is that you're in 480p mode as opposed to 240p on the Amiga
> > screen ... meaning, for one, solid colors without missing interlace
> > lines.
>
> I know the older amiga (14 inch) screens suffers from larger dot
> pitch, but i quite like that retro look :-) and i prefer the overall
> look of the picture, seems clearer to me.
>
> > I get the nicest looking results using the coverter into a good CRT
> > VGA 17" monitor (a Dell/Sony Trinitron in this case). The ideal CRT
> > would be native 640x480... but I've never found one of those in 17" or
> > larger.
>
> Must try a VGA CRT as i agree that should be better than LCD.
>
> The pause/blank screen when the converter switches res and my monitor
> tries to also sync is a little annoying, when booting my GS i never
> see the Apple IIGS bit, just GS/OS loading. I also get a strange
> issue in Sierra games when i open the restore/save menu the converter
> seems to crash with only showing the top bit of the screen, I have to
> power off the converter then back on again and then seems fine, but i
> only have to do this once everytime i use the converter....odd.
>
> Cheers
<<On my 20 inch Dell widescreen LCD results seem best using Aspect
and
1024 by 768 for a larger picture, but if i switch to 1:1 640 seems
best, but not sure if this is just because the picture is smaller.>>
It's both that the pic is smaller, and because in that configuration,
you're minimizing the amount of processing (extrapolation) on the
video.
<< I wonder if trying a 15inch LCD and running at 640by 480 will be
better...I am sure my work has a spare one ;-) >>
It might. Ideally, an old 640x480 native LCD would theoretically be
best.. but the problem is that older LCD technology isn't very good
compared to the newer. To my eyes, a quality, hi-rez upscaling LCD
(such as my 1280x1024 Samsung 910MP) easily outperforms an older
technology 640x480 LCD, especially in terms of black level and
contrast. I tried it.
<<I know the older amiga (14 inch) screens suffers from larger dot
pitch, but i quite like that retro look :-) and i prefer the overall
look of the picture, seems clearer to me. >>
The larger dot pitch actually helps in this case with the color
dithering... but by 240p and 480p, I wasn't referring to dot pitch...
but interlaced video versus non interlaced (or progressive scan). My
eyes have greedily took to 480p or higher video many years ago, and
they get irritated by blank lines or line jiggle now.
<<The pause/blank screen when the converter switches res and my
monitor
tries to also sync is a little annoying, when booting my GS i never
see the Apple IIGS bit, just GS/OS loading.>>
Yeah, I find that annoying too.. I wondered if it's doing that in
response to the changing dot clocks coming the IIgs as video modes are
switched.. but as its dot sync to the 16mhz super hires mode is
imperfect, I'm actually not sure what it's doing. It could just be
that the V+H syncs coming from the IIgs are interrupted during mode
changes, thus simply requiring the converter to relock onto the
15.7khz signal.
JS