Testing: Support for more HDMI resolutions and other changes.

https://github.com/MiSTer-devel/Main_MiSTer/wiki

Moderators: Mug UK, Zorro 2, spiny, Greenious, Sorgelig, Moderator Team

Kev79
Atarian
Atarian
Posts: 5
Joined: Sat Oct 06, 2018 12:20 pm

Re: Testing: Support for more HDMI resolutions and other changes.

Postby Kev79 » Sat Oct 20, 2018 2:27 pm

Does anyone here know the custom mode settings for MiSTer.ini needed to get 1920x1200@60 and 1600x1200@60 display modes working?

Sorgelig
Fuji Shaped Bastard
Fuji Shaped Bastard
Posts: 3513
Joined: Mon Dec 14, 2015 10:51 am
Location: Russia/Taiwan

Re: Testing: Support for more HDMI resolutions and other changes.

Postby Sorgelig » Sat Oct 20, 2018 11:11 pm

Kev79 wrote:Does anyone here know the custom mode settings for MiSTer.ini needed to get 1920x1200@60 and 1600x1200@60 display modes working?

max horizontal resolution is 1920
max vertical resolution is 1080

you cannot set any of mentioned resolutions.

Kev79
Atarian
Atarian
Posts: 5
Joined: Sat Oct 06, 2018 12:20 pm

Re: Testing: Support for more HDMI resolutions and other changes.

Postby Kev79 » Sun Oct 21, 2018 2:01 am

According to the DE10-Nano User Manual the UXGA (1600x1200) resolution is supported so I used http://www.epanorama.net/faq/vga2rgb/calc.html to get the correct parameters.

These settings:

video_mode=1,1600,64,192,304,1200,1,3,46,162

work fine with my Dell U2410 monitor. If you want ro try this mode use these settings at your on risk.

Sorgelig
Fuji Shaped Bastard
Fuji Shaped Bastard
Posts: 3513
Joined: Mon Dec 14, 2015 10:51 am
Location: Russia/Taiwan

Re: Testing: Support for more HDMI resolutions and other changes.

Postby Sorgelig » Sun Oct 21, 2018 3:49 am

probably because buffer size 1600x1200 is less than 1920x1080. But this is anyway not supposed to be supported resolution. 162MHz is beyond maximum which is 148.5MHz.
If it works for you, then OK.

wesbrown18
Atarian
Atarian
Posts: 4
Joined: Thu Nov 22, 2018 9:16 pm

Re: Testing: Support for more HDMI resolutions and other changes.

Postby wesbrown18 » Sun Dec 09, 2018 10:56 pm

Interestingly, my experience was in between Kev79's 'it works', and sorgelig's 'it shouldn't work'. The answer appears to be somewhere in between.

Setting the pixel clock to

Code: Select all

162
didn't work -- it may be a limitation in the DE10 Nano, or in the monitor. However, setting the pixel clock to the aforementioned

Code: Select all

148
worked.

So, I have a display running at 1600x1200x55hz. It appears to work reasonably well as it's within my Dell 2001FP's tolerances, except almost all the cores don't appear to use the extra lines at the bottom, despite being set to 4:3.

Sorgelig
Fuji Shaped Bastard
Fuji Shaped Bastard
Posts: 3513
Joined: Mon Dec 14, 2015 10:51 am
Location: Russia/Taiwan

Re: Testing: Support for more HDMI resolutions and other changes.

Postby Sorgelig » Mon Dec 10, 2018 9:10 am

wesbrown18 wrote:Interestingly, my experience was in between Kev79's 'it works', and sorgelig's 'it shouldn't work'. The answer appears to be somewhere in between.

your experiment doesn't contradict to my words.
You've lowered the pixel clock and your Monitor supports arbitrary pixel clock. So you can have higher resolution in cost of lower frame rate.

In new releases where i switched to new scaler, there is no predefined buffer size, so 1920x1200 should be possible now if pixel clock is not an issue. New scaler hasn't been checked against max pixel clock. With old scaler i could use up to 180MHz.

kitrinx
Atari User
Atari User
Posts: 43
Joined: Wed Sep 26, 2018 6:03 am

Re: Testing: Support for more HDMI resolutions and other changes.

Postby kitrinx » Mon Dec 10, 2018 5:19 pm

