Linux standalone is frozen on CONNECT TO GROUP, but never connects

[chaseology]

Linux STANDalone will not actually - CONNECT TO GROUP - (any group)... and keeps repeating the message in terminal "aoo_client: already connecting!" when clicking on CONNECT TO GROUP again...just sits there without going to the next screen, waiting for others to connect...etc...

OS = LUBUNTU 18.04 64 BIT USING jack audio connecting kit

[essej]

This symptom can happen when there is something wrong with the audio processing, as if the audio callback isn't being called by the audio system. Can you try with a different JACK configuration, or perhaps by switching to ALSA in SonoBus's audio setup? Did you ever see a sonobus jack client show up in there (whichever tool you are using to look at JACK routing)?

[chaseology]

Thank you for your reply... I had to bring up the AUDIO SETTINGS 1st before clicking on CONNECT..and click on something inside this box AND wire up in the JACK CONNECTION BAY the output of the GUI to the sound card gui...if there was no wiring, inside the jack audio connection bay...it would not CONNECT TO GROUP...so the WIRES had to connected first...or at least one wire... so CLICK once somwhere in the settings box, the the GUI would appear inside JACK AUDIO CONNECTION bay...then go to the jack audio connection bay and wire up at least one connection from output to input or input to output and only then... would CONNECT TO GROUP

[essej]

So after that you were able to get it all working? I believe you could also check those input and output channels to do the jack connection routing as well (for instance select capture_1 in Active Input Channels, and playback_1 and playback_2 in Active output channels). But thanks for the feedback, that I need to add some helpful text to make sure people go to Setup Audio at least the first time they use the app (it should save the most recent settings on future launches)

[chaseology]

I tried to use the SonoBus AUDIO SETTINGs to click INPUTs / outputs, but it would not do anything on either...so i had to do everything inside the jack connection bay...and also noticed that the OUTPUT PINS of the SONObus JACK GUI, must be connected to the sound card GUI PINS or it does not work...so at all times...it seems...that the JACK standalone version must be connected to the Jack soundcard GUI pins at all times...