Re:The Linux audio stack demystified (and more)
by vetinari on Tuesday July 23, 2024 @08:42AM
(#41045353)
> I am unclear why Jaroslav Kyocera chose to make ALSA single-client, but Apples CoreAudio multi-client driver model is the right way to do digital audio on general-purpose computing devices running multi-tasking OS'es on application processors, in my opinion.
Because ALSA is a different layer in the audio stack than CoreAudio.
But on the Mac side everyone is OK with using CoreAudio (with the accompanying set of daemons), while on Linux, for some reason, everyone wants to go as low-level as possible, "just open the device file" and is wondering, why something is missing. Because you skipped that, that's why.
Because ALSA is a different layer in the audio stack than CoreAudio.
ALSA corresponds to MacOS drivers and I/O Kit.
CoreAudio (Audio Toolbox / Audio Unit) corresponds to Pipewire / Pulseaudio.
But on the Mac side everyone is OK with using CoreAudio (with the accompanying set of daemons), while on Linux, for some reason, everyone wants to go as low-level as possible, "just open the device file" and is wondering, why something is missing. Because you skipped that, that's why.