Sorgelig wrote:In new releases where i switched to new scaler, there is no predefined buffer size, so 1920x1200 should be possible now if pixel clock is not an issue. New scaler hasn't been checked against max pixel clock. With old scaler i could use up to 180MHz.


1920x1200 actually does seem to work pretty well in the new scaler. I've been doing some minimal testing with this string:

video_mode=1920,48,32,80,1200,3,6,26,154130

Integer scaling works correctly with it as well. That will probably be nice for 4k displays.

wesbrown18
Atarian
Atarian
Posts: 4
Joined: Thu Nov 22, 2018 9:16 pm

Re: Testing: Support for more HDMI resolutions and other changes.

Postby wesbrown18 » Tue Dec 11, 2018 2:54 am

Sorgelig wrote:
wesbrown18 wrote:Interestingly, my experience was in between Kev79's 'it works', and sorgelig's 'it shouldn't work'. The answer appears to be somewhere in between.

your experiment doesn't contradict to my words.
You've lowered the pixel clock and your Monitor supports arbitrary pixel clock. So you can have higher resolution in cost of lower frame rate.


Makes sense to me, I wasn't saying there was a direct contradiction.

In new releases where i switched to new scaler, there is no predefined buffer size, so 1920x1200 should be possible now if pixel clock is not an issue. New scaler hasn't been checked against max pixel clock. With old scaler i could use up to 180MHz.


I upgraded to the latest MiSTER firmware file, as well as the december release of the Minimig core. I also put the MiSTER on the network so that I could iteratively increase the pixel clock using ssh and vi.

At a resolution of 1600x1200, I've inched the pixel clock one by one until clock of 153MHz -- translating to an effective refresh rate of -56.7hz. When I increment it to 154, with a reported ~57hz, we start to see noise on the screen in the Menu. The Minimig core sometimes throws garbage onto the screen, and sometimes it works. Sometimes I get a `HDCP error` reported by the Framemeister. At 155mhz, the menu sometimes works, but the Minimig core goes crazy on the screen.

Should I be expecting this to work at 60hz, with a pixel clock of 162mhz, with the new scaler?

Sorgelig
Fuji Shaped Bastard
Fuji Shaped Bastard
Posts: 3513
Joined: Mon Dec 14, 2015 10:51 am
Location: Russia/Taiwan

Re: Testing: Support for more HDMI resolutions and other changes.

Postby Sorgelig » Tue Dec 11, 2018 5:02 am

kitrinx wrote:1920x1200 actually does seem to work pretty well in the new scaler. I've been doing some minimal testing with this string:

video_mode=1920,48,32,80,1200,3,6,26,154130

Integer scaling works correctly with it as well. That will probably be nice for 4k displays.


4K is multiple of 1920x1080, not 1920x1200.

wesbrown18 wrote:Should I be expecting this to work at 60hz, with a pixel clock of 162mhz, with the new scaler?

There is no correlation between old and new scalers. So try and you will see.

kitrinx
Atari User
Atari User
Posts: 43
Joined: Wed Sep 26, 2018 6:03 am

Re: Testing: Support for more HDMI resolutions and other changes.

Postby kitrinx » Tue Dec 11, 2018 3:22 pm

Sorgelig wrote:4K is multiple of 1920x1080, not 1920x1200.


I know this, but scaling from 320x240->1920x1200 ->3840x2160 ends up first as 5x integer scaled image, so the end result when the tv scales it further is usually a nice sharp image with pixels that appear even (because of the high resolution). Effectively do 4k interpolation instead of 1200p or 1080p interpolation.

Alternative if you're lucky your 1080p tv crops the extra lines from 1200 to 1080p evenly, and you get get 5x integer scaling and only lose a little of the visible area.

Soltan's coefficients are so good though, integer scaling isn't as big a deal as it is elsewhere.

Sorgelig
Fuji Shaped Bastard
Fuji Shaped Bastard
Posts: 3513
Joined: Mon Dec 14, 2015 10:51 am
Location: Russia/Taiwan

Re: Testing: Support for more HDMI resolutions and other changes.

Postby Sorgelig » Tue Dec 11, 2018 4:08 pm

you can use 640x480 resolution instead of 1920x1200.

wesbrown18
Atarian
Atarian
Posts: 4
Joined: Thu Nov 22, 2018 9:16 pm

Re: Testing: Support for more HDMI resolutions and other changes.

Postby wesbrown18 » Wed Dec 12, 2018 3:15 am

