Audio can already be connected in or out as a JACK client, and MIDI using real or virtual ALSA MIDI devices.pljones wrote:The point of being a JACK server would be that anything in the JACK universe could then connect in or out to MusiKernel
That idea definitely has merit. There are 2 paths that could be taken there:pljones wrote:whilst the user doesn't have to worry about getting JACK working.
1. Re-implement the JACK API from scratch
2. Auto-start the original jackd if not already running
A lot of the problem with QJackCtl is that it exposes 1,000,000 different settings to the user. If I wrote a similar application, it would hide most of those and try multiple times to start jackd, intelligently tweaking different settings until it landed on a combination that works (rather than leaving the process of elimination to getting working settings as an exercise to the user).
But then, there's the whole jack1 vs. jack2 fiasco, I'm not sure which distros have finished reverse-deprecating jack2 and reverse-upgrading to jack1.
That's a good point. I look into it, thanks.pljones wrote:There's always a time when virtual audio (or MIDI) cabling becomes useful, which is why Reaper provides ReaRoute. (Given jackd can also use PortAudio, I don't see that as an issue.)