Code: Select all
video_mode=2560,48,32,80,1440,3,5,33,241699
That's from Nvidia custom resolution, CVT reduced blank.
Moderators: Mug UK, Zorro 2, Greenious, spiny, Sorgelig, Moderator Team
Code: Select all
video_mode=2560,48,32,80,1440,3,5,33,241699
JamesF wrote:@profdCode: Select all
video_mode=2560,48,32,80,1440,3,5,33,241699
That's from Nvidia custom resolution, CVT reduced blank.
Grabulosaure wrote:the cores must be recompiled with .OHRES(4096) as a parameter to the scaler (without that, it shows a clipped image).
Sorgelig wrote:Currently there are no cores which can output native resolution higher than 1280x720. So there is no point to set output resolution to 2K or 4K.
It's enough to set 1/4 resolution of your TV, so for 2560x1440 TV it's enough to set 1280x720 and let the TV to do integer 2x scale. So no artifacts will be added by such scale (if you will set appropriate video type in TV settings).
The same for 4K 3840x2160 TV you can use 1920x1080 resolution with 2x integer scale by TV.
Grabulosaure wrote:Newsdee wrote:Implementing filters on an emulator to post-process dithering
Do you have any link ? I don't quite understand.
A design limitation is that horizontal and vertical interpolations are separate, it's two vectors, not a matrix.
Newsdee wrote:I dug a bit deeper and it's the gdapt and mdapt shaders found in Retroarch. Here is a writeup about them: https://forums.libretro.com/t/mdapt-gda ... -06-14/375
JamesF wrote:Are you sure vsync_adjust=2 is working now with all cores?
I think you need the special cores by Grabulosaure to activate the low latency mode, the official cores do not support low latency mode yet, afaik.
If I understood Grabulosaure correctly, the current implementation is triple buffered hence 1-3 frames of lag
paulbnl wrote:JamesF wrote:Are you sure vsync_adjust=2 is working now with all cores?
I think you need the special cores by Grabulosaure to activate the low latency mode, the official cores do not support low latency mode yet, afaik.
If I understood Grabulosaure correctly, the current implementation is triple buffered hence 1-3 frames of lag
At least NES and SNES have been updated with low latency scaler.
In MiSTer.ini it is said that vsync_adjust =2 uses a single buffer.
cacophony wrote:I don't think it's actually working yet with vsync_adjust =2 and the release cores based on my testing and conversations with Grabulosaure.
These were the instructions that I got from Grabulosaure on 12/26:
"I have posted on temlib.org/pub/mister/ascal a version of SNES which blinks LEDs when buttons are pressed. The low lag mode has issues with the default settings with 148.5MHz clock, if you need 1920x1080@60Hz, use instead something like "video_mode=1920,48,32,80,1080,123,6,26,154130" . Select NTSC, no triple buffer, no vsync_adjust."
I did confirm that it seemed to work with that special LED build after following those instructions.
paulbnl wrote:cacophony wrote:I don't think it's actually working yet with vsync_adjust =2 and the release cores based on my testing and conversations with Grabulosaure.
These were the instructions that I got from Grabulosaure on 12/26:
"I have posted on temlib.org/pub/mister/ascal a version of SNES which blinks LEDs when buttons are pressed. The low lag mode has issues with the default settings with 148.5MHz clock, if you need 1920x1080@60Hz, use instead something like "video_mode=1920,48,32,80,1080,123,6,26,154130" . Select NTSC, no triple buffer, no vsync_adjust."
I did confirm that it seemed to work with that special LED build after following those instructions.
I think what you are talking about is a separate low latency mode.
I have made photos with the HDMI vsync_adjust=2 output to a LCD monitor and a CRT connected to the VGA output and the latency varies between 0 and 1 frames max.
JamesF wrote:@cacophony
If you look at the changelog you'll see that most cores (including Genesis) have been updated with pll_hdmi_adj.vhd on Dec 31, so vsync_adjust=2 didn't do anything on the Genesis core back in Dec 26.
Also, as Grabulosaure said, the convergence (synchronization) time is slow on other cores besides Genesis, but he's working on it, hence the experimental label.
I've just discovered that the low-lag mode and HDMI_PLL_ADJ isn't correctly instantiated in Sorgelig builds (SNES,NES,Genesis, Minimig,ao486, ...). There is a missing signal (lltune) : vsync_adjust=2 doesn't work, it behaves just like vsync_adjust=1
For the low lag mode, there is frequency and phase adjustments.
Each time the input video mode is changed, that thing modifies timing to align the input and output video modes, generating a few wacky frames.
There are two options :
- Either the core tries to get signal aligned quickly, it lasts 2..3 seconds to align and a bit more time before the screen will eventually display an image (this is the current implementation).
- Or tuning is done very slowly (10...30 seconds) to allow the screen to [hopefully] never loose sync and keep displaying an image, with eventual tearing due to desynchronisation.
JamesF wrote:I'll quote Grabulosaure on Discord on Jan.22nd:
Users browsing this forum: No registered users and 10 guests