>>108102536
Not him but...
>Anything else I should do to migrate? Any PA junk I can get rid off now?
You can get rid of all PA config files
>Anything else PW needs that I should have?
There are other optional deps in case you need them, such as pipewire-jack, pipewire-v4l2, etc.
>Now all my pactl commands are gonna turn into wpctl equivalents, right? What about pavucontrol? Do I substitute that for pwvucontrol? Anything else I'm forgetting?
If you have pipewire-pulse installed pactl and pavucontrol will work perfectlt OOTB on PW, no need to change anything
>For some reason my waybar modules for pulseaudio still work just fine, is that supposed to happen?
I'm assuming It's Pipewire running libpulse in the background. Should be fine to leave as is
You should be good to go but I recommend disabling node suspension to avoid audio pops and cracks:
~/.config/wireplumber/wireplumber.conf.d/disable-suspension.conf
monitor.alsa.rules = [
{
matches = [
{
# Matches all sources
node.name = "~alsa_input.*"
},
{
# Matches all sinks
node.name = "~alsa_output.*"
}
]
actions = {
update-props = {
session.suspend-timeout-seconds = 0
}
}
}
]
# bluetooth devices
monitor.bluez.rules = [
{
matches = [
{
# Matches all sources
node.name = "~bluez_input.*"
},
{
# Matches all sinks
node.name = "~bluez_output.*"
}
]
actions = {
update-props = {
session.suspend-timeout-seconds = 0
}
}
}
]
Then either restart pipewire.service and wireplumber.service or reboot the PC and you'll never have any audio issues on Linux ever again. Look into other configs on the Arch wiki if you want more specialized setups (realtime, JACK latency, etc.)
