Hm? Removed pulse, installed pipewire-pulse, ran pipewire && wireplumber && pipewire-pulse as user and everything just works. Except that my cheap bt-inear sometimes cause a crash of bluetoothd (and that one should restart by itself but whatever) but that’s not pipewire’s fault.
@MonkderVierte@tjhrulz
Hm? Removed pulse, installed pipewire-pulse, run pipewire && wireplumber && pipewire-pulse as user and got no available sound devices.Why? Because wireplumber’s bullshit crashed after forking to daemon somewhere in camera support code (but i do not have cameras!).
With reference pipewire-media-session everything worked, but everybody forcing unstable and bloaty wireplumber, making old configuration not supported…
Yes, maybe it’s not pipewire fault, just it’s modular architecture, but it makes me unhappy with it, so i still using jack. And i sure, there should be separate provider processes for camera and audio devices
Hm? Removed pulse, installed pipewire-pulse, ran
pipewire && wireplumber && pipewire-pulseas user and everything just works. Except that my cheap bt-inear sometimes cause a crash of bluetoothd (and that one should restart by itself but whatever) but that’s not pipewire’s fault.@MonkderVierte @tjhrulz
Hm? Removed pulse, installed pipewire-pulse, run pipewire && wireplumber && pipewire-pulse as user and got no available sound devices.Why? Because wireplumber’s bullshit crashed after forking to daemon somewhere in camera support code (but i do not have cameras!).
With reference pipewire-media-session everything worked, but everybody forcing unstable and bloaty wireplumber, making old configuration not supported…
Yes, maybe it’s not pipewire fault, just it’s modular architecture, but it makes me unhappy with it, so i still using jack. And i sure, there should be separate provider processes for camera and audio devices