Resolution 1920x1200 support

[Zarkov]

Hi, can support for 1920x1200 be added for monitors that are 16:10?

[mapf]

You can try

Code: Select all

video_mode=1920,128,208,336,1200,1,3,38,193160

(generated using https://arachnoid.com/modelines/ and https://morf77.pythonanywhere.com/

[ByteMavericks]

That’s what I’ve got on my dell monitor, works well

[lamarax]

You may also try:

Code: Select all

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

Works perfectly with my adaptive sync monitor, allowing me to use vsync_adjust=2 for every core (including WonderSwan @75.4 Hz).

[FoxbatStargazer]

This is a common enough monitor resolution that an official video mode would be welcome.

[Zarkov]

Awesome, thanks for the info.

I also just discovered this section on GitHub as well
https://github.com/glopgar/MISTer_video_modes

[Zarkov]

I added the line to my ini and after reboot, I get no video on the monitor. I putty back in and replace the ini file with a backup to get it working again.

I have a dell u2410 hooked up via hdmi to the mister.

Maybe I’m not entering it correctly? Or my monitor can’t do 1920x1200 over hdmi?

[FoxbatStargazer]

I would try a more conservative CVT timing from here

video_mode=1920,136,200,336,1200,3,6,36,193250

[Zarkov]

I would try a more conservative CVT timing from here

video_mode=1920,136,200,336,1200,3,6,36,193250

Tried this line and its the same. My monitor wont display a picture.

I checked out that site and made some notes for modes to test. I also learned how to get the Fpix in KHz value by taking the Pixel clock and Multiply by 1000.

Thanks for your time/help.

[Zarkov]

You may also try:

Code: Select all

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

Works perfectly with my adaptive sync monitor, allowing me to use vsync_adjust=2 for every core (including WonderSwan @75.4 Hz).

Hi, I used this line and it is now working. Sorry I must have not tried this one prior. Thanks.

So just to summarize:
for Dell U2410 via HDMI:
CVT RB 1920 48 32 80 1200 3 6 26 154128 works
1920 128 208 336 1200 1 3 38 193160 did not work
CVT 1920 136 200 336 1200 3 6 36 193250 did not work
CVT RBv2 1920 8 32 40 1200 21 8 6 148200 did not work

[Jeruro]

You may also try:

Code: Select all

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

Works perfectly with my adaptive sync monitor, allowing me to use vsync_adjust=2 for every core (including WonderSwan @75.4 Hz).

Works perfect with my Apple Led Cinema Display. Thanks for posting!

[lamarax]

Hi, I used this line and it is now working. Sorry I must have not tried this one prior. Thanks.

Yeah, let's just say that these auto-generated theoretical modelines, come up with overly "enthusiastic" values for real world hardware

I believe after a linux update sometime back in summer (?), you can now [read/parse/get-EDID] from inside MiSTer's console, so it's easier to tailor modelines to each particular panel's capabilities.

That said, I concur that there should be a default preset in the .ini for 1920x1200.

[ash2fpga]

Yeah, let's just say that these auto-generated theoretical modelines, come up with overly "enthusiastic" values for real world hardware

I believe after a linux update sometime back in summer (?), you can now [read/parse/get-EDID] from inside MiSTer's console, so it's easier to tailor modelines to each particular panel's capabilities.

That said, I concur that there should be a default preset in the .ini for 1920x1200.

I have wondered about the various modeline calculators found online. Are these actually based on what hardware can really support, or someone simply came up with a set of equations that happen to work (some of the time?) and put the calculators online for anyone to use (for better or for worse)? The pixel clock, in particular, seems like the can vary quite a bit depending on where you find a modeline online.

[FoxbatStargazer]

The main thing that varies is the blanking settings, that's also what most of the numbers are. After you write a line of your video information, there needs to be a sync signal, and a buffer before and after to separate the sync from the image. Displays can vary greatly in what range of blanking they can tolerate, especially when comparing CRT vs LCD. CRTs usually need more blanking time because they have to physically reposition the guns during the blanking interval to draw the next line.

[breiztiger]

sorry to tell but for those with a dell u2410 ...

can this monitor handle 75hz correctly for wonderswan and 57.2 from cave68k core ?

thanks for the answer