@mitu said in Why is Pulseaudio no longer an option in Settings > Audio > Output?:

Is there a way to get it back?

Modify the buld script and enable it if you wish.

I was able to update using the instructions you gave me (along with that other error I was having) and all seems to be working well now!

I have NO IDEA why lr-dolphin seems to be more stable using pulseaudio (any ideas?) but I feel I get emulator core crashes by far less often when using pulse than using any other sound driver.

@windg thanks it works !

@mitu

I've already done that, a number of times.

There's something more complicated going on here.

I attempted a completely fresh install to track my progress better step-by-step.

It's here: https://retropie.org.uk/forum/topic/34489/continued-sound-issues-some-kind-of-bug

There seems to be:

A bug somewhere in the RetroPie audio script since 4.8 (whatever update coincided with the ".asoundrc is no longer being used" message).

Why would raspi-config generate .asoundrc when we should be using /etc/alsa/conf.d/99-retropie.conf? Why multiple config files for the same thing?

Something kind of bug or interaction with omx player.

I think most of those who are posting with lvl0 volume mixer issues who aren't helped by your guide are stumbling because they have omx player enabled.

To answer your question, pulseaudio is not installed by default on RetroPie 4.6.1.

@babyboodle said in PulseAudio unable to connect; poor emulator performance issues and menu crashes.:

reset to default settings

If you have reset RetroArch to default settings in the RGUI and then saved the config you have probably set non ideal defaults. Our defaults are not the same as the RetroArch defaults. You should remove /opt/retropie/configs/all/retroarch.cfg and reinstall retroarch from "Manage Packages/Core Packages"

@mitu that seems to have done the trick, thanks for your help.

@mitu said in Audio Settings w/ PulseAudio:

@bluestang It should be fixed now in latest RetroPie-Setup, make sure you update if you wan to test it again.

Thanks, works as expected.

I found my solution and I will post it out here so it might help someone else with bluetooth audio problems.

I think my whole issue is because I did not add user "pi" to bluetooth. I followed the article here https://retropie.org.uk/forum/topic/20338/tutorial-bluetooth-audio-on-retropie-v4-4-and-raspberry-pi-3-model-b

Finally bluetooth connected in the GUI and it worked out for me in the end.

Update: I tried these instructions: https://raspberrypi.stackexchange.com/questions/53408/automatically-connect-trusted-bluetooth-speaker/76288#76288

Installed BaReinhard's repo and rebooted. I was able to connect to the AirPods when it launched back up and for a brief moment sound actually came through from youtube on the AirPods and I thought I may have fixed it, but then it cut out again after about two seconds. I'm getting the feeling that it connects and then gets disconnected almost immediately for some reason. Indeed, looking at bluetoothctl it seems to connect then disconnect to the devices immediately.

E.g. it will say:

sudo bluetoothctl
Agent registered
[CHG] Device D0:03:4B:ED:E5:20 Connected: yes
[CHG] Device D0:03:4B:ED:E5:20 Connected: no
[CHG] Device D0:03:4B:ED:E5:20 Connected: yes
[CHG] Device D0:03:4B:ED:E5:20 Connected: no

in quick succession, continuing on with this "yes/no" pattern. It does not seem able to maintain a connection.

Don't know if that sheds any light on the problem.

@mitu Thanks, I have an official Pi 4 Retropie build, modified for KMS and using legacy audio.

I was surprised that the MESA did not update at all (from 19.3.2.1) but I'm not overly concerned by this.

Thanks for providing the log file. I don't notice anything different between the 2 runs, so it's not something related to a configuration.
Try removing pulseaudio completely then reboot the system, this might get rid of any PA interference.

Finally fixed this, and just in case anyone has a similar unconventional setup and the same problems, the solution was, on the pi, edit /etc/pulse/default.pa and change:

load-module module-udev-detect tsched=0

to

load-module module-udev-detect

The finally solution for me was manage the relationship 1:1, one speaker with one dongle (USB). For spread the sound on all speaker i used an virtual audio card with "paprefs". Maybe we'll see this skills on new Bluetooth versions.

Sorry for the lengthy delay in replying...
IRL got in the way :-)

OK so it's definitely only the navigation sounds missing. I've tried several themes and none seem to have sound.

I'm guessing they must not be supported in Ubuntu as i don't seem to have them in the Sound Settings menu item.

Oh well :-)

Ah, should have read the rules properly sorry

Only audio issues I noted were when I closed out of Kodi, the menu audio was off by a second or so.