@mitu thanks for the reply. I turned off my shader preset to see what would happen, and it does improve performance to "mostly" 60fps. The global shader I use is just "sharp-bilinear-2x-prescale" which afaik isn't supposed to be demanding at all, so I'm surprised performance tanks so badly with it on.

Unfortunately I've screwed up the video settings for all the snes cores by attempting to remove the global shader preset from bsnes, while keeping it in place for snes9x. Shaders don't work at all for snes anymore, and different resolutions in the runcommand menu aren't even working... I don't know why that happened.

Bsnes is causing me too much trouble, so i'm just gonna uninstall it once I restore my backup...

Have you tried lr-mame2000 ? Should be less demanding than Mame2003.

@luckyluca said in Pi400 slow stuttery dremcast redream emulationI:

Regarding overclocking, do you know what the default gpu clock is for the pi400/pi4?

I think the default gpu_freq is set to 500 (Pi4), I assume is the same for Pi 400.

@mitu Thank you, this worked.

@wmarcio Actually, the issue was caused by a similar thing! Instead, it was the usb that I had connected into the pi. All my freezing and stuttering has finally stopped. Thank you for the help!

you edit the config.txt file with some of these settings:

https://www.raspberrypi.org/documentation/configuration/config-txt/video.md

I think it is fixed. I reboot multiple times and only once it flicked black for about 1/2 a second.

I moved my splash screen to /opt/retropie/supplementary/splashscreen/

then I

edited asplashscreen.sh and removed the -b from around line 37 near OMX (that removed a black background that used to be needed to hide post text.

I had to use the command sudo chown on the directory to get write access

@pjft said in Bug (solved): OMXPlayer on Stretch-based builds stutters on composite:

Does running standalone omx player result in the same stuttering?

Absolutely! And yes, this issue remains unsolved.

@matchaman

Being on a modern TV myself, I keep it disabled at a system level just for the NES, as (A) it's really the only system that needs that level of response time and (B) it isn't likely to have performance affected. I've even considered just setting it to off at an individual game level for the few titles that need that level of accuracy.