@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.

Yes, the problem with lr-mame2000 is that is not compatible with all games. :( In any case I will try to configure the gpicase controller searching in the config files for mame4all

I ended up just going back to the 3.5mm jack for audio in my cabinet. Based on the linked article, I just made sure I had the following settings in my config.txt: disable_audio_dither=1 audio_pwm_mode=2 For some reason my pwm_mode was set to 0 in my config and changing that to 2 resolved all my issues with the 3.5mm jack. Unfortunately, I was never able to get the crackle / hiss / static noise issue resolved when sending audio out HDMI to my HDMI to VGA adapter.

@griffon I hear you. Others have reported similar or related issues, and I have a similar problem on my TV as well, whereby sometimes the audio won't play until I change channels and then come back to the HDMI input on my Toshiba LCD TV. Clumsy HDMI handshake implementations is my best guess.

@bytethis right, and I changed the source of course to see the video. But it didn't work until I changed the pi from the HDMI2 on the back of my TV to the HDMI1. Boom, plenty of sound. Very happy! Thanks again, Paul

Additionally, is your HDMI routing directly to your TV or is it passing through a soundbar or AV receiver?

@Floob @NinjaX567 after one of the new updates i no longer get audio in dreamcast either. Its only in dreamcast. I havent tried composite audio to see if it works on it.

I had this problem last weekend after updating everything to the last version. It seems in some emulators de audio driver was changed to alsathread. I changed it back to sdl2 and the audio was back on the emulators. I did have sound in Emulationstation but aftering entering an emulator it was gone. Access retroarch configuratie with select+x and check the drivers in settings. Hope it helps.

@Charononus Glad I could help.

@gotwood3001 If you exit emulationstation with F4, you will be taken to the command prompt. From there you can edit files with the nano text editor. There is a much easier way though to edit /boot/config.txt and that is to use winscp or putty to access it via the network. Read more. Video tweaks here.

Actually I didn't do anything really except on my PC went to look at the network, retropie showed up and without extra software for IP addresses etc, it's let me copy/paste to the rom folders and delete stuff I don't want. We expecting a bunch of setup but, nope, showed on my network and allowed full access.

@exon said: i thought hdmi=group need to be changed to 2 for monitors. It depends on the resolution you want to output. hdmi_group=1 has "TV" resolutions and refresh rates, and also sends the audio out the HDMI hdmi_group=2 has "monitor" resolutions and refresh rates, but does not send the audio out the HDMI If using a resolution in group 2, or if using a HDMI-to-VGA adapter which usually detects as a "monitor" in group 2, then you can force HDMI audio out with hdmi_drive=2 Most TVs support common monitor resolutions as well (1024x768, 800x600, etc) and most monitors these days support at least the common TV resolutions (1080p, 720p, etc) so the only practical difference between "1080p 60Hz" and "1920x1080 60Hz" is what happens with the audio. There's a full list of all supported resolutions and refresh rates a little way down on this page: http://elinux.org/RPiconfig#Video

Thanks for the reply suprjami. Unfortunately I couldn't get it to work looking at those two links. My knowledge of linux just isn't good enough. If only there was a way to use a conditional statement within asound.conf that checks to see if the USB headset is plugged in before changing the default output to it.