Is there no interest in having retropie run as a service on top of a full desktop environment?

Not on the Raspberry Pi.
RetroPie (ES + emulators) works fine on a PC platform from the desktop, but the audio configuration is handled by the system/desktop environment and there's not much that RetroPie configures at this point, it just used the default audio device that's register in the system (i.e. in PipeWire/PulseAudio).

EDIT: as explained before, you need to find the right Audio Card setting which works for you. Try using PCM/Master instead of HDMI, it should work.

@dvojkaa for others there is this topic
https://retropie.org.uk/forum/topic/35350/no-audio-on-raspberry-pi-5/8

and it seems to work for him so i will try the same a write here again what happes

@abj Thanks. This fixed the audio for me.
On my unsupported pi5 setup, switching to the Pegasus frontend killed the audio, and switching back to ES was not fixing it.

OK, I finally got it fixed. and I really should have looked at this first, so I'm sorry for putting everyone who looked at this on a wild goose chase. But I've been putting off working on this because I've had other projects and while I can rebuild, I didn't want to. But the overscan didn't work, it would not pull it to the left like I wanted, I made sure the TV was on game mode and not stretching or adding any post processing. I had a spare TV and wanted to rule out the TV, and behold I seen this
IMG_20231028_182219.jpg
I commented out the hdmi_drive=2 and it all works.
I'm not even going to pretend I know what was going on, but my guess the damaged connector was pushing sound through what was left working of the cable and had to push the video to the side to make room for that. I dunno, but new cord, and verified it's working. I'm going to buy some backup HDMI cables just in case and really try to come up with a better solution to where I sit the Retropie

The Audio settings in the RetroPie system (or audiosettings in RetroPie-Setup's configuration/tools) is doing the same thing as the raspi-config options.

Not sure which version of RetroPie are you using (version 4.4 is too old to support the PI4), but out of the box I think HDMI sound should work using the 4.7.1 image.

Make sure that in the Audio settings in the RetroPie system you choose HDMI as output, then in ES the settings should be:
AUDIO CARD: Default
AUDIO DEVICE: HDMI

For OMX audio output, just use ALSA and it should work.

I found an easy way to do this.

I just needed something like a Turtle Beach Ear Force DSS 7.1 Dolby Surround Sound Processor.

One can find that on Ebay currently for $10.

https://www.ebay.com/itm/272275549904

I successfully replaced the line

dtoverlay=vc4-kms-v3d

in my config.txt file with

dtoverlay=vc4-fkms-v3d

and now everything works perfectly! Thanks for the help @mitu

@technicaljunky It's not a problem if PulseAudio is present - the only issue for you seems to be EmulationStation's audio settings, which should be solvable with the correct configuration.

@mitu Thank you! Very simple solution, and it works perfectly! I didn't realize you could add scripts in there.

I still get the fun "failed to find mixer element" when I run the script, run a rom, or shutdown the system, but I'm not too worried about that. At least the audio works in both configurations now.

@gazbusola

My issue clearly had to do with pulseaudio, which I have no use for (at least for now!) on my current Raspberry Setup.

Your issue might have to do with the different HDMI modes. Have you looked into the config file for all the HDMI settings?

@Paxi said in RetroPie on Ubuntu Mate 20.4.01 HDMI sound issue:

there is only a 32bit version available.

RetroPie has only experimental support for 64 bit on the Pi, using the Raspberry OS 64 bit beta version.

Isn't there anything more I could try, specifically in RetroArch/Pie config?

You can try to disable PulseAudio and make sure RetroArch uses ALSA.

hdmi_safe=1 is equivalent to:

hdmi_force_hotplug=1 hdmi_ignore_edid=0xa5000080 config_hdmi_boost=4 hdmi_group=2 hdmi_mode=4 disable_overscan=0 overscan_left=24 overscan_right=24 overscan_top=24 overscan_bottom=24

You can add

hdmi_force_hotplug=1 hdmi_ignore_edid=0xa5000080 config_hdmi_boost=4 hdmi_group=2 hdmi_mode=4 disable_overscan=1

instead of hdmi_safe=1.

I wonder if any "good brand" TV of that time has also this problem ?

Telefunken used to be good, they sold the name, its not really telefunken anymore.
DGM is a total unknown brand.

I wonder if any LG TV has audio problems.

I couldn't get speaker-test to work, or aplay. alsamixer had volume.

I ended up just re-imaging the SD card with a fresh copy of RetroPie. This fixed my issue. All ROMs I've played have had appropriate audio.

@mitu thank you. That was the issue. I knew it was something easy. Thanks for the support!

@ahndrooan You can edit the topic title - there's no 'solved' checkbox :).

@TheBossT said in Retropie 4.4 HDMI Problem: Garbled Sound When Playing ANY Console/Emulator:

Also if anyone can maybe give some alternatives to bluetooth audio as the lag ain't great, that will be greatly appreticated!

There aren't many solutions out there and it seems this solution not only breaks other audio outputs but also is unusable due to the lag. I'm almost certain the Pi dosen't have enough horsepower to emulate games and stream bluetooth audio, as per the tutorial above I have completely removed it and I recommend that you should too. Let me know how you get on and if you find an alternative that doesn't stutter.

Thanks for answering, check that other users had the same problem, so check my settings thoroughly:
thanks to this help guide:
https://retropie.org.uk/docs/Sound-Issues/
This step solved the problem for me:

USING THE BUILT-IN HDMI AUDIO
If you have a standard RPi and want to send audio over the HDMI connector then it should just work. In some instances though, you will need to manually modify the raspberry pi boot config file (sudo nano/boot/config.txt) and ADD the following lines to those already there:

# forces HDMI mode hdmi_drive=2 # Setting hdmi_force_hotplug to 1 pretends that the HDMI hotplug signal is asserted, so it appears that a HDMI display is attached. In other words, HDMI output mode will be used, even if no HDMI monitor is detected. hdmi_force_hotplug=1 # Pretends all audio formats are supported by display, allowing passthrough of DTS/AC even when not reported as supported. # May not be needed for all HDMI devices hdmi_force_edid_audio=1

Once you've made the change, save the file, restart your Raspberry Pi, and move onto Step 2.