Sorgelig wrote:
wesbrown18 wrote:Should I be expecting this to work at 60hz, with a pixel clock of 162mhz, with the new scaler?

There is no correlation between old and new scalers. So try and you will see.


I am a little confused; we may be miscommunicating. I think I already tried with the combination of:

* With the latest `MiST` firmware file.
* With the latest `Minimig` core file,

... with the results as described, of MiSTer not working at 1600x1200 at any hz rate higher than ~57hz or a pixel clock of 154mhz.

Is there anything further I need to be doing, setting wise, to 'try with the new scaler code' and see?

wesbrown18
Atarian
Atarian
Posts: 4
Joined: Thu Nov 22, 2018 9:16 pm

Re: Testing: Support for more HDMI resolutions and other changes.

Postby wesbrown18 » Sat Dec 15, 2018 9:37 pm

Using the latest version of the following components, some updated in the last day or so:

  • MiSTer_20181213.dms (MiSTer, 2018-12-13)
  • menu_20180902.rbf (menu, 2018-09-02)
  • Minimig_20181216.rbf (Minimig, 2018-12-16)

With the aid of my Framemeister xRGB-mini in 'HDMI passthrough' and in 'semi-passthrough' mode:

The following modeline works -- (this takes me back to 1997 when I was writing XFree86 modelines ... ):

Code: Select all

video_mode=1,1600,64,192,304,1200,1,3,46,162


It yields a 1600x1200x60hz picture at a pixel clock of 161.21mhz!

So the new scaler does work really well at higher than 1080p resolutions. There was some confusion over what the latest version of the cores were.

:cheers:

------

However, when vsync_adjust=1, the signal is out of sync for my monitor when the Minimig core is in PAL mode. The Framemeister reports that it is receiving a signal of *1600x1200x50.46hz*, with a pixel clock of *136.81mhz*.

When reading the description in the MiSTER.ini config file:

Code: Select all

; For proper adjusting and to reduce possible out of range pixel clock, use 60Hz HDMI video
; modes as a base even for 50Hz systems.


... it's quite confusing to me. Should the vsync-adjust parameter be adjusting so far off the 60Hz base?

Sorgelig
Fuji Shaped Bastard
Fuji Shaped Bastard
Posts: 3513
Joined: Mon Dec 14, 2015 10:51 am
Location: Russia/Taiwan

Re: Testing: Support for more HDMI resolutions and other changes.

Postby Sorgelig » Sat Dec 15, 2018 9:54 pm

wesbrown18 wrote:... it's quite confusing to me. Should the vsync-adjust parameter be adjusting so far off the 60Hz base?

recommendation is based on the fact that with vsync_adjust=1 output framerate will match input and if you use 50hz base and input frame rate is 60hz, then pixel clock will increase by 20% and will out or supported range.
If you are sure the core is 50hz-only then you can use 50hz base for this core.

Non-standard pixel clocks are always out of standard and may not be supported by your display. This is true not only for higher clocks but also for lower clocks.

As for pixel clock itself, i've tried new scaler with ~180MHz - and it works well. So, it's up to your display what clock can be used.

ghogan42
Atari freak
Atari freak
Posts: 63
Joined: Wed Oct 17, 2018 7:27 pm

Re: Testing: Support for more HDMI resolutions and other changes.

Postby ghogan42 » Sun Dec 16, 2018 12:12 am

I learned the other day that mister.ini supports subsections so for cores that you plan to use at 50Hz you could do something like this:

Code: Select all

[minimig]
video_mode=9      ;or some other 50Hz mode line
vsync_adjust=1


At least my TV won't work with a 60Hz mode set and vsync_adjust=1 for a 50Hz system

BlockABoots
Obsessive compulsive Atari behavior
Obsessive compulsive Atari behavior
Posts: 104
Joined: Sat Oct 20, 2018 3:20 pm

Re: Testing: Support for more HDMI resolutions and other changes.

Postby BlockABoots » Tue Dec 25, 2018 4:28 pm

I have a Samsung NU8000 TV and when i use the 'vsync_adjust' setting set to '1' in the MiSTer.ini file i notice i get screen tearing towards the top of the screen now and again. Is there a way to fix this tearing or will i juts have to set the 'vsync_adjust' setting to '0'


Return to “MiSTer”

Who is online

Users browsing this forum: Locutus73, overdriver and 6 guests