Le mar. 27 sept. 2022 à 11:44, Dylan Aïssi a écrit :
> Make wireplumber sending a signal when it is ready seems the proper to way
> to follow. Thanks for your suggestion! These changes should be done directly
> in wireplumber/pipewire, I will report it to upstream.
>
Forwarded to:
https://gitlab
Hi Matthias,
Le lun. 26 sept. 2022 à 12:09, Matthias Heinz a écrit
:
>
> I'm certain now that this is a race-condition between wireplumber and
> pipewire-pulse. Even though wireplumber should be started before pipewire-
> pulse the Type= to start the service is just "simple", which means wireplu
reopen 1019944
Hi Dylan,
sadly the last patch didn't work for me, as you already know.
I'm certain now that this is a race-condition between wireplumber and
pipewire-pulse. Even though wireplumber should be started before pipewire-
pulse the Type= to start the service is just "simple", which m
H,
Le ven. 16 sept. 2022 à 19:51, Matthias Heinz a écrit
:
>
> after upgrade wireplumber from 0.4.11-3 to 0.4.11-5 it fails to somehow
> realize
> what the target of the last stream was, if it was not the default device.
> pavucontrol just reports it as "Unknown output" then.
>
In Wireplumber
Hi,
with the help of NiklvsKoesikovs from the pipewire irc channel we came to the
conclusion that the order in which pipewire-pulse and wireplumber are started
matter.
pipewire-pulse has to be startet AFTER wireplumber.
Please add this to the systemd service file.
Thanks
Matthias
Package: wireplumber
Version: 0.4.11-3
Severity: important
X-Debbugs-Cc: m...@familie-heinz.name
Hi,
after upgrade wireplumber from 0.4.11-3 to 0.4.11-5 it fails to somehow realize
what the target of the last stream was, if it was not the default device.
pavucontrol just reports it as "Unknown o
6 matches
Mail list logo
