<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div>While I don't see the need of deprecating pulseaudio ( or even forcing users to switch !) ,<br></div><div dir="auto">pipewire has been an improvement in my experience. Bluetooth headsets for instance didn't really work at all with pulseaudio whereas under pipewire they mostly did. In GNOME pipewire became the default sound server, too. The user still has pipewire-pulse for compatibility and it also just *works*. Honestly I don't want to start a discussion about which sound server is better; imho we should provide the users with a way to start pipewire should they choose to run it. Maybe this could be mention on the d-wiki page ? The alpine wiki also mentions two ways of running it: in a dbus-session (needed for screensharing) or without it (see my comment on the bug report). Pipewire is also need to enable screensharing under wayland.<br></div><div dir="auto"><br></div><div dir="auto">regards,<br></div><div>---<br></div><div dir="auto">Matthias Geiger (werdahias)<br></div><div><br></div><div><br></div><div><br></div><div>21. Feb. 2023, 16:04 von kilobyte@angband.pl:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div>On Sat, Feb 18, 2023 at 06:24:50PM +0000, Matthew Vernon wrote:<br></div><blockquote><div>FWIW, I just reverted to pulseaudio for audio on my bookworm/sysvinit<br></div><div>system, and it works fine. So this might be the thing to suggest for the<br></div><div>general user?<br></div></blockquote><div><br></div><div>pipewire is drastically less buggy than pulseaudio, thus I see no reason to<br></div><div>not migrate to it by _default_. Obviously, having both is good as when one<br></div><div>fails the user can try the other as a workaround. Also, pulseaudio is<br></div><div>more battle-tested (even if it failed a lot of those battles), thus it has<br></div><div>kludges for some problems pipewire hasn't been beaten to work with yet.<br></div><div><br></div><div>The main problem here is that there's nothing that would start pipewire's<br></div><div>components; on systemd that is done by systemd-user-session. An easy way<br></div><div>would be a .desktop that runs during X startup, but that won't handle non-X<br></div><div>usage.<br></div><div><br></div><div>Also, the scope is different: pulseaudio does sound only, pipewire handles<br></div><div>both sound and video.<br></div><div><br></div><div><br></div><div>Meow!<br></div><div>-- <br></div><div>⢀⣴⠾⠻⢶⣦⠀<br></div><div>⣾⠁⢠⠒⠀⣿⡁ Q: Is it ok to combine wired, wifi, and/or bluetooth connections<br></div><div>⢿⡄⠘⠷⠚⠋⠀ in wearable computing?<br></div><div>⠈⠳⣄⠀⠀⠀⠀ A: No, that would be mixed fabric, which Lev19:19 forbids.<br></div></blockquote><div dir="auto"><br></div> </body>
</html>