Originally posted by caligula
View Post
People were attempting to add audio effects like noise removal with pulseeffects before pipewire. So not having routing graphs and DSP effects in pulseaudio was leading to some horrible work around as well.
Remember pipewire can store and use all the meta data pulseaudio did so is able to use that metadata to do simple setups. Due to having the means to do metadata all the way out to jackaudio like stuff as well means you can have a simple setup with a little complex mixed in.
There is a little more complexity doing the server the pipewire way for audio. But the server design being a little more complex means not needing horrible hacks because you have run into a limit of functionality of the audio server.
See the yes and no. Yes it is slightly more complex but over all its not more complex because you don't have horrible hackly solutions for like pulseeffects was to add in functionality. Pipewire might be just at the ideal sweet spot for a audio sound server on complexity. The hard problem of being complex enough to perform the tasks required and not too complex to use.
Comment