You are here

Add new comment

rncbc's picture

IDK :(

Let me tell ya that I have zero knowledge on how this all is supposed to behave on macosx and coreaudio, because i just don't care.
But anyway, qjackctl is a UI interface to JACK, and JACK as an infrastructure only deals with JACK-aware devices and applications, period.
That said, I'm afraid I just can't help you on whether macosx/coreaudio have this or that facility for you to share or "mux" some sound, in and out, to and from the JACK sub-system--maybe there's something, maybe not, I really don't know, sorry. Perhaps, you'll need to go into another forum, one that is dedicated to the bitten-fruit corp. at least :)

Is Jamulus configured to run as JACK client application? if yes, then it should appear on the qjackctl Connections and/or Graph windows, showing that it have a couple of input ports and, on the other side, another couple of output ports. It's is at this point that you shall connect each one of the Jamulus input ports to system/capture_N, and its output-ports to system/playback_N, respectively. Only after that you can play, hear and be heard, through the sound device you are using for JACK, a Focusrite Scarlett Solo USB, right? And only after that you can go to the qjackctl Patchbay and setup a persistent connections profile, as to save you all the trouble to re-connect all this stuff again tomorrow or after... but remember, you'll always need to start JACK and launch Jamulus on your own: the Patchbay only makes the intended connections, it doesn't run ther apps for you, ever.

hth.
cheers