For now my conclusion is this: Progressive scan with RP4b still works. You just have to either set it in config.txt as the appropriate sdtv_mode (16 NTSC/18 PAL), but then Emulationstation will also be in 240, which looks terrible, or use tvservice to enforce it on a per rom/platform basis after retroarch starts to switch back and forth. You can use my watcher python script and run it on startup in the background and then make an appropriate runcommand-onstart script or make your own solution. Script: https://retropie.org.uk/forum/post/220137 pi@retropie:~ $ tail -2 /etc/rc.local su pi -c 'python3 -u /opt/retropie/configs/all/vmodes_watcher.py &> /var/log/vmodes_watcher.log' & exit 0 # taken from https://github.com/Sakitoshi/retropie-crt-tvout/tree/master/to_configs pi@retropie:~ $ cat /opt/retropie/configs/all/runcommand-onstart.sh if [ -f "/opt/retropie/configs/$1/480i.txt" ]; then interlaced=$(tr -d "\r" < "/opt/retropie/configs/$1/480i.txt" | sed -e 's/[/\\[/'); fi > /dev/null if [ -f "/opt/retropie/configs/ports/$1/480i.txt" ]; then interlaced=$(tr -d "\r" < "/opt/retropie/configs/ports/$1/480i.txt" | sed -e 's/[/\\[/'); fi > /dev/null if [ ! -s "/opt/retropie/configs/$1/480i.txt" ] && [ ! -s "/opt/retropie/configs/ports/$1/480i.txt" ] || [ -z "$interlaced" ]; then interlaced="empty"; fi > /dev/null if [ -f "/opt/retropie/configs/$1/240p.txt" ]; then progresive=$(tr -d "\r" < "/opt/retropie/configs/$1/240p.txt" | sed -e 's/[/\\[/'); fi > /dev/null if [ -f "/opt/retropie/configs/ports/$1/240p.txt" ]; then progresive=$(tr -d "\r" < "/opt/retropie/configs/ports/$1/240p.txt" | sed -e 's/[/\\[/'); fi > /dev/null if [ ! -s "/opt/retropie/configs/$1/240p.txt" ] && [ ! -s "/opt/retropie/configs/ports/$1/240p.txt" ] || [ -z "$progresive" ]; then progresive="empty"; fi > /dev/null if tvservice -s | grep NTSC && { ! echo "$3" | grep -wi "$interlaced" || echo "$interlaced" | grep empty; } && ! echo "$interlaced" | grep -xi "all" && { echo "$3" | grep -wi "$progresive" || echo "$progresive" | grep empty; }; then echo 'NTSC 4:3 P' > /opt/retropie/configs/all/desired_mode/value; else echo 'NTSC 4:3 ' > /opt/retropie/configs/all/desired_mode/value; fi echo "runcommand-onstart $1 $2 $3" pi@retropie:~ $ cat /opt/retropie/configs/all/runcommand-onend.sh if tvservice -s | grep NTSC; then tvservice -c "NTSC 4:3"; fbset -depth 8; fbset -depth 32; fi > /dev/null 240p is default, override per platform/ROM in 480i.txt files pi@retropie:~ $ cat /opt/retropie/configs/mame-libretro/480i.txt all As stated in this thread: https://github.com/raspberrypi/firmware/issues/683#issuecomment-283179792 what was done in the firmware to make these new modes work is A. Setting the progressive scan bit in the VEC (Composite TV out) register set: https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/vc4/vc4_vec.c#L104 B. Remove the interlace flag for the mode: https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/vc4/vc4_vec.c#L256 tvservice does essentially the same thing and sets the new modes: https://github.com/raspberrypi/userland/blob/2448644657e5fbfd82299416d218396ee1115ece/interface/vmcs_host/vc_sdtv.h#L60 https://github.com/raspberrypi/userland/blob/master/host_applications/linux/apps/tvservice/tvservice.c#L703 https://github.com/raspberrypi/userland/blob/master/interface/vmcs_host/vc_vchi_tvservice.c#L1213 https://github.com/raspberrypi/userland/blob/master/interface/vmcs_host/vc_vchi_tvservice.c#L698 Since there is a hardware flag that needs to be set, it won't be possible to resolve this with xrandr modesetting alone as was suggested. Ideally RetroPie in some form could enforce this natively in a similar fashion by taking the SDTV_MODE as a parameter and enforcing it through VCHI like tvservice does, alongside the modsetting being done in the modified SDL library.

The crt-mattias and crt-geom are way too demanding for a Raspberry Pi, they're not installed by default on the Pi - only on a PC installation.

