Ben Cotton wrote on Fri, Nov 20, 2020:
== How To Test ==
This change needs to be tested on as many different audio cards as
possible. The same test plan applies here as with PulseAudio.
To test, one needs to install the pipewire-pulse library (which
removes the pulseaudio package).
Took me some time to figure out how to test:
- there's no such package; there's a pipewire-libpulse that apparently
got integrated into pipewire-libs but doesn't replace pulseaudio unlike
the comment above (in fc33's update-testing pipewire-0.3.16-1.fc33.x86_64)
- /usr/share/doc/pipewire/README.md talks about pw-pulse <appname> to
test but not how to replace the user's pulse socket
- there's pipewire-pulse and a pipewire.socket/service user service in
(the new) pipewire package, but the user service doesn't start
pipewire-pulse (unless the exec is commented out in the config maybe?)
I ended up manually removing the socket at /run/user/<uid>/pulse/native,
starting pipewire-pulse manually and killing the old pulseaudio instance
but I'm sure there's a better way?
I've messed around with (very casual) things and everything appears to
work, with pipewire-pulse spewing some warnings when I tried pavucontrol
[W][001555077.904969][pulse-server.c:411 reply_error()] pulse-server
0x56434a66a640: [PulseAudio Volume Control] ERROR command:87 (EXTENSION)
tag:17 error:19 (Operation not supported)
and errors when a client disconnect
[E][001555597.840471][core.c:71 core_event_error()] core 0x56434a67f520:
proxy 0x56434a67f520 id:0: bound:-1 seq:667 res:-22 (Invalid argument)
msg:"unknown resource 40 op:3"
both are probably harmless, and that aside everything looks great; I
think making things easier to test (or clarifying the procedure) for
fedora 33 would help reassuring people about it.
Haven't tested the jack side of things as I don't use it normally.