PipeWire 1.0 RC Available With Jackdbus By Default, Improved IRQ-Based Scheduling

[phoronix]

Phoronix: PipeWire 1.0 RC Available With Jackdbus By Default, Improved IRQ-Based Scheduling

PipeWire 0.3.81 was released today for what's being treated as the PipeWire 1.0 release candidate ahead of its stable release still comimg up this calendar year...

https://www.phoronix.com/news/PipeWire-1.0-RC

[tildearrow]

PipeWire is now able to match the JACK audio server and have equal latency to PipeWire with the professional audio profile.

Equal latency to itself?

[dammarin]

Equal latency to itself?

Well, that's certainly true, though hardly worth writing about.

[Azpegath]

Did the configuration file syntax file changes make it into this? They were redefining that from one standard to another a while back? The lua to json porting?

Edit: Turns out that was Wireplumber, see post below.

[Kver]

Equal latency to itself?

They mean equal latency between the default profile and the pro audio profile. Pro Audio is more complicated to deal with, but unlocks raw input/output channels so you can use complex mixers and directly interface with audio devices. The default profile hides that complexity for traditional setups. I guess the default logic might have caused some latency, which was bypassed by pro audio.

This just means there's not a latency penalty for us common folk who aren't connecting to raw interfaces, and no more reason to use pro audio profiles for performance - if you noticed it.

[avis]

Did the configuration file syntax file changes make it into this? They were redefining that from one standard to another a while back? Like json to something else.

PW strives to be 100% config file compatible with PA. I've not heard about any syntax file changes.

[unwind-protect]

So is thingie actually any good?

Can I run a setup where every client is jack und everything goes through Jamin just like with plain jackd? Does qjackctl work? Do commandline utilities for changing connections work?

[Azpegath]

PW strives to be 100% config file compatible with PA. I've not heard about any syntax file changes.

Michael wrote about it a while back.

Edit: This is the blog post I'm thinking of.

https://www.collabora.com/news-and-blog/blog/2022/10/27/from-lua-to-json-refactoring-wireplumber-configuration-system/

It was related to wireplumber and not specifically pipewire. It is targeted for the Wireplumber 0.5 release, which is not ready yet.
The roadmap can be seen here:

https://gitlab.freedesktop.org/pipewire/wireplumber/-/wikis/0.5-release

[avis]

Michael wrote about it a while back.

If you're really interested, you open PW's git repo and see for yourself. It's not that difficult.

PipeWire's configuration file format is JSON. In addition to true JSON
PipeWire also understands a more compact JSON representation. Where
`"` can be omitted around strings, no trailing commas are required and
`:` or `=` can be used to separate object keys from their values.

[Azpegath]

If you're really interested, you open PW's git repo and see for yourself. It's not that difficult.

Thank you for your input.