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.
As someone who has pulse just the way they want it, what will this mean for me?
Is it a forced change on a current install?
Is there an equivalent to PulseEffects for PipeWire?
Actually, PulseEffects has been renamed into EasyEffects and is PipeWire only now
I find Easy effects is much more feature rich easier to import APO files and such
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.
PulseEffects is still working fine for me is why I was asking. Been using it for the past year after making the switch.