Amiberry 3.3 / RPi 4 slow

[gordonfreemanjr]

@dankcushions Nope. Let me go through the events quickly:

• Amiberry is slow. I find the advice on the resolution and framerate. Apparently 4K is stuck at 30 FPS. I use raspi-config to switch to 1080p
• I reboot, the ES is gone and won't boot. I edit the config.txt, try to comment the HDMI values back. I save, I reboot. The ES is still gone. I check whether my changes were saved: yes, they were
• I give up and wipe the SD card to start over
• Once the new RetroPie is installed and working, I perform an experiment: I do the same thing, which is changing the resolution with raspi-config on a freshly installed RetroPie. Same situation: the ES is gone and won't boot. I wipe the SD card again
• With another clean install, I'm back to tackle the issue again. As for some reason this blows my ES sky high, this time I'm not touching raspi-config. I edit the config.txt with sudo nano, set the HDMI values to 1x16, I reboot.
• The ES works and boot correctly. I run raspi-config to check the resolution: apparently it's 1080p. At this point I write in the other topic that I made it.
• I try Amiberry: no changes, laggy and choppy
• I learn about the /opt/vc/bin/tvservice -s command. The output tells me that I'm NOT in 1080p at all, but still stuck in 4K.
• ...and here we are.

[dankcushions]

@gordonfreemanjr thanks for the summary. sticking to one thread would help! and have you tried

hdmi_group=2
hdmi_mode=82

in config.txt?

[gordonfreemanjr]

@dankcushions You're right. The reason is I was convinced we're talking two separate issues, that's why two topics. Sorry about that!

I haven't, let me try it real quick.

[gordonfreemanjr]

@dankcushions Ok, tried it. No changes. Also, according to /opt/vc/bin/tvservice -s I'm still in 4K even with 2x82 settings forced with config.txt

[mitu]

What resolutions does your TV support ? If you use the Runcommand launch menu to change the resolution, what are your choices ?

[gordonfreemanjr]

@mitu Tons... it’s over 50 of them.

Screenshots:
https://ibb.co/2McjX00
https://ibb.co/RBtpYg9
https://ibb.co/MpqWmx7
https://ibb.co/ZGx1V0B

I tried setting 87-15 and 87-17 as global Amiberry modes, no change.

For the record, I’m back to the 1x16 setting in the config.txt. Not that it changes anything.

[mitu]

@gordonfreemanjr said in Amiberry 3.3 / RPi 4 slow:

For the record, I’m back to the 1x16 setting in the config.txt. Not that it changes anything.

Is looks like your TV is upscaling everything to 4k ? Try setting
just

hdmi_safe=1

into config.txt and see if it boots to a different resolution. Does the TV have a 'Game Mode' you can turn on ?

[gordonfreemanjr]

@mitu Yes, the TV has a Game Mode. If hdmi_safe=1, should I also uncomment the group/mode settings?

[mitu]

@gordonfreemanjr You can comment out the custom video mode and try with just hdmi_safe.

[gordonfreemanjr]

@mitu Um, no. With this setting on and the custom modes commented out, the ES won’t boot.

Also, the terminal window looks like this:
https://ibb.co/t2ztQTX

[mitu]

Ok, so the hdmi_safe works, but for some reason ES doesn't start.
Can you run emulationstation --debug and post the \\retropie\configs\all\emulationstation\es_log.txt to pastebin.com ?

[gordonfreemanjr]

@mitu Sure. Here:

https://pastebin.com/Pu26SKm9

[mitu]

@gordonfreemanjr The log shows no error related to the video and a proper showdown.
I just tried the same thing on a Pi4 and EmulationStation starts ok - albeit in 640x480 @ 60hz, forced by hdmi_safe. Does your TV shows the change of resolution when starting ?

[gordonfreemanjr]

@mitu I’m not sure about showing the change of resolution, but when I power the Pi up with the new settings, apart from the black screen and the ES not booting, when I press the HOME button on the Smart TV’s remote, the following info is displayed:

HDMI 1
Game Mode
640x480 / 60p
SD
the date and the time

[mitu]

@gordonfreemanjr said in Amiberry 3.3 / RPi 4 slow:

Game Mode
640x480 / 60p

This seems right, similar to your screenshot. Why ES doesn't show up, that I cannot explain - didn't found this situation before.

[gordonfreemanjr]

@mitu Still, when the Pi is blackscreened at the start up, that is when the ES doesn’t show up, the F4 key works and brings the terminal up. As far as I’m concerned, this the expected behaviour when quitting the ES.

It’s almost like the ES was booting after all, just hiding behind the black screen for some reason.

[dankcushions]

@gordonfreemanjr i don't know why it would make a difference, but could you try with the default theme? and/or updating emulationstation to latest master (update from source)?

[gordonfreemanjr]

@dankcushions I like this suggestion. I’ll try that later today and get back to you. Thanks!

[gordonfreemanjr]

@dankcushions Both methods have failed. Same situation: black screen on startup, even with the preset theme and the ES script updated from source.

[mitu]

@gordonfreemanjr One last idea (filtering out 4k modes at the source) - add to config.txt:

[hdmi:0]
hdmi_max_pixel_freq=200000000
[hdmi:1]
hdmi_max_pixel_freq=200000000

Remove the hdmi_safe option and comment out the hdmi_group/hdmi_mode options (if still enabled).