9 ms·
PipeWire: A year in review and a look ahead
- jboynyc 5y agoI recently made the switch in NixOS and found it pretty painless. Can't get my mic to work in Firefox though, and the other day I was looking through the manual trying to figure out how to use my HDMI screen's speakers rather than the built-in one and couldn't find the right incantation. Sounds like such rough corner cases will be a thing of the past soon. Congrats to the dev team!
- filmor 5y agoYou can still use pavucontrol for configuring in- and output devices per application.
- noisy_boy 5y agoThat is how I have to manage the target output when Pipewire doesn't switch the audio to my Bluetooth headphones upon connection (sometimes it does). The confusing part is that the selected/target output in Settings->Sound on Pop!_OS continues to show as the headphones but the sound from the application, say Firefox, doesn't switch to that (clicking on Test works perfectly which is when I realized that the issue probably was not with Bluetooth/headphones but about per-app switching and tried pavucontrol which confirmed the doubts by showing Firefox output still going to analog stereo).
- MayeulC 5y agoSometimes, especially on intel platform, you need to configure the sound card to output HDMI audio instead of speakers/headphones. At least with pulseaudio (change sound card profile in pavucontrol's settings tab).
- chockchocschoir 5y agoI wonder how your setup is different than mine. I also switched to Pipewire (some months ago) and I'm using NixOS and Arch Linux, and on both I could just change the audio output to my speakers on my monitors (via HDMI) with the usual device switch, same as before with just PulseAudio. Everything works perfectly.
- lillecarl 5y agohttps://github.com/Lillecarl/nixos/blob/1c76775bbed80057cf5438e5766a2fcc32e8a256/common/default.nix#L441 https://github.com/Lillecarl/nixos/blob/1c76775bbed80057cf54... https://github.com/Lillecarl/nixos/blob/1c76775bbed80057cf5438e5766a2fcc32e8a256/common/default.nix#L457 https://github.com/Lillecarl/nixos/blob/1c76775bbed80057cf54... This is my pipewire config, does the job perfectly for me, tracking unstable.
- anotherhue 5y agoOff topic, but I watched the ffmpeg args that go-chromecast used and scripted it. Now I preproces my videos and use catt. You can detect when they're h264 and use - c:v copy for speediness.
- jboynyc 5y agoI must admit I simply didn't realize the pulseaudio commands would still work. I figured they wouldn't because they were no longer installed after disabling pulseaudio and switching to pipewire. That's why I was trying to make things work with the pw-* commands and failing.
- heavyset_go 5y agoHave you tried different profiles for your hardware?
- mauricioc 5y agoAssuming you're talking about Bluetooth mics: If you're using pipewire-media-session (for example, if you're on NixOS 21.11 instead of NixOS unstable), then profile autoswitching [0] is disabled by default, so you have to use pavucontrol to switch from A2DP to HSP. Profile autoswitching is enabled by default in WirePlumber, which is the default session manager in NixOS unstable as of a few days ago. [0] https://wiki.archlinux.org/title/PipeWire#Automatic_profile_selection https://wiki.archlinux.org/title/PipeWire#Automatic_profile_...
- codethief 5y agoWait what. I've desperately been waiting for this feature and now I learn it's already been there for a while (albeit disabled by default). ._. (Kinda goes to show that enabling this feature by default is a good idea.) Thanks, you just made my day!
- yencabulator 5y agoFor the command-line folk: # mic on, worse audio quality pactl set-card-profile bluez_card.DE_AD_BE_EF_FA_CE headset-head-unit # mic off, better audio quality pactl set-card-profile bluez_card.DE_AD_BE_EF_FA_CE a2dp-sink
- 29athrowaway 5y agoI've switched to Pipewire. I couldn't A2DP working until I restarted, for some reason. Now everything runs OK.
- eternityforest 5y agoMaybe you still had a pulse daemon running
- 29athrowaway 5y agoThat's possible.
- heavyset_go 5y agoIn my experience, switching to WirePlumber fixed the few problems I had originally had with the default session manager.
- atoav 5y agoWireplumber looks very capable to me, although I think the documentation could be better, especially there could be more examples for more advanced configuration. One thing I still fight with is pw-loopback. I like to create a default sink that I can remap to my sound card. Playing a simple sine over that will give me hickups and dropouts. There is nothing in the documentation of pw-loopback that tells you any about this and as of now I could not resolve it. When I plug the same output directly into the soundcard in Catia, the sound issues are gone.
- russnes 5y agoI'm using pipewire and pipewire-pulse in void linux, and everything works perfectly.
- gspr 5y agoDo Bluetooth devices also work perfectly? For me, BT works perfectly with PulseAudio. PipeWire is very satisfying for absolutely everything else, but BT devices just refuse to connect (and I'm inept at debugging BT issues).
- alias_neo 5y agoFor me, on several machines, the _only_ way I could get Bluetooth devices to connect, behave, and to use their high quality codecs was switching to PipeWire. As it stands, between my desktop (Manjaro), laptop (NixOS/Ubuntu) and work laptop (Ubuntu 20.04), I have one single issue with Pipewire; on my work laptop if I have audio output set to HDMI (monitor speakers), when I plug in a wired headset to join a conference call it doesn't switch to the headset. If it's set to internal speakers first, it _does_ switch. So, if I have a conference call and I was using the monitor speakers, I have to jump into the Gnome sound control and switch to headset manually.
- qalmakka 5y ago0 issues with PipeWire and Bluetooth audio in my experience. Try setting `bluetoothd` logs to debug and look a bit on what's happening.
- Toblerone 5y agoI had problems until i realized i still had `pulseaudio-*` packages installed. Now I only have `pipewire` and `pipepire-pulse` and everything works flawlessly.
- gspr 5y agoThanks, that's a useful hint!
- kaishiro 5y ago
- TD-Linux 5y agoI have been impressed how I've been able to make arbitrarily complex audio graphs in QJackCtl and it just works. I can even activate patch bays and it forces the audio configuration and applications (even browsers) stay happy. It's impressive how it manages to support connections that require reclocking and do the needed large ratio resampling needed behind the scenes, something that PulseAudio was never really able to do. It's also nice for monitoring while streaming and seems to have much lower latency than OBS's monitoring.
- jcelerier 5y agoNote that qjackctl's author has made qpwgraph which is a similar tool but tailored to pipewire, it works great (and is already available in e.g. ArchLinux AUR, or here otherwise: https://gitlab.freedesktop.org/rncbc/qpwgraph https://gitlab.freedesktop.org/rncbc/qpwgraph )
- pimeys 5y agoIs there a good writing about setting OBS with monitoring using Pipewire? I'd be really excited to make my Zoom streaming better with OBS.
- bsder 5y agoDumb question: what did the Pipewire developers do that makes it so much better than everything else on Linux? Sound has been an absolute disaster area on Linux for decades and it seems like the Pipewire guys just flat out solved it. (I would say "suddenly", but Wim Taymans has been working on this directly for almost 7 years and worked on Gstreamer before it) What did they do so much better and differently?
- marcodiego 5y agoSome of the pipewire devs are old pulseaudio and jack devs. They are fixing their mistakes now. With a common goal, at last.
- TD-Linux 5y agoIn my case, the big advantage is the automatic insertion of resamplers between different clock domains, meaning you can connect anything to anything. Pulseaudio tries really hard to make sure there is only one clock driving any connection graph, so that's why there's no arbitrary connection support without loading things like module-loopback that add the resampling themselves. Another thing that helps is that in some ways PipeWire is less featureful than PA. For example, it limits the max audio buffer size to ~180ms which means it doesn't have to implement rewinds, one of the buggier features of PA (with the downside that power consumption can't ever be quite as low as PA).
- shutty 5y agoCan anyone explain me like I'm five, why this major transition from PulseAudio to PipeWire is happening during the last year?
- frankzander 5y agobecause it's very easy to use and works good
- faho 5y agoPipewire was started by Wim Taymans, one of the gstreamer people. Originally it was supposed to allow video-streams in sandboxed environments like flatpak (and was known as "pulsevideo"), but then he noticed that it could be extended to do audio as well. Since pulseaudio's architecture isn't well-suited to incorporate sandboxing, that project continued and it turned out that it could handle compatibility with both pulseaudio (the sound server for "consumerist" needs) and jack (the one for "pro audio" people where low latency is paramount). You can even use programs like QJackCtl, which was written for Jack, to perform audio routing and stuff with pipewire! So now, we have a sound server that 1. is much nicer to configure than pulseaudio 2. is compatible with sandboxing 3. is compatible with pulseaudio, jack and the older alsa APIs and features 4. is developed much more quickly than either of the others See also https://fedoraproject.org/wiki/Changes/DefaultPipeWire https://fedoraproject.org/wiki/Changes/DefaultPipeWire
- eternityforest 5y agoWim Taymans is amazing. Maybe one of the greatest programmers of all time.
- jabl 5y ago5. Pipewire doesn't use buffer rewinding, which was a rich source of complexity and bugs not only in PulseAudio, but also exposed bugs in the kernel audio device drivers. And even bugs or poorly specified behavior in HW itself, considering AFAIU neither macOS, Windows (nor Jack) use rewinding.
- 5y ago
- throwaway984393 5y agoStill facing several bugs in pipewire/wireplumber on Alpine. Not entirely sure if I missed some configuration (it's a bit confusing) or just buggy, though I've def seen some other user reports with the same bugs as me. Probably going back to pulse to get working audio/bluetooth again. Linux is a real trip, man. Bluetooth was introduced 24 years ago and we can still barely make it work. Seems to work on Windows, Android, Mac.
- SettembreNero 5y agoNever encountered a platform that didn't gave me problems with Bluetooth, honestly. Maybe on other platforms things are a little bit smoother but also with inferior troubleshooting.
- qalmakka 5y agoPipewire is a blessing. It fixed so many things I can't really start listing them. Funnily, in my experience, it is a arguably better PulseAudio implementation than PulseAudio itself.
- mkdirp 5y agoI'm not a pro user but PipeWire has been mostly great. I originally switched because of PulseAudio was causing a hissing noise on with my bluetooth headset, and switching fixed it. However, there are still two issues that I'm struggling with and haven't been able to find a definitive answer for. One is the audio sometimes randomly jitters while simply playing music. It seems this only happens when I use my bluetooth headset, but is fine with built-in audio. The other is, when the automatic switching to bluetooth headset is hit and miss. Sometimes it switches, sometimes it doesn't, and sometimes one applications switch, but others don't. So I'm left to use pavucontrol to switch things over correctly. My searches haven't returned any fruitful results so I'm not if I'm just searching for the wrong things or I'm the only person who has these issues.
- durazabu 5y agoYou are definitely not the only one was has the issue about the automatic switching to bluetooth headset. One workaround is to run `pactl load-module module-switch-on-connect` (not persisted across reboot) as recommended on the arch wiki: https://wiki.archlinux.org/title/PipeWire#Sound_does_not_automatically_switch_to_Bluetooth_headphones https://wiki.archlinux.org/title/PipeWire#Sound_does_not_aut...
- mijoharas 5y agometa comment: I find it's almost always worth checking the arch linux wiki for any software you're using (either as a guide or if you're having issues). It's one of the best resources out there, though obviously if you're not running arch you'll need to tweak things from the suggestions.
- InfiniteRand 5y agoHas switching to a bluetooth headset on Linux ever been non-buggy? I mean I imagine for specific hardware-software combinations it works robustly, but I feel like this is a periodic issue I have to deal with on Linux machines
- mkdirp 5y ago
- doix 5y agoSome more anecdata, I switched to pipewire when I bought my new laptop and it was great. I was struggling to get pulseaudio working properly, switched to pipewire and installed pipewire-pulse[0] from the arch packages, and stuff "just worked". It's one of the only times in recent memory that moving over to 'the new thing' actually worked without significant pain. https://archlinux.org/packages/extra/x86_64/pipewire-pulse/ https://archlinux.org/packages/extra/x86_64/pipewire-pulse/
- mijoharas 5y agoI actually did have a few issues and things to tweak when I switched (I think I did it fairly early) but after some initial setup everything started working perfectly.
- kirenida 5y agoIs anybody here using pipewire to stream to a different machine on the same network? I currently use Pulseaudio to send audio from my laptop to a raspberry (with a DAC hat) connected to my hifi, but it turns out it's a pretty niche use case. So I'm looking for anybody with a similar use case who has upgraded from PA to PW and can talk about the experience.
- jck 5y agoI've had good luck with this method: https://wiki.archlinux.org/title/PipeWire#Sharing_audio_devices_with_computers_on_the_network https://wiki.archlinux.org/title/PipeWire#Sharing_audio_devi...
- kirenida 5y agoYeah, that looks like the PA conf I'm currently using. Did you notice any difference after switching to Pipewire?
- mr_person 5y agoI have been attempting this in some way or another for a month or two. So far, no luck. The most realistic option I have found would be to use NetJack, but while its been noted in a roadmap as a relatively straightforward protocol, it is not yet implemented (at least, it wasn't last time i looked). It may be possible to hack a pipewire-jack client to do it now... but that seems like more effort than its worth. An alternative would be Scream, if all you want is one-way streaming. If anyone has any other ideas, i would be very much interested too!
- em3rgent0rdr 5y agoYou could also use jacktrip. Jacktrip is a jack client, so it will work under pipewire.
- gbtw 5y agoI have a similar setup, however it seems that video doesn't want to play in browsers with the networked audio for some reason. Anyone else experience that?
- kn100 5y agoAs someone who has a fairly basic use case for something like Pipewire - I switched to it about a year ago and hope to never switch back. Everything just works properly - and some of the value added stuff we have now (Easyeffects inside a Flatpak sandbox comes to mind) are very cool and work extremely well. My thanks to the developers, who have done an AMAZING job of building a realistic alternative. There is a lot of REALLY good software coming out for Desktop Linux recently. Wayland, Pipewire, Wireguard, etc!
- phkahler 5y ago>> There is a lot of REALLY good software coming out for Desktop Linux recently. Wayland, Pipewire, Wireguard, etc! etc indeed: OBS Studio VLC Ardour, LMMS, MuseScore LibreOffice (Writer, Calc, Impress, Draw, Base) GnuCash, Scribus, Dark Table, Inkscape, Krita, Blender, Synfig Studio, Gimp KiCAD, LibreCAD, FreeCAD, OpenScad, Solvespace, Slic3er And untold others that are incredibly useful.
- encryptluks2 5y agoMany of programs you mention are useful, but not new and really aren't that great at showcasing a great user experience.
- 127 5y agoI would single out both Krita and Blender. Both are fantastic projects that really elevate what you can do artistically with free software.
- stncls 5y ago> Everything just works properly Not to mention the drastically lower CPU usage compared to its predecessor [1] and general lack of bugs. > There is a lot of REALLY good software coming out Agreed, but I would still single out PipeWire as being particularly outstanding. None of the other examples are as new, or as uncontroversial. Anecdotically, when I look at the comment section of any PipeWire article here, I see basically universal (and enthusiastic) praise. In my case, it comes from the fact that so many sound servers have existed before, and none were even close to satisfactory, until now. It seems genuinely like a hard problem. [1] https://news.ycombinator.com/item?id=28502614 https://news.ycombinator.com/item?id=28502614
- zibzab 5y agoMost pipewire users here seem to be arch users with access to bleeding edge releases. But how does PW work for, say, Debian/Ubuntu users?
- adia 5y agoDebian unstable user here (and also Gentoo on a different PC) - I've removed PulseAudio for a couple of months now, and everything works nicely (including a Bluetooth headset and HDMI audio out) with PipeWire and WirePlumber - the only hiccup was an old manual configuration I had for ALSA to use PulseAudio as default audio sink, which needed to be removed. I haven't tested Jack compatibility yet.
- WhatIsDukkha 5y agoWorks great on debian bookworm as a full replacement for jack and pulseaudio. Read the debian wiki for the setup.
- dlundqvist 5y agoI use it together with wireplumber on three systems, all running bookworm. One old MacBook Air, a fairly new ThinkPad and a run-of-the-mill desktop PC. Works flawlessly on all of them. I have no custom configuration, all default what comes from the packages. For the laptops I also use BT headphones, and with the ThinkPad I use a headset that with the latest wireplumber switching profiles just work whenever I join a meeting with Slack or Teams (both in Google Chrome). For the desktop PC I had a use case I never got working properly, or at least easily, with PA. That is to expose all the HDMI outputs of the graphics card as separate sinks. With PW, just switch over to the Pro profile and they all appear. Then I can route what ever stream/application I want to a specific HDMI output. Additionally, I use USB MIDI devices and a software synth, qsynth, using JACK. Setting up both MIDI and audio routing via qjackctl is so convenient. Oh, and USB audio devices also work without a problem. Can't say if that is different from PA as I never used them much before.
- goodpoint 5y agoDebian Sid (aka Unstable) is just as bleeding edge as any other "rolling" distro.
- zaggynl 5y agoYeah it's awesome, if only nomachine(https://www.nomachine.com/ https://www.nomachine.com/, MS Remote Desktop alternative) would add support for it, that or I missed something to get it to work.
- deleted 5y ago[deleted]
- alfiedotwtf 5y agoI gave pipewire a go for a few hours tonight, but couldn't get the A2DP profiles to appear in pavucontrol. Bluetoothctl seems to happily connect and pair, but there's nowhere to point the output to my bluetooth headset :(
- smasher164 5y agoBig fan of PipeWire, although I wish the tooling could work directly with PipeWire, instead of going through pactl. It's there, it's just not user-friendly. I ended up writing a tool for changing volume/muting that directly uses pw-cli: https://github.com/smasher164/pw-volume https://github.com/smasher164/pw-volume.
- danShumway 5y agoAgreed, at least to a certain degree :) I never really got good with pactl or the various other interfaces, so while it's great that Pipewire is compatible with them, I was also hoping that Pipewire would mean I never needed to get comfortable with them. If I have any criticism of Pipewire, it's that as someone who is not really interested in learning all of the quirks and weirdness of the old systems and would happily never really learn those systems except for older compatibility reasons, it's slightly weird to be running Pipewire and have all the tutorials that I've run into around it still start with, "let's learn some Pulseaudio commands".
- Arnavion 5y agoYou can also munge the pw-dump output with jq, instead of needing something to be compiled. pw-dump | jq ' ( .[] | select(.type == "PipeWire:Interface:Metadata") | (.metadata // [])[] | select(.key == "default.audio.sink") | .value.name ) as $default_sink_node_name | .[] | select(.info.props["node.name"] == $default_sink_node_name) as $default_sink_node | . '
- smasher164 5y agoYes. This is how I did it initially, before rewriting it using serde. However, as I mention here (https://www.reddit.com/r/swaywm/comments/sks343/comment/hvn3p3c/?utm_source=share&utm_medium=web2x&context=3 https://www.reddit.com/r/swaywm/comments/sks343/comment/hvn3...), shell with jq was too slow -- particularly if you're holding down the volume key.
- 5y ago
- mxmilkiib 5y ago2p; it would be nice to see native PW CV rather than JACK API CV, as well as some form of integration with NSM for saving graphs and making them portable.
- pabs3 5y agoI just wish PipeWire didn't have such choppy audio under load, pulseaudio doesn't have the same problem.
- _joel 5y agoI might start to look into Linux again for DAW usage. I'm very much on Logic/MacOS and dip my toe every so often (well have done since Dynebolic days) but always go back to Logic.
- squarefoot 5y agoCan anyone link to some documentation explaining how to make it work without messing with other software? I tried twice to enable it on two different Debian installs, and both times I suddenly lost access to all my MIDI devices under Wine (no matter the user or the Wine version), although they were still perfectly usable by native Linux software, so I had to uninstall it back.
- danShumway 5y agoMy switch to PipeWire on Arch has been mostly painless except for one particularly annoying bug that I haven't been able to track down yet -- when the computer is hibernated, something in the config goes wrong and I need to rerun `alsactl init` to get sound playing again. I'm certain this has something to do with me doing a bad install and not cleaning up old config files or something, possibly with either me either using PulseWire or not using PulseWire to manage the session, but it's pretty annoying (although apparently not annoying enough to get me to debug the issue). Otherwise, it seems to basically just work. I'd love to do more with it, but truthfully I didn't really dig into Pulse/Alsa/Jack enough initially to really notice what the benefits are, so I can't tell a difference. One thing I'd love is for a cleaner command-line interface to handle sinks, particularly when scripting. I'm sure if I took the time I'd understand them, but I find PulseAudio's sinks really annoying to work with and to manipulate. Again, I think this is mostly just the fact that I never really dug into Linux audio too deeply before so I'm not always completely sure what's going on with it, and I'm not doing anything complicated enough for me to immediately tell a difference. In some ways I guess that's a recommendation; if I managed to get the hibernation bug fixed then this would be a totally transparent switch from my perspective. That seems kind of impressive.
- josteink 5y ago> WirePlumber was made the default PipeWire session manager in Fedora 35 That sounds great and all, but can someone enlighten me exactly what a session-manager is, in the context of Pipewire? I’m using Pipewire and it works fine. But is this something I should know about? Something I can or should tweak? Or is it mainly for the distro-maintainers?
- mrlonglong 5y agoI tried to get pipewire to work in Gentoo on my laptop. I was not successful. I do hope things will improve.
- t00 5y agoI switched to PipeWire few months back on Manjaro and apart from a problem with packages when switching, there is one issue which bothers me slightly - Bluetooth headphones delay. I tried all codecs on my QC35-II, 3 different BT 4 and 5 dongles and the delay is unbearable, rougly 500ms, kills CS:GO experience. On a headphone jack PipeWire is great, audio is clean without any glitches. Just this bluetooth...
- skrtskrt 5y agoNo delay on Fedora 35 with all defaults
- aftbit 5y agoI've also experienced this on Arch Linux, in the form of a variable delay to my bluetooth speaker under pipewire but not pulseaudio. I also noticed a lot more general bluetooth flakiness. I have not characterized the issue nearly as thoroughly as you have. Instead I ran a wire to the other side of my office and installed some DIY speakers, which rendered the problem moot. Regardless, I've always had issues getting bluetooth to work reliably, especially on linux.