PipeWire

According to Bobby, one improvement concerns jack compatibility, where developers added locking around the PortAway array and MixerList to prevent crashes, especially when applications register many audio ports.

Another notable fix in PipeWire 1.6.10 eliminates unwanted pops and clicks that could occur when unsigned audio streams finish.

The problem was caused by incorrect buffer clearing during stream draining, producing an audible burst at the end of playback.

Now, I am excited about the GStreamer integration receiving corrections to video playing strides and offsets.

Those things essentially display everything here, and I'm hiding the BlueMan icon in the SysTray so you don't see multiple Bluetooth, but it's still there just in case you do need like a deeper configuration.

Audio, mostly using like ALSA and Pipewire direct commands.

Power settings.

Again, DPMS.

So if you're just on KDE 6.8 and you're thinking, I don't have X11, X Wayland will keep you just fine.

You need Pipewire with its Pulse Audio layer or Pulse Audio itself and a Vulkan capable GPU.

Now, Valve said it's designed mainly for the Arch, Debian, and Fedora families on KDE, Plasma, and GNOME.

So if you're running a distribution that has Jack and ALSA demix only, you're going to be unsupported.

So the idea is basically that you have devices in ALSA which have certain features and characteristics, and ALSA abstracts away from the individual hardware in terms of the hardware registers, the interrupts, and all the rest of it.

On top of that, we have layers like Pulse and Pipewire,

as in

Pulse

Yeah.

No, I mean, the point I'm trying to make is basically that you have more hardware-oriented layers, and ELSA would be one of them.

And then on top of that, you have Pulse Audio and Pipewire, which essentially provide the link between ELSA and the, well, ELSA essentially, because OSS, as I said, has phone by the wayside, and there's also Jack, but ELSA, Jack, and OSS would be the three major sound systems that And Elsa is probably the most prominent one.

And Pulse in part will simply take care of providing that link between Elsa and any application sitting on top of them.

It shows up.

It connects over NetJack or PipeWire, and it gets really, really interesting real quick when we start talking about the round-trip latency.

I was made aware of this because, well, the gentleman designing this audio interface Wanted to make the latency incredibly low.

He wanted it to match that of the top-of-the-line RME audio format converter known as the RME AIO Pro, which is also the same one that you guys are hearing my voice through because it's what's in the digital audio workstation here in the studio.

Sure would be.

Also, you could do this with Pipewire and RDP, and that would also be more efficient.

It would be interesting to know exactly what they are doing.

Somebody will probably figure it out, but it's amazing they've gotten this far in some ways.

And you just plug it in, you power it on, and it boots.

All it is is Jellyfin, ready to go.

Pipewire for the audio, so the audio just freaking works.

What more do you need? Can anybody build this? Can we do this? Is there a decent Jellyfin app for Linux that we could boot to? Anyways, let us know.