starting mpv in a paused state makes pipewire mad
mpv -ao=pulse -pause Downloads/5.\ The\ Trestle\ Table\ -\ Planing\ The\ Tapers.mp4
which launches mpv in a paused state causes pulsewire to log things like:
(bluez_output.00_16_94_19_F1_EB.a2dp-sink-80) client too slow! rate:512/48000 pos:525826048 status:triggered
187 events suppressed
every two seconds, until mpv is unpaused.
I often have 7-8 mpv instances started in a paused state, which makes pipewire very mad (pulseaudio was fine with it). I say very mad because it seemed to crash sometimes, would log lots of angry messages, and no audio would come out of my bluetooth headset.