Re: [Jack-Devel] jackd and volume control

That's a positive last post Thomas. Really sorry that I couldn't resist posting another one, but there's been some factual misinformation in this thread, and I have a feeling that it's not been clear that it is actually misinformation. Port gain connections does not require extra memory, extra context switches, or extra CPU usage (except when applying the gain itself if connection gain is not 1.0). That's fine, we all make mistakes, but unfortunately several people just repeated these claims afterwards. I think those who just repeated these claims should search within themselves and think about why they did that. For anyone reading this later who think about maybe implementing port gain, the only things needed to do is to extend the API, add a gain array into the connection manager shared memory (well, this requires some memory, but it's not much compared to what's already there), plus modify the mixing routine. The last part seems to require a little bit work since there's some hardware optimization you either have to try match up in performance, or to just do a plain float vector addition, at least as a first step. Smoothing the gain values to avoid clicks and zipper noise would be nice too, but it's not essential as a first step. It might be slightly more complicated than this, but I'm pretty sure that's the essential steps. would be merged, but I hope we one day would move away from installing libjack and friends into the system, but that these are instead included with a controller program (for instance qjackctl), like I do for Radium on Windows, i.e that all libjack functions are weak-linked and automatically links to the libraries specified by the the controller program (i.e the controller program specify the path of the jack libraries). Then the controller program could include a client mixer and a connection GUI, plus interface to start and stop the server. This requires current clients to be recompiled though, but not only is this way much simpler for the user, I think it may also be a way to make jack more popular on windows and osx, and even linux. This way, it would also be much simpler to fork jack, and include features such as jack port connections. I wish we could have focused more on the philosophical discussion about what jack is and what it should be used for (and in a slightly less hostile tone), but it's important to get the facts right. On Fri, Mar 29, 2019 at 5:03 PM Thomas Brand <tom(a)trellis.ch> wrote: