Pipewire

Is anyone else nostalgic for 2007-tier linux? You are!? Well that's great! Red Hat principal engineer Wim Taymans has been hard at work creating a brand new linux audio subsystem! Yes, another one.
"PipeWire should be available in most distributions soon"
- pipewire.org
I, for one, simply cannot wait to repeatedly sudo vim /etc/asound.conf

Attached: redhatpls.png (869x560, 382K)

Other urls found in this thread:

blogs.gnome.org/uraeus/2017/09/19/launching-pipewire/
twitter.com/SFWRedditImages

Apparently pipewire fits somewhere in here

Attached: linux-audio-mess.png (1404x913, 276K)

obligatory

Attached: standards.png (500x283, 43K)

Attached: f9t8hF2.png (712x238, 38K)

Too lazy to find it again, but I found a blog somewhere from a RedHat developer apologizing for PusleAudio and saying it's not gonna be like that again this time. Fingers crossed they're not bullshitting.

I'd like to see that
Poettering has only ever deflected blame for PulseAudio not working onto drivers, distributions and audio clients

Thank God. Pulseaudio is still shit. I don't know why people said it got good. I have never had a single computer where it worked right.

Is there any reason why they couldn't replace pulseaudio with pipewire and call it pulseaudio? These were both Redhat projects, were they not? Has the name pulseaudio been stained so completely that they had to distance themselves from it?

The problem here is that certain projects have become dependent on Pulse. For example, Firefox recently dropped ALSA support and now uses Pulse exclusively. This means to avoid breakage PulseAudio will either:
- Have to run alongside Pipewire
- Implement a legacy-mode PulseAudio interface (kind of like how PulseAudio mimics ALSA)
Either way the Linux audio mess is going to grow larger. Again.

blogs.gnome.org/uraeus/2017/09/19/launching-pipewire/
>So after multiple years of development we are now landing Pipewire in Fedora Workstation 27. This initial version is video only as that is the most urgent thing we need supported for Flatpaks and Wayland. So audio is completely unaffected by this for now and rolling that out will require quite a bit of work as we do not want to risk breaking audio on your system as a result of this change. We know that for many the original rollout of PulseAudio was painful and we do not want a repeat of that history.

>redhat
stpped reading right there

these graphs are always funny, they make the interactions seem purposefully more complicated than things actually are.

the only things in the graph you have to worry about, for your average linux install, are the actual output device, alsa being an interface to that hardware, and pulseaudio using alsa and bluez to expose volume controls and other audio stuff to userspace.

Shhh someone can't throw a tantrum about their edge case hardware not working perfectly if they don't obfuscate the data they're presenting!

Just look at all of the "look at these things that systemd can do (but is never actually compiled with)", or the xorg bitching about features that were cut over a decade ago.

Open source is great, open source retards online can sometimes not be so great.

windows will always be better for v/a and games because the software that produces it in the first place runs on windows.

What?

>last updated a decade ago
>has things like fucking aRts on it

-- also, holy fuck 2008 was a decade ago?!

>PipeWire is Free Software and is developed in the open. It was created by Wim Taymans, Principal Engineer at Red Hat and co-creator of the GStreamer multimedia framework.
did anything actually use gstreamer?

Every media player in gnome, plus a couple of other shitty ones.

>gnome
so nothing important

>it's a brainlet tries to understand something once again

Pipewire is specifically for remote video and audio it isn't trying to replace the "audio stack" which is pulse audio on top of alsa.
Alsa actually handles all of the basic audio stuff and Pulse still depends on it but you can actually use Alsa on it's own.

Pulse's only ability is really that it adds network based routing of audio on top of alsas featureset.

Pipewire is specifically meant for a wayland standard (not Xorg) remote protocol.
Just like wlroots and Mir and becoming standard wayland libraries and a compositor.

Pipewire itself won't be useful till desktops and WM's adopt it.
Gnome and Sway already have it in mind and I think KDE is adopting it too.
This doesn't displace PulseAudio though and even if it did PulseAudio and pulse.d are potterware crapfests with horrible latency.

KYS moral outrage OP.

you can actually still compile it for alsa, it's just that distro maintainers compile it to pulse because of systemd faggotry.

If you don't want to compile programs for ALSA you can install 'apulse' the pulse emulator for ALSA.

JACK can be used for audio networking on top of apulse or ALSA