Try adding a fbset -g 1920 240 1920 240 32 after you switch the video mode via tvservice, this will tell framebuffer console to change it's size to the new video mode. So vcgencmd hdmi_timings 1920 1 23 25 39 240 1 4 3 15 0 0 0 60 0 6400000 1 tvservice -e "DMT 87" fbset -g 1920 240 1920 240 32 fbset -depth 8 && fbset -depth 32

I think the only way is to have something like: CEA for emulationstation and DMT for retroarch. I can't figure out any other way :/

@chipsnblip This is more than anyone could ask for. On behalf of the retro community and myself. Thank you!

@TANKARD @mitu Custom configs for CRT using the built-in composite out You can also tweak the runahead settings for 8bit/16bit consoles to further improve the input lag and use wired controllers.

@ohmycommodore From what I've tried out, systems where the resolution is the same as ES (probably 320x240) are fine, it's only when the resolution needs to switch that the problem occurs. You can definitely try it out and just send that command to clear out the frame buffer if you get stuck at any point. The one or two N64 games I tried worked really well, as well as psx games with enhanced resolution and the older systems with one or two frames of runahead. I'd be interested in seeing how RT works with Pi4 and Lakka though. I haven't used it much as I have all my PSX games in chd and didn't really want to change them all over.

@jamesfarnhamlong said in Retrotink U - Higher res ES and PSX games: The 450x270 looks best, but I was wondering if it was possible to run one @ 720x578 to improve the picture a little. I know the TV supports this as I have an old Apple TV that uses this revolution. How do I write the hdmi_timing to make this work? Is there a calculator or something I could use? Try this - http://eightvirtues.com/lakka/hat/RPi HDMI Timings Calculator and Core Docs.ods (courtesy of https://www.youtube.com/channel/UCtF_2HGXXPlUi1J0Euw1Qrw). Is it possible to adapt this to run at 2x resolution so I can use the enhanced graphics in psi-rearmed. Is there a way to have this only affect psx game launching? Or would it then throw out all the other systems? Is there much point? Maybe if you use the calculator linked above you can derive the correct HDMI timings to use. As for the effect on the other systems, you'll have to ask the author of those configs.

Have just published this - https://retropie.org.uk/2019/07/composite-out-broken-on-retropie-4-5/

it depends on the shaders you are using now. for example, assuming you use 240p with your new CRT, a scanline shader would be pointless because a) 240p already shows scanlines on a CRT and b) 240p is not enough vertical resolution to allow fake scanlines to be rendered. shaders that adjust the colour or fidelity of the image may or may not be useful or provide the desired effect, depending on what they are doing and how you are connected to your CRT.

@mitu Saw some feedback on it in my searches..Thanks for confirming...

@mcorcoran I wonder if it has something to do with GFE version because you're having to use "-unsupported". Do you have the newest version of the GeForce Experience installed on your Windows PC? Also, you might have just typed it wrong in the post but "-localaudio" is just one word without spaces. I remember one time I was having trouble with resolutions and I discovered I was spelling "width" wrong. Another thing you can try is putting the "-width 720 -height 480" before the "-unsupported" in that command. If you could get it working without "-unsupported" by updating GFE, that would probably be better. Last, you might also experiment with the refresh rates by adding either "-fps 60" or "-fps 30". What refresh rate is your Windows PC when you manually set it to 720x480? That would be the refresh rate you should try first.

I went with this one , had free shipping. Will post when tried out.

Yes, it might be possible. You'll need to modify the autostart script in /opt/retropie/configs/all/autostart.sh and start either Emulationstation or the desktop - depending on your current TV connection. There's a way to detect which output is connected (see this topic), so you can use something like this: if (/usr/bin/tvservice -s | /bin/egrep 'HDMI|DVI') ; then # Start the desktop xinit else # Start Emulationstation emulationstation fi

Adding this line to Mednafen VB.cfg: video_refresh_rate = “50.0” Fixes the timing issue, hope this post helps anyone with the same issue. Runs great now! ( btw, definitely lower the audio_out_rate to around 33200 or something like that, and sample fidelity to lower and add some audio time skew, no framedrops or sound skips now that I could notice even when playing in 3d )

@Capeman Hi, please share your settings to make the theme look like yours. Thank you very much

@M3th0D I was getting 15khz out of HDMI like you but i went into a hdmi to component converter, using retropie.. I came a cross this post when i was trying to work things out, and seen the runcommand , I used it but in a different way,,I got emulation station running in 480i, and retroarch running in 1600x240.. and it switches back to 480i when exiting games. https://retropie.org.uk/forum/topic/22467/hdmi-to-component-crt-help-runcommand/10 just wanted to pass on the info.