Nice! Leaves me wondering why the funding was increased tho. Is it because the SFT projects have been successful so far? Or because they were not moving fast enough? Or perhaps simply because more money was needed to achieve this year's aims?
Granted, 4 mil might not be an enormous amount for an institution this size.
One thing that hasn't been mentioned yet is interopability, that is, flatpak interacting with the rest of your system.
I'm not that familair with flatpak, but in my brief experience with the steam flatpak, I had trouble getting it to recognize my controllers. Steam installed through pacman (Arch's package manager) had no such issues, on the other hand. My hunch is that this has to with flatpaks being more isolated from the rest of your system.
Im pretty sure that's just some kind of permission issue, but it can be nice to not have to troubleshoot acces rights and the like. But this is obviously a double edged sword: more isolation may also mean more security, just at the cost of ease of interaction with other components.
There's a compability layer, generally called pipewire-pulse. I think it's not a one-for-one copy, but it works great for desktop applications that expect pulse.
Some things that previously were pulseaudio modules, like rtp and raop (airplay), have been reimplemented as native pipewire modules, I believe.
More complicated setups I can't personally speak to, but since pipewire is also catered towards professional audio workflows (as opposed to just desktop audio), you should at least be able to replicate what you have now.
And, as others have already pointed out, pulseeffects has been long dead, and now lives on as easyeffects.
Nice! Leaves me wondering why the funding was increased tho. Is it because the SFT projects have been successful so far? Or because they were not moving fast enough? Or perhaps simply because more money was needed to achieve this year's aims?
Granted, 4 mil might not be an enormous amount for an institution this size.