Pipewire is a true blessing for Linux
Official Release Page for those who don’t want to read the Phoronix article: https://gitlab.freedesktop.org/pipewire/pipewire/-/releases/1.0.0
It’s great to see that Pipewire has reached this milestone. Personally I’ve been using it since 0.3.35 for very basic audio needs and it’s been a very smooth transition. After installation I never had to tinker with it anymore. "It just works"TM
I had to do some tinkering way back to make my bluetooth earplugs be recognized as an audio device.
Not sure if that is still needed today
No
deleted by creator
Genuinely one of the best pieces of software that these heroes are giving away.
I’ve seen so many audio changes on Linux. But Pipewire is the first one without any negatives.
For a long time, people shat all over pipewire and said it wasn’t viable as a replacement for the existing Linux audio stack, but clearly that hasn’t ended up being the case
I’ve heard nothing but good, and replacing Pulseaudio was painless. It was Pulseaudio that people hated on in my experience
When it was brand new there were some edge case bugs that broke on certain workflows and hardware, but that’s pretty much entirely fixed now and I’m guessing for a long time now it’s been more universally stable than pulseaudio was.
Also, some people just pointlessly dislike anything that’s new, or because it breaks their spacebar heating
Pipewire makes me feel like I’m a bit stupid. I keep reading about it, I read the introduction and FAQ on their website, yet I still couldn’t tell you what that thing even does. All I know is it’s a slightly less buggy drop-in replacement for pulseaudio, and pulseaudio is something I use because Firefox forces me to. (I would still be on plain old ALSA if it weren’t for Firefox.)
Also, it definitely did not “just work” for me out of the box, I had to do quite some digging and some very non-obvious stuff to get it to a) start up and b) let me use my microphone. I still don’t even know what “starting up” really means for pipewire (is there a daemon or something?), the website likes to pretend that isn’t a thing, but without doing some stuff to start it up, audio just won’t work for pulseaudio and pipewire applications…
The Arch wiki made installing it very painless for me. Zero problems. Install it, remove PA, activate systemd service.
you can install pipewire directly from archinstall now
I hope the garuda linux devs found it as easy as you. Wish they would disable the 5 second standby timer by default, but I’ll manage.
btw
Hol up, 1.0? I’ve been using it and thought it was around for few years already
In F/OSS, it is not unusual for software to stay below 1.0 version for a long time yet still get a lot of use. Just look at how long OpenSSL, for example, was at 0.9.something, while already being of crucial importance to a lot of internet infrastructure.
The reasons for this are varied, but the most important is probably simply that free software developers don’t feel the pressure to call a product 1.0 when they don’t believe it is ready to be called that.
This is the best summary I could come up with:
It has finally happened: PipeWire 1.0 has been released as this now very common software to the Linux desktop for managing audio and video streams.
With time it’s proven to be a suitable replacement to the likes of PulseAudio and JACK while pushing forward the Linux desktop with its modern design and feature set.
PipeWire 1.0 delivers improved time reporting for less jitter in ALSA when using IRQ mode, various module fixes, Bluetooth LC3 codec and compatibility improvements, improved transport and time handling for JACK, optimized buffer re-use with JACK, and a variety of other improvements.
There isn’t anything fundamentally different about PipeWire 1.0 but was part of their plan for releasing 1.0 later in the year and finally moving past all the 0.3.xx releases.
PipeWire has proven itself stable and plenty reliable for Linux desktop uses.
Downloads and more details on the big PipeWire 1.0 release via FreeDesktop.org GitLab.
The original article contains 161 words, the summary contains 150 words. Saved 7%. I’m a bot and I’m open source!
Is there something like the banana voicemeeter for pipewire?
I am currently using Helvum, which is kinda lacking a lot of the functionality.
big fan of qpwgraph
I believe a problem you may encounter asking this question is the fact pipewire does most of that itself?
lets go
Brilliant piece of software
I’ve been using PipeWire this year on my Void Linux laptop & desktop. It’s been mostly OK but has a few problems. For years I have been using plain ALSA (with no custom configuration) because pulseaudio causes me regular issues across multiple machines (mostly silently failing).
Pros:
- I don’t have to use Chromium for my mic to work on online video conf (WTF Firefox)
- “EasyEffects” lets me quickly fix crappy youtube audio (bad gain normalisation, way too much sibilance) with a minimum of effort.
Cons:
- Sometimes breaks all audio until I manually restart it (hey, just like pulseaudio. This problem never happens when using ALSA straight)
- First time setup is complicated, involving environment variables, dbus user session buses and multiple daemons (running just pipewire isn’t enough). Why can’t it handle this all itself? Surely it should notice if these things are missing and just fix it itself? Compare this to straight ALSA where you (1) do nothing and then (2) everything works (except Firefox mic support)
- I can’t have multiple audio outputs all unmuted at the same time. Eg my headphone output and my rear speaker output. If I override this (using alsamixer) then it gets forgotten next boot anyway, it seems to be out of scope of PipeWire’s understanding.
[This comment has been deleted by an automated system]
- Sometimes breaks all audio until I manually restart it (hey, just like pulseaudio. This problem never happens when using ALSA straight)
Well, how much lennart is in this thing? Not only can that predict how well it’s going to work, but also how soon it’ll be fixed, how responsive the ‘team’ will be to bug reports, how compatible it’ll be with other system components AND whether ‘compatibility’ will be achieved before the entire OS has been systematically imported into (and badly replicated by) the project.
Oh nice! I wonder if this will fix discord streaming audio?
Nope. This will only be fixed when Discord gets their head out of their ass, unlikely to happen soon.
Can you describe the issue? I don’t use Discord (and I presume the problem might depend on what browser you use).
I’m assuming this is a “dedicated app” (i.e. apt install discord). I was capable of streaming the video, but sound was a different beast. Audio streaming on discord was a no go. I was finally able to do it with pipewire and using discord-screenaudio
https://github.com/maltejur/discord-screenaudio
A custom discord client that supports streaming with audio on Linux
Jaysus, I wish this were a world where stuff like that wasn’t necessary.
Uneducated question: what’s the benefit of a dedicated client over running it in a normal browser?
Sorry for late reply. I just now noticed this.
The difference would be that a browser would likely have multiple web pages fighting for resources whereas the dedicated client would not have to fight over so many resources.
The OS has a dedicated task scheduler that alots cpu time to each process. Some processes get preferential treatment, but most processes started on user space ( i.e.double click UI icon) are just “normal” priority.
When a task scheduler hits on a process, that process can start executing whatever it needs to do. The problem with running discord in a browser is that the application is splitting its attention across multiple pages ( and probably other stuff ) instead of a single page.
Basically, it’s faster to focus on painting a single canvas than it is to painting 3 at the same time.
I’m not going to discuss shared memory and separate processes or forking. You can goggle search if you want to know more about that.
I am not so sure that it will end up faster or better.
**In theory: **A CPU scheduler should give programs as much CPU time as they want until you start nearing CPU resource saturation. Discord doesn’t need very large amounts of CPU (admittedly it’s a lot more than it should for a text chap app, but it’s still not diabolically bad). It will only start getting starved when you are highly utilising all cores. That can happen on my 2-core laptop, but I don’t have any games on my 6 core desktop that will eat everything. Nonetheless on my laptop I’d probably prefer my games take the resources (not Discord) and I’d happily suffer any reasonable drop in responsiveness of Discord as a result.
I don’t think that a new process (a new dedicated browser-client) instead of a new thread (tab in existing browser) is intrinsically faster or better. CPU schedulers are varied and complex, I wouldn’t be surprised if any differences in performance measurements would end up down in the noise. If anything the extra memory usage might cause more IO contention and memory starvation, making everything slower rather than faster. But this is all conjecture, so don’t give it much credit.
Basically, it’s faster to focus on painting a single canvas than it is to painting 3 at the same time.
I don’t think that’s much of a problem in practice, at least for Firefox: one tab can crash and stop rendering completely (or lock up 100% of 1 CPU core) but the others will keep going in other threads. For the most part they shouldn’t be able to affect each other’s performance.
In practice: What’s the actual metric that you think will be better or worse? I assume responsiveness to typing and clicks in the discord UI?
I’ve never seen discord lag or stutter from causes other than IO limitations (startup speed, network traffic, heavy IO on my machine) or silly design (having to refresh the page after leaving it open all day, I suspect it’s intentionally auto-disabling but I’m not sure). That’s not something that running a separate discord client in a separate dedicated/embedded browser will fix.
I have discord installed from the flatpak. Screen sharing works but it doesn’t share audio from the applications. Discord-screenaudio and web browser discord have been suggested to me but they don’t work with unfocused push to talk. I’ve also tried xwaylandvideobridge but that didn’t stream the audio either.
deleted by creator
deleted by creator
