Hm. I can’t really avoid a raising feeling of mistrust in the sanity of the JACK developers… (or can you possibly see any meaningful point in this behaviour?).
By the way, a question to you who surely follow the situation closer: how does PipeWire look as a potential replacement for JACK?
Looks great. Hot pluggable audio devices! Per app latency settings. Just needs a whole heap of work to stuff it in.
To stuff it into Zynthian, you mean? Or is just not fully reliable/polished/stable yet?
The reuse of the same parameter letter is logical… if you understand the logic! There are jacks parameters which include the driver (-d). The drivers then have their own list of parameters.
Pipewire is still fairly young and each time I look, it is missing features or is less performant than Jack for our use case. It does offer some attractive features but they are likely to be at a cost that could be detrimental to Zynthian performance. It aspires to replace all other audio and video high-level interfaces which is ambitious and will take time. We don’t need 90% of those features and jackd offers a stable platform with all our current required feature set.
I look forward to pipewire being appropriate for us but it is more advantageous to desktop environments.