Help?

Ok, this is embarrassing.
It turned out that (for some reason) the volume was set to -60 db in the playback audio setting, and this (for some reason) affects also the Kodi UI sound volume. The playback audio settings are separated from the general settings > system > audio, but the playback audio can be modified pressing the keyboard keys + and -. This, coupled with the weird behavior of Kodi that (for some reason) does not play UI sounds when using a controller, but only when using a keyboard.
It turned out to be a rather silly problem, but I leave it here hoping this can help others facing the same behavior.

@natesroom So i figured it out, I needed to update the RetroPie Setup Script or whatever that name was in the screen first then run the install option packages.

In the Documentation that should be noted (unless it is and i just missed it)

@xsy77 said in Kodi 19?:

Do you when or if it will get the update to 19?

I don't know.

Is the only solution for me at the moment to use berry boot to have both retropie and Librelec/OSMC to get Kodi 19?

If that works, why not ? Is there anything you need from Kodi 19 and it's not in Kodi 18 ?

EmulationStation does not know (nor care) how the controller is connected, so there's nothing to configure there.

You can however pause the RA software during gameplay and resume it afterwards using the onstart/onend scripts for runcommand - see here.

@breadncup There is a new version of Kodi, but with my limited technical knowledge, basically, many of the older apps on it won't work on it.

@mitu
I can delete files from my PC, but they re-appear when i mount it again. So broken SD card.

Thanks for the help. I would never thought of that.

Set your default video resolution at 720x576i or 720x480i and switch to 240p when running a game, using the Runcommand onstart script - https://retropie.org.uk/docs/Runcommand/#runcommand-onstart-and-runcommand-onend-scripts.

@mitu over the repository

There is some configuration that can be done by modifying the ALSA configuration file ($HOME/.asoundrc), but looks complicated and there's no 'one-size-fits-all' solution (depends on the devices present on the system).

You could try installing PulseAudio and configure the module-combine for simultaneous output.

Hey it WORKED!

~/.config/openbox/autostart

gnome-terminal --full-screen --hide-menubar -- bash /home/pi/autostart.sh

and
~/autostart.sh (chmod +x)

#!/usr/bin/env bash kodi-standalone sleep 2 emulationstation

So on boot, Kodi launches. On first Kodi exit, the script will launch ES. From then on, ES does what it does when launching Kodi and returning to itself on exit.

Thanks for your help @mitu!

@cyber said in RPI4: Kodi version update, N64 stuttering, no rumble pack:

I have selected there now the first one (lr-mupen64plus-next).

I cannot find any config files "lr-mupen64plus*" - thats why I took now pictures of the settings which I can see with the retroarch core menu:
https://1drv.ms/u/s!AnFpCl7HpNVtg9s3sr_EwOEzchjJRw
https://1drv.ms/u/s!AnFpCl7HpNVtg9s2ejenqrrrORMhew
https://1drv.ms/u/s!AnFpCl7HpNVtg9s10tfvMXtuttTlPA
https://1drv.ms/u/s!AnFpCl7HpNVtg9s0Up0aFFn_PBBQ7A

i don't think there's much point testing lr-mupen64plus-next as it's going to be slower than standalone, but there's a few settings you can change:

native resolution factor = 1x Overscan = Disabled

be mindful to change only these, and exactly these. some others are named similarly.

graphical issues: compared with mupen64plus-gliden64-highres I have e.g. in the menus black lines: https://1drv.ms/u/s!AnFpCl7HpNVtg9s4IPgzfQ90i32wrQ

comparing what to what? please be specific. if it's to lr-mupen64plus-next, again this is not optimal. use mupen64plus-gliden64

Glad you got it fixed. You can try now to apply the overclock back, though I'd recommend you give it a try without it and see how the system performs. The Pi4 should be powerful enough for most systems.

They are sorted by type, then alphabetically.

So emulators, libretrocores, ports, supplementary.

Post the Kodi log file from $HOME/.kodi/temp/kodi.log to pastebin.com, maybe we can spot the error.
Also, please fill in the info asked in https://retropie.org.uk/forum/topic/3/read-this-first.

@ramco That's weird, I never saw a TV/Remote who shuts down Kodi or the Raspberry, the power button is never assigned to o CEC button, it should only turn off the TV.
Probably it is your TV brand, never heard about that one. Each TV brand as it's own CEC implementation and name, yours might be one of the weakest.
You said you are running Kodi 18.2, Kodi is currently in version 18.8, update it and check, although I doubt it will fix your problem.

@Marco-G gpu_mem=320 is pretty much essential if you want to play high bitrate 4k hevc. You don't need as much if you don't play this kind of media.
About hdmi_ignore_cec_init=1, what it does is to not switch (the TV) to the Raspberry Pi/Retropie source when it is started or rebooted. It has no effect in anything else.

@gorrie06 full log here :

https://pastebin.com/ZeVUAU31