Sooperlooper GUI cannot connect

[shirazd]

I am using SooperLooper as an AU plugin in Reaper. It used to work fine for me, but something over the last eight months or so changed that.

In the screenshot below, in the preferences window, when I enter the host and port, I can get it to say "Connected" but the GUI text continues to say "Not Connected".

Then about 20 seconds later the Preferences window too switches back to "Not Connected" and this popup window comes up:

I don't think it ever connects (false positive on the initial connection).

This used to work fine.

I watched Mac's console while doing trying to start and stop the connection but it didn't seem to be logging anything.

Is there anything else I can check? Is there any kind of error logging? Or any suggested things to check generally?

Again this worked, and then stopped working sometime within the last 8 months or so.

Any help greatly appreciated.

This is literally the only plugin I could find to emulate a guitar foot pedal that works in 2022.

Shiraz

[shirazd]

ps. @ dev ... if I can get this working again I'm gonna slip you a $20. I promise I'm not trying to buy your support, I would have done it anyhow!

[SagePbbbt]

Similar issue.

The engine seems working fine. It appears as it should in the JACK graph, but the GUI and the engine aren't staying connected. The GUI sends a ping and the engine responds to it, but nothing more happens beyond that.

Been using SooperLooper for years. Worked until a couple of months ago. Have reinstalled Jack, SooperLooper, even did a fresh OS install. Help would be much appreciated!

[shirazd]

Yes mine stopped working in my estimate a few months ago. (I used it successfully as recently as 6 months ago, but that's an estimate).

Noting that I don't use Jack myself. I use it as a plugin in my DAW, Reaper.

[essej]

Ugh, this is related to networking configuration on your machine... and it has been a long-time issue with how the OSC comms works internally in SL, and how it interacts with your network configuration in annoying ways. What does your /etc/hosts file look like (easiest is to view that from Terminal, with 'cat /etc/hosts')?

[SagePbbbt]

Thanks for responding! I actually installed al linux partition JUST for using sooperlooper (I love it, haven't found anything as good). But getting it working on Mac OS would be good. But here's the /etc/hosts info:

127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost

[shirazd]

thanks for your response!

i am a web dev, so my hosts file is as follows:

# This entry was appended by Docker Desktop because `localhost` did not resolve
# to a list of addresses which included 127.0.0.1. This can happen due to a bug
# in the macOS migration assistant, or possibly because another tool has
# corrupted the file.
127.0.0.1	localhost
# End of the section appended by Docker Desktop
# Added by Docker Desktop
# To allow the same kube context to work on the host and the container:
127.0.0.1 kubernetes.docker.internal
# End of section

127.0.0.1 lri
127.0.0.1 voicesoftheland
127.0.0.1 ewa
127.0.0.1 bookshare
127.0.0.1 rnibbookshare
127.0.0.1 ws-mukurtu
127.0.0.1 mukurtu-alt
127.0.0.1 mukurtu-pantheon
127.0.0.1 nytraditions
127.0.0.1 sipnuuk


192.168.68.135 openmediavault # thinkpad ethernet

[soulflyer]

@shirazd @SagePbbbt @essej did you ever find a way round this? I still get the same problem...

[SagePbbbt]

I did not. I now have a linux partition on my mac just for running sooperlooper which is ridiculous. but I love sooperlooper, and i reinstalled mac os and all software and I still couldn't resolve this. - Sage

…

On Tue, 25 Feb 2025 at 20:15, Iain ***@***.***> wrote: @shirazd <https://github.com/shirazd> @SagePbbbt <https://github.com/SagePbbbt> @essej <https://github.com/essej> did you ever find a way round this? I still get the same problem... — Reply to this email directly, view it on GitHub <#43 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A37H53LHKF3MRLOWTEBZNXT2RRNEHAVCNFSM6AAAAABX2PPAV2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBRG43DGMZUGM> . You are receiving this because you were mentioned.Message ID: ***@***.***> [image: soulflyer]*soulflyer* left a comment (essej/sooperlooper#43) <#43 (comment)> @shirazd <https://github.com/shirazd> @SagePbbbt <https://github.com/SagePbbbt> @essej <https://github.com/essej> did you ever find a way round this? I still get the same problem... — Reply to this email directly, view it on GitHub <#43 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A37H53LHKF3MRLOWTEBZNXT2RRNEHAVCNFSM6AAAAABX2PPAV2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBRG43DGMZUGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[soulflyer]

Thanks Sage. I'm kinda stuck with Mac atm, and it's an m1 so running linux on it is not a viable option. The recently resurrected MOBIUS seems to be a workable alternative for now though.

[shirazd]

@soulflyer I never did solve it. I ended up switching to this:

https://www.meldaproduction.com/MSuperLooper

The name similarity is just a coincidence as far as I can tell.

It works without issue in Reaper, on my M1 Macbook which is on the latest MacOS version.

It's a solid, well featured plugin that I've sadly barely used as I just haven't had as much time for making music. I have a midi foot buttons controller mapped to the buttons, as I play guitar. It's basically a very well featured live looper, equivalent to pricey hardware ones.