3 ms·
Firefox is cross platform. It has to support Win32/64 sound, Linux (alsa/pulse), whatever the hell FreeBSD and MacOS use .. Back in 2013 I had a lot of issues
by djsumdog 10y ago
Firefox is cross platform. It has to support Win32/64 sound, Linux (alsa/pulse), whatever the hell FreeBSD and MacOS use ..
Back in 2013 I had a lot of issues with Steam games not running correctly with PulseAudio (lots of static instead of sound half the time I tried to start a game). Sometimes doing a killall on the pulseaudio server would help, sometimes it would not. On that machine, I added a -pulseaudio USE flag in Gentoo and removed it entirely.
On my current machines, I do use Bluetooth audio and find PA easier to deal with. I also no longer play games on my Linux boxes.
I'm also old enough to remember the horrors of ESound and the KDE one (whatever it was called) and how audio would constantly be out of sync.
Pulse is a lot better and seems to do well today. Still Pulse has some huge limitations. Run two X servers and use either consolekit or systemd? Good luck trying to get audio to continue playing on both X servers at the same time. It won't. Want to run MPD as a system daemon? You'll need to figure out how to enable TCP in Pulseaudio.
I don't run SystemD, but I do run Pulseaudio. Those are my choices. Gentoo still gives me that choice, which is why I use it as my home and work distro. Void is another great Linux distribution that gives you such choice as well.
Like I started with, Firefox has to support a ton of audio backends for various operating systems. We're not talking about maintaining OSS support. Pulse still depends on ALSA in the Linux kernel for it to work, so ALSA isn't going away any time soon. There's no reason for Firefox to need to depend on that intermediary layer and remove direct access when that already exists.
- RSZC 10y agoI do run MPD as a system daemon, can't recall having to do anything crazy with Pulseaudio...
- djsumdog 10y agoMaybe your distro has it configured by default. I had to modify config (you can change the one in your home directory or the system on in /etc/pulseaudio/default) to include something like module-native-protocol-tcp auth-ip-acl=127.0.0.1 You could also use auth-anonymous=1 but if you're not careful with that, people can play stuff on your speakers. We use to mess with each other at work doing that. :-P
- paulfurtado 10y agoNote that by default in most distributions, pulse starts running when a user logs in, and runs as that user, but it can easily be configured to run as a system daemon instead to support multiple user sessions using it at the same time.
- djsumdog 10y agoYes, but ALL OVER the official documentation it says running it as a system daemon is not recommended at all. But yes, in the above use case, that would solve the issue of audio not continuing when switching X sessions without needing module-native-protocol-tcp.
- flukus 10y ago> the KDE one Phonon? Wasn't that just a layer on top of pulse and/or alsa?
- djsumdog 10y agoHad to do a few searches but I found it: artsd (part of https://en.wikipedia.org/wiki/ARts https://en.wikipedia.org/wiki/ARts)