this post was submitted on 07 Oct 2024
368 points (96.5% liked)
Technology
60052 readers
2865 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'll also add the audio stack in Linux at the moment is a hot mess. I'm currently trying to resolve a problem that seems to exclusively plague the rear mic input on my system and nothing else and this shit is fucking obtuse. It's ridiculous how many competing audio frameworks there currently are.
There are only 2 current audio frameworks, right? PipeWire (most current, best compatibility from what I've seen) and PulseAudio (dominant for a long time but now being replaced by PipeWire)
Sort of kind of. The actual drivers are still ALSA which both pulse and pipewire build on top of. Then there's JACK which is older but basically tried to be Pipewire before Pipewire. Lastly there's WirePlumber which is an automation/scripting thing built on top of Pipewire. So depending on what you're doing you end up having to wrangle with a minimum of Pipewire and ALSA, and might also need to mess with WirePlumber and Pulse (as Pipewire exposes a Pulse API).
Just install wireplumber, plus the pipewire modules for alsa and pulseaudio (pipewire-alsa and pipewire-pulse, respectively). These 3 will run any audio application.