Is winuae able to detect emulated (Amiga) output resolution?

[ceztko]

Is possible to winuae to exactly know the resolution is should be outputting as if would be a real amiga? I was thinking about this wondering if it would be possible for winuae changing the host system (Windows, in this case) resolution according to the detected amiga resolution, instead of stretching/scale the screen. After all, if i have a 640x400 mode in Windows, why shouldn't i use it? Knowing the exact amiga "native" resolution, shouldn't be difficult for winuae, with a good heuristic, to choose the best resolution available choosing from the ones on the host system.

This feature could be interesting using devices capable of generating custom resolutions/sync frequencies, as discussed here .

[Toni Wilen]

You asked wrong question

WinUAE does it just like real Amigas do, it outputs single resolution (736x576 or something close enough with 3 possible pixel clock values) with varying sizes of "borders".

Problems with autodetection:

1: border is not always real border.
2: background color effects can happen in borders
3: multiple resolutions mixed
4: scrolling can move (invisible "hardware") borders

[I think I have replied to similar question at least twice already..]

[ceztko]

Originally Posted by Toni Wilen

You asked wrong question

WinUAE does it just like real Amigas do, it outputs single resolution (736x576 or something close enough with 3 possible pixel clock values) with varying sizes of "borders".

Ok, thanks. This is true for AGA too?
Following this reasoning, having a single resolution of 736x576 (50 hz with pal T V) should give the best "nostalgic" result, right? Please, can you specify these pixel clock values (or point me to a place where i can find more info about the topic in general)?

Originally Posted by Toni Wilen

[I think I have replied to similar question at least twice already..]

I'm sorry, but this even a reason to have an official faq with not-newbie topics .

[Toni Wilen]

I meant inside custom chips pixel clock be either 35ns (shres), 70ns (hires) or 140ns (lores). Output signal is still the same (PAL or NTSC)

Only solution for centering/autoresolution is non-trivial AI program that analyzes display data

Amiga display hardware is very flexible and many programs do all kinds of tricks with it..

Anyway, perfectly centered screen without borders is not what real Amigas do, everything works as designed

[ceztko]

Originally Posted by Toni Wilen

Only solution for centering/autoresolution is non-trivial AI program that analyzes display data

After your explanation, i perfectly understand why this is true.

Originally Posted by Toni Wilen

I meant inside custom chips pixel clock be either 35ns (shres), 70ns (hires) or 140ns (lores). Output signal is still the same (PAL or NTSC)

Ok, last one: googling, found that netbsd suggests 736x480 for 60hz modes in a fb driver. Could be this the best resolution for ntsc? However, if a single single resolution is used, why it isn't perfectly know and there's doubt around it?

I'll tell you what it does it look winuae in my philips CM8833 using this cable and a radeon 9250.

[sink]

i will testing somestuff with the arcadevga this week, if you found something interresting can u take a pic for looking on your tv the resultat?