--audio-backend=alsa
doesn't necessarily mean that Kodi is using ALSA directly. Only if PipeWire currently isn't using the ALSA device at all will Kodi be able to grab it, otherwise it will still go through the PipeWire ALSA compatibility layer. To make sure Kodi is using PipeWire directly you can check
pw-top
, if Kodi isn't showing up as a client while playing audio it is using ALSA directly. If it's using the PipeWire ALSA compatibility it looks something like this:
Code:
S ID QUANT RATE WAIT BUSY W/Q B/Q ERR FORMAT NAME
I 29 0 0 0,0us 0,0us ??? ??? 0 Dummy-Driver
S 30 0 0 --- --- --- --- 0 Freewheel-Driver
S 47 0 0 --- --- --- --- 0 Midi-Bridge
S 52 0 0 --- --- --- --- 0 bluez_midi.server
R 55 2048 48000 159,1us 33,3us 0,00 0,00 0 S32LE 2 48000 alsa_output.pci-0000_05_00.6.analog-stereo
R 73 2400 48000 79,3us 37,1us 0,00 0,00 0 F32LE 2 48000 + alsa_playback.kodi.bin
S 56 0 0 --- --- --- --- 0 alsa_input.pci-0000_05_00.6.analog-stereo
S 67 0 0 --- --- --- --- 0 Firefox
I 76 0 0 0,0us 0,0us ??? ??? 0 F32LE 2 48000 Firefox
Note that Kodi doesn't keep the ALSA device busy all the time so PipeWire may grab it at some point and then Kodi and PipeWire try to use the same ALSA device simultaneous which can cause terrible distortions.
(2024-08-02, 00:28)DaVu Wrote: That command will remove pipewire and will install wireplumber
This really shouldn't remove PipeWire. Both pipewire-media-session and WirePlumber are PipeWire session managers and only work with PipeWire. The difference between the two is that WirePlumber is more powerful and has become the recommended default.