Good news regarding tearing and low EmulationStation performance on Pi 4

ecto

@bluestang That did the trick! My retroarch was set to alsaand after changing it to alsathread the crackling went away after enabling KMS. Now everything works as expected! Thanks so much!

Now there is still the error messages in the syslog left (but those don't seem to have any negative effect?!
Also, whenever I start a game I get the message lvl0: VolumeControl::init() - Failed to find mixer elements. But that, too, doesn't have any negative effect.

Anyways thanks for helping me out!

bluestang

@ecto said in Good news regarding tearing and low EmulationStation performance on Pi 4:

@bluestang That did the trick! My retroarch was set to alsaand after changing it to alsathread the crackling went away after enabling KMS. Now everything works as expected! Thanks so much!

Now there is still the error messages in the syslog left (but those don't seem to have any negative effect?!
Also, whenever I start a game I get the message lvl0: VolumeControl::init() - Failed to find mixer elements. But that, too, doesn't have any negative effect.

Anyways thanks for helping me out!

You need to set the volume controls in EmulationStation to Audio Card -> Default and Audio Device -> Master.

ecto

@bluestang Thanks again! All problems resolved. All emus and ports working!

A little info for anyone playing Hexen 2: As the Hexen 2 port uses SDL 1, there are some fullscreen issues. I resolved that by launching hexen2 with XINIT: in the launch script. ~~It works ok, but there are some small sound issues.~~

EDIT
I found a Hexen II port that supports SDL2, so no more problems anymore!

Another EDIT
lr-vecx doesn't seem so like kms?! I can't get it to work right with either hard- nor software rendering. With hardware rendering, there is no graphics at all, and with software rendering the graphics are very choppy.

ecto

@bluestang A little update: I could not get rid of the sound (driver?) problems. I always found hundreds of ALSA lib pcm.c:8424:(snd_pcm_recover) underrun occurred errors in the runcommnd.log.
So I reverted back todtoverlay=vc4-kms-v3d,noaudioand dtparam=audio=on.

EDIT
looked up the exact error mesage

bluestang

@ecto said in Good news regarding tearing and low EmulationStation performance on Pi 4:

@bluestang A little update: I could not get rid of the sound (driver?) problems. I always found hundreds of ALSA lib pcm.c:8424:(snd_pcm_recover) underrun occurred errors in the runcommnd.log.
So I reverted back todtoverlay=vc4-kms-v3d,noaudioand dtparam=audio=on.

EDIT
looked up the exact error mesage

what emulator is causing this?

bluestang

@brunnis @George-Spiggott @dankcushions

There have been some clock improvements since 5.10.17 kernel's release...

I am running the latest 5.10.33 kernel through sudo rpi-update and I have my display set to 1080p @ 120 Hz (hdmi_group=1 and hdmi_mode=63) on the KMS driver and I am getting a constant 120 FPS in EmulationStation. More graphic intensive themes (i.e. Cosmic Rise) will result in 60 FPS but I do not see the dreaded dip to 30 FPS whatsoever.

I no longer have to set gpu_freq_min=500 either. I do have overclocked settings, but the governor is set to balanced and the clock freq is throttling down as reported by bcmstat.sh.

If your feeling adventurous give it a go and I'd be interested in your results.

Darksavior

Got 1440p working btw. No more uneven scanlines

hdmi_enable_4kp60=1
hdmi_group=2
hdmi_mode=87
hdmi_cvt=2560 1440 60 3

saccublenda

@philcsf said in Good news regarding tearing and low EmulationStation performance on Pi 4:

@setiawan Not tried composite, but I've encountered similar issues where the full KMS driver isn't respecting some of the config.txt video options.

Right now, I'm having to choose between:

Tearing issues, but supporting deep blacks via FKMS (hdmi_pixel_encoding=2)

Fixed tearing, but limited-range blacks via KMS ('hdmi_pixel_encoding' is ignored, so all blacks are slightly grey, which doesn't look great on an OLED)

I've noticed too that the hdmi_pixel_encoding is ignored with KMS and kernel 5.10.17-v7l+. Is there a workaround for this?

GreenHawk84

Extremely stoked for what could become of Retropie with new video drivers.

Also still concerned about how all our video snaps are going to be handled with KMS. I spent sooo much time on video snaps and making sure all my games have videos.

yamanobe

I'm sorry, can someone please tell me where to change the final settings?
My retropie has tearing all the time, and when I add "dtoverlay = vc4-kms-v3d-pi4, noaudio" to config.xml, I get splash screen and screen saver hiccups.