Direct video CRT Zoomed image in menu core

[DGanger]

I have a pretty minimal setup. DE10-nano, DAC, self-made VGA to SCART cable and small CRT (Sony KV-14CT1K). My config is default with only direct_video and composite_sync set to 1. My image in menu core is slightly zoomed in. For example, when update_all script works first letters of log aren't visible. But everything is ok, when I use Genesis core. What is the issue?

[akeley]

I have a similar setup and have never seen anything like that. If your .ini is ok, then perhaps it's something with the cable? Which schematic have you used?

[thorr]

Mine was the same way until I turned on the scaler for the menu. The issue is that is the way the menu timings are set up in direct video. Try these and it should fit. I just got a new TV and will be working on a new video mode soon, but this works with slight spaces on the sides.

[Menu]
direct_video=0
vga_scaler=1
vsync_adjust=1
vscale_mode=1
video_mode=1280,120,140,202,240,2,0,22,27565

[FoxbatStargazer]

I'm surprised you see anything of any script at all using direct video? I thought framebuffer (i.e. scaler) was required.

[akeley]

Ah, I did misread it, I thought OP means OSD. Yeah, mine is the same, the first letter is missing - but then it's something so inconsequential, and I see it so rarely, that I've never thought about fixing it.

[thorr]

I'm surprised you see anything of any script at all using direct video? I thought framebuffer (i.e. scaler) was required.

No, it works fine, but the edges are cut off.

[DGanger]

Mine was the same way until I turned on the scaler for the menu. The issue is that is the way the menu timings are set up in direct video. Try these and it should fit. I just got a new TV and will be working on a new video mode soon, but this works with slight spaces on the sides.

[Menu]
direct_video=0
vga_scaler=1
vsync_adjust=1
vscale_mode=1
video_mode=1280,120,140,202,240,2,0,22,27565

I added setting to mister.ini but unfortunately it doesn't help. Image just start to flicker, then stop for a second, and flicker again.

I want to illustrate my problem.

Menu core:

menu_core1.jpg (408.83 KiB) Viewed 2862 times

menu_core2.jpg (478.39 KiB) Viewed 2862 times

Genesis core:

genesis_core.jpg (1.27 MiB) Viewed 2862 times

[FoxbatStargazer]

Isn't that just overscan? One of the joys of Mister is that it has so many different systems following different analog standards, you tightly adjust it for one core and its off for many anothers... this is why most systems kept important info away from the overscan, but not the Mister terminal, which assumes an LCD monitor! Maybe there's some setting to alleviate but I don't know of it...

[lnielsen]

I have the same issue when running the updater all script. I have a basic MiSTer connected to an LCD TV via HDMI.

[FoxbatStargazer]

I have the same issue when running the updater all script. I have a basic MiSTer connected to an LCD TV via HDMI.

That should be fixable on most LCD displays, the display itself is doing a slight zoom to cover up overscan in old video content. Unfortunately how you fix it can depend greatly on the TV, but you might look through the different wide/zoom settings on your TV, or sometimes its under "screen" or "display area".

[ash2fpga]

On some flat panels perhaps either there is a very minimal physical mask covering up the very edge of the screen, or the very edge pixels do not have physical screen elements they would map to ("sorry, you have a 1916x1076 screen, not a 1920x1080 screen")?

https://www.avsforum.com/threads/offici ... t-20461784
"basically I kind of have about 1916x1076 in a 1920x1080 screen."

Looks like 1916x1076 is a "thing" in videos, too:
https://forum.doom9.org/showthread.php? ... ost1720225