Support Linux Studio Plugins and Calf Studio Gear in PW's libjack implementation
So now that PW builds with PA and JACK shims by default, they can be used to fool PA & JACK apps into using PW as their sound daemons. However, when I tried to do so, after long and painful packaging dependency manipulations for PW and PA, I was not able to recreate my default desktop session using only PW.
I use JACK as main sound daemon with PA being its client but almost all ALSA & PA & JACK apps in the system by default are routed by qjackctl into pipeline LSP & Calf consisting of
- first 2 ports of lsp-plugins-spectrum-analyzer-x4
- Calf Stereo Tools
- lsp-plugins-para-equalizer-x16-stereo
- lsp-plugins-mb-compressor-stereo in "up" mode
- Calf Bass Enhancer
- Calf Multiband Enhancer
- lsp-plugins-limiter-stereo
- last 2 ports of lsp-plugins-limiter-stereo
- hardware output + lsp-plugins-latency-meter
[Playing sweet tunes of "AC7: Skies Unknown" - "Pipeline Destruction"]
I barely convince qjackctl to recognize PW as JACK server. But then it was not able to apply patchbay or recognize connections from LSP. LSP tools are all standalone binaries (with LV2 libraries for other host applications) while Calf plugins are ran by shared calfjackhost binary.
This setup is as good as you can get for default desktop audio handling (allows me to quickly fix any weirdness from misbehaving audio sources and bad recordings), clunkiness of UI and significant CPU chunk (mostly for optional wave graphs, not a problem for my new obsolete 50$ Xeon E5-2650v2 from 2013) notwithstanding. But PW's implementation seem too incomplete for now. I don't know what exactly is missing but it's probably a number of core features. Same goes for libpulse and PA's basic pasystray & paman & pavucontrol suite.