You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently having an issue running SooperLooper as an AU plugin in Mainstage (as well as logic and as a standalone application). I have gotten to the point where the plugin is validated and I can add the plugin to a track, but when I start the GUI I get an error that says:
Connection Error
No response from SooperLooper engine process.
Please make sure that the JACK server is running.
Also check that the systems hostname resolves properly.
To my understanding, the AU plugin doesn't need JACK to run correct? I have JACK installed but its not running and I haven't used it in years. I have read some old posts about issues relating to the hostname thing but none have resolved the issue. Is there anything else I should try or is this a known issue? I am on an M1 mac, I am not sure if that is causing the issue. The same thing happens in Logic as well.
The text was updated successfully, but these errors were encountered:
Hello.
I am currently having an issue running SooperLooper as an AU plugin in Mainstage (as well as logic and as a standalone application). I have gotten to the point where the plugin is validated and I can add the plugin to a track, but when I start the GUI I get an error that says:
Connection Error
No response from SooperLooper engine process.
Please make sure that the JACK server is running.
Also check that the systems hostname resolves properly.
To my understanding, the AU plugin doesn't need JACK to run correct? I have JACK installed but its not running and I haven't used it in years. I have read some old posts about issues relating to the hostname thing but none have resolved the issue. Is there anything else I should try or is this a known issue? I am on an M1 mac, I am not sure if that is causing the issue. The same thing happens in Logic as well.
The text was updated successfully, but these errors were encountered: