I've been contemplating trying out Pipewire as a replacement
for Jack. What is holding me back is a what seems to be a
serious lack of information. I'm not prepared to spend a lot
of time and risk breaking a perfectly working system just to
find out that it was a bad idea from the start. So I have a
lot of questions which maybe some of you reading this can
answer. Thanks in advance for all useful information.
A first thing to consider is that I actually *like* the
separation of the 'desktop' and 'pro audio' worlds that
using Jack provides. I don't want the former to interfere
(or just be able to do so) with the latter. Even so, it may
be useful in some cases to route e.g. browser audio or a
video conference to the Jack world. So the ideal solution
for me would be the have Pipewire as a Jack client.
So first question:
Q1. Is that still possible ? If not, why not ?
If the answer is no, then all of the following become
Q2. Does Pipewire as a Jack replacement work, in a reliable
way , in real-life conditions, with tens of clients,
each maybe having up to a hundred ports ?
Q3. What overhead (memory, CPU) is incurred for such large
systems, compared to plain old Jack ?
A key feature of Jack is that all clients share a common idea
of what a 'period' is, including its timing. In particular
the information provided by jack_get_cycle_times(), which is
basically the state of the DLL and identical for all clients
in any particular period. Now if Pipewire allows (non-Jack)
clients with arbitrary periods (and even sample rates)
Q4. Where is the DLL and what does it lock to when Pipewire
is emulating Jack ?
Q5. Do all Jack clients see the same (and correct) info
regarding the state of the DLL in all cases ?
The only way I can see this being OK would be that the Jack
emulation is not just a collection of Pipewire clients which
happen to have compatible parameters, but actually a dedicated
subsystem that operates almost independently of what the rest
of Pipewire is up to. Which in turn means that having Pipewire
as a Jack client would be the simpler (and hence preferred)
 which means I won't fall flat on my face in front of
a customer or a concert audience because of some software
not posting to any of LA* mailing lists often in the last years, but today I thought
I should make an exception to point out that it's now exactly 20 years ago that the
first Linux Audio Conference or "LAC" for short (then still called "Linux Audio
Developer's Meeting") took place at the ZKM in Karlsruhe, Germany.
Wow, 20 years come and gone so quickly! It's great to see a couple of "early
adopters" are still around today here, and many new names have entered the scene
in the meantime and left/leave a lasting footprint in it.
As a quick "trip down memory lane", here's a short list of things that happened back then:
- Takashi Iwai dove into the innards of an ALSA driver
- Fernando Lopez-Lezcano introduced the PlanetCCRMA distribution, based on Fedora
- Steve Harris explained the concept of a Bode frequency shifter as a LADSPA plugin
- Paul Davis held the keynote, AND spoke about JACK, AND shared his experience of writing
a DAW that is at the forefront of free, open-source and cross-platform DAWs today.
- Dave Philipps looked at the historic development of Linux audio, from OSS to ALSA and beyond
- Jörn Nettingsmeier managed to get the audio part of the presentations both recorded AND live-streamed
at a time when "streaming" was still a term unknown to most of us.
- The term "Linux Sound Night" already existed, but was..perhaps not as musical yet as you might have expected :-).
- And, we also learned that schedules are not easy to keep - I believe after the first day we
ran some >2 hours late, and people begin to STARVE.
- Posing in front of the ZKM "Kubus": https://linuxaudio.de/LAC2003_Posse.jpg
For some more memories, see also http://lac.linuxaudio.org/2003/zkm/
Of course, on the downside it has to be noted that Corona has impacted us too -
after an almost perfect track record of conferences or mini-conferences every year,
2021 and 2022 didn't see any event happening. There is a certain risk now that it
won't recover, but that's in our hands to change (sidenote: I have talked to my
contacts at ZKM here in Karlsruhe in January, but they are unable to finance and/or
organize an event of this size at the moment - certainly somewhat influenced by
current economics, but I am hearing ZKM has actually reduced their headcount quite
a bit, and after the recent passing of its artistic-scientific chairman, Peter
Weibel, it will have to be seen how his successor, Alistair Hudson, will steer
it into the future).
Whatever LAC's future will be, free and open-source audio software is certainly
flourishing, and will continue to do so. It just would be soo nice to enjoy the
results together with real, tangible people :-\.
If anyone sees an option for hosting a future LAC, lac-team(a)lists.linuxaudio.org
is willing to listen to proposals you might have (or just discuss it right here).
Well, the heck - there is no steering committee or anything in place, so I guess
the first one brave enough to say "I think we can do it" will get the job :-).
I am forever grateful to all the folks who have enriched and continue to enrich
our open-source audio life by writing or presenting software, creating
documentation and tutorials, hosting (AND attending) conferences like the LAC,
and whatever else helps to keep the penguin dancing!
figuring out the syntax for c++20 concepts I run into challenges. With a two
parameter template concept like swappable_with or convertible_to is it always
necessary to use a requires statement like this:
void f(T t) ...
With single parameter concepts like integral a syntax like this will work:
void f(T t)...
Also with single parameter concepts a statement like this should work:
std::integral auto my_variable;
Will that work with a two parameter concept like the above convertible_to? I
haven't seen/found a syntax which does it.
Any help is appreciated, definitely including a good read that WILL
demonstrate or demystify these things.
* Website: http://juliencoder.de - for summer is a state of sound
* Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g
* Audiobombs: https://www.audiobombs.com/users/jeanette_c
* GitHub: https://github.com/jeanette-c
Don't care about money
It doesn't give me half the thrill <3
a story to continue. I'll release a second block of video tutorials
about LV2 plugin programming from the scratch. For everybody who wants
to make his/her own plugins. This time about graphical user interfaces.
I'll show you:
* the LV2 way to go, with turtle and C/C++,
* toolkits and the pitfalls,
* some of the toolkits we can use, and
* finally how to make UIs for the plugins we made before.
Every Friday, for the next some 10 weeks. Starting with this
announcement video: https://youtu.be/7mCLDBBXajU
See you on Friday