ALSA flag conflicts with Sound I/O flag?

[milch]

Enabling ALSA at the same time as sndio makes palemoon try only ALSA.
The error thrown says it's in `loop.c : 70` - `can't make support.system handle`
That error comes from the ALSA library as far as I could tell, so might or might not be of help.

[vannilla]

As far as I know ALSA and sndio are mutually exclusive (but correct me if I'm wrong) so you're better off enabling only one at a time, never both.

[milch]

Enabling one or the other involves rebuilding, that's the issue.
I feel it shouldn't be needed if the browser checks every enabled one and uses the responsive one if any.
I'm trying to improve the quality of life of my unofficial musl builds, that's how I noticed.

[Moonchild]

I feel it shouldn't be needed if the browser checks every enabled one and uses the responsive one if any.

Enabling ALSA at the same time as sndio makes palemoon try only ALSA.

The checking would happen in a specific order, right? Whichever comes first would be the one used, in that case. If that's ALSA, then it would use ALSA. Doing the check at run-time might be a lot more complex (and risk serious bugs), so that's probably why it's a build-time exclusive thing only. I'll let Travis weigh in for details around the multimedia component in UXP.

[jobbautista9]

ALSA support is enabled by default when building for Linux, so an explicit --enable-alsa in the mozconfig wouldn't be needed. PulseAudio is also enabled by default if the OS is not Windows or Mac. Currently sndio and JACK (does that JACK support code even still work today?) are the only sound servers which don't have this kind of automatic enabling AFAICS.

This issue of ALSA always being chosen when both ALSA and sndio support are built has actually been a pet peeve of mine when I used to build my own browser for my Linux, so I always added both --disable-pulseaudio and --disable-alsa to ensure Pale Moon only used sndio in my Devuan setup.

The checking would happen in a specific order, right? Whichever comes first would be the one used, in that case. If that's ALSA, then it would use ALSA. Doing the check at run-time might be a lot more complex (and risk serious bugs), so that's probably why it's a build-time exclusive thing only.

When both PulseAudio and ALSA support are present, PulseAudio would always get "chosen" by Pale Moon. Perhaps because IIRC PulseAudio technically hogs all of ALSA for itself (while trying to capture the ALSA-only applications), while sndio doesn't. So maybe PM would see that ALSA is free and use that first, unlike with PA where it sees ALSA is unavailable to be used directly and so then tries to use PA...