SooperLooper Forum

Ah yes, this is a bug in 1.6.18 I tested the workaround I mentioned on OSX and realised it only works on Linux. The way to do it on OSX is to open a terminal cd into the .app directory. Start SooperLooper and then SLGUI: $ ./sooperlooper & $ ./slgui -N -H $(hostname) You should then have the nor...

Is this for SooperLooper stand-alone? What happens when you try and load something? There is a bit of a bug in 1.6.18 where it doesn't realize that SooperLooper is on the same machine. The workaround would be starting SLGUI using:

Does this problem presist alasdairc? Looks a bit like you had a zombie process, maybe due to the suspend.

Did you see the Pigtronix Infinity which was debuted at NAMM this year? It is only two simultaneous loops but the second can up to six times the length of the first. It looks like it has MIDI in too. No word on price yet though. SooperLooper is inspired by Echoplex Digital Pro (EDP) LoopIII and Loop...

Could you give more details about your setup? Where does SooperLooper come in to it? What is your computer and your audio interface?

OK, I have done a few more. I am a bit stuck with the record_or_overdub_solo_trig and record_overdub_end_solo_trig as to me they don't seem to do anything beyond their non-trig counterparts. They don't seem to trigger the loop or anything. Anyone use these and care to explain?

Could you give more details?

- What platform are you on?
- Are you using Sooperlooper stand-alone or AU?
- What exactly happens when you try and change pitch or stretch?
- Could you post the terminal output?

I guess this reply is a bit late but your sooperlooper installation should come with an executable called slconsole. Which, although not ncurses based, allows you to control sooperlooper from the command line.

I see. But later this is changed to 127.0.0.1 anyway in loop_control.cpp line 317: if (_spawn_config.host == "127.0.0.1" || _spawn_config.host == "localhost") { char tmpbuf[100]; snprintf (tmpbuf, sizeof(tmpbuf), "osc.udp://127.0.0.1:%d/", _our_port); _our_url = tmpbuf;...

I had this issue as well. Removing the ~/.sooperlooper will not fix it. Using the -H flag is indeed a workaround. $ slgui -H `hostname` Meanwhile, I tracked down the bug in the code and fixed it. Unless there was a good reason to hard set the host to "localhost" at that point. Index: src/g...

Ok, thanks for the encouragement Jesse. I am just going to start going through these from the top. First I am changing the mute description slightly to: [cmd] mute Press to mute loop output, press again to un-mute. Dry passthough audio will be unaffected. To continue playing the loop from the top pr...

I have started making a full midi command reference page. So far I have managed to generate a html page which fits into the existing SooperLooper docs style wise and contains all bindable commands. They are mostly stubs though as I have mostly just copied descriptions accross from the GUI command re...

I meant the features that are planned to be worked on. Would like to take a look really, see if I can help out by submitting patches. Same goes for bugs really but I guess the bugs forum would be good enough.

Is there a public list of accepted feature requests?

Ah yes I see. That will do for me I guess and I can still toggle "quantize mute" to get back to the regular mute functionality. It doesn't seem to affect anything else I am doing for the minute as I haven't been using the quantize features.

When it is actively looping I wouldn't want "once" to "trigger" the loop again but just play it to the end and then mute or stop. When I set "quantize to loop" and "mute quantize" it doesn't seem to do what I want but still "triggers" the loop to sta...

From my LINE-6 delay/looper pedal I have gotten used to the "once" button playing to the end of the loop and stopping without restarting the loop when you press it. The one_shot command in SL seems to restart the loop each time you press it. I would like to request either another command t...