SooperLooper Forum

If the midi learn shows a PC, then perhaps the device isn't really sending note like you expect? Grab the handy application Midi Monitor from http://www.snoize.com/MIDIMonitor/ and see what it really is sending! The soft step manual should be able to help you set it up.... I'm guessing you are on th...

To do a long-press your device needs to send Note On/Off events on press and release, which I assume the soft step can be configured to do. It *might* work with a momentary CC (where 127 is sent on press, and 0 is sent on release)... but I'd need to check if SL does in fact support that. Anyway, if ...

OK, try this: run the Terminal application. Then type the following command followed by enter:

ping -c 4 localhost

Does it appear to work, or does it give you an unknown host error? Run the following command:

cat /etc/hosts

And copy/paste the output here.

It isn't terminal output, it is *Console* output, which is separate utility that shows system log output (even from running GUI apps). Not sure that it will help us here, but go ahead and post any messages that appear when you start up SL.

Hmm, but after you reset the loop with Undo-all (muted or not), the act of recording a new loop pops it out of a muted state. I'm not sure I see the issue... what are you doing with the loop after you reset it?

Look for anything new that appears when you start SL, then paste it in here.

OK good, you didn't mention you wanted to monitor your input, only that you couldn't hear output I almost added the 'in mon' tip but for some reason didn't!

Be sure that Software monitoring is enabled, and that the track is either set up for input monitoring or rec-enabled.... Logic can be weird with plugins and not let them run unless it thinks there is something going on.

I don't have Logic Pro 9 to test with (I have Logic Pro X), but I had to enable Software Monitoring (in preferences->audio) in order to make the AU plugin work properly. When you record a loop, do you see activity in the output slider area as the audio loops? In addition to software monitoring, you ...

Augmenting the default loop memory should be the solution. Make it even bigger, memory is cheap and plentiful nowadays. My default of ~40 secs was set probably 10 years ago! What is happening internally, is that with each overdub (or any operation) it uses up another 7 second chunk of memory (in you...

Very strange, it always seems to start up again for me when recording a new loop, but I haven't tried with your exact setup yet.

Hmm, if you have sync to set to Loop 1 in SL (which I assume you do?).... it will start sending clock as soon as you define a new loop 1 (by starting and finishing a record). And it looks like it sends a clock Stop message if you undo that loop to the Off state. Otherwise it should send clock start ...

I haven't upgraded myself... so I won't be of much help until I do. Can you check to see if any other JACK apps (or Jack itself) have issues or have been reported to?

Or it could be a network configuration issue... what do you see when if you run the Console utility when you start jack and SL?

Yes, Undo All, which can be done by long-pressing the Undo button on a loop. This can bound to midi as well, either directly, or with a long-press of Undo (or some of the other combo record-or-overdub like commands). To do long-presses via midi you need to use a note event binding.

Could you use something like MIDI Monitor to record the exact MIDI events being received from the G2 at the time of a crash?
http://www.snoize.com/MIDIMonitor/

Then post them here, and that should help narrow it down...

[Also replied via email] Hmm, I was investigating some more and discovered it actually is working as designed. The trick to using the "in mon" is that you have to be feeding the corresponding side chain inputs with the audio you want to monitor. To get what you want in Live will involve ac...

That's correct, currently that limit with respect to the side chain audio I/O had to be set ahead of time and so I set it at 9 (main I/O + 8 sidechain I/Os for the loops). I believe in the past I tried that higher and Live didn't actually give any more ports, so it's possible there was some kind of ...

The "in mon" control should be sending it's live input through to its dedicated output but it looks like there is bug in there preventing it from doing anything. Good catch! As for slaving Live to SL's midi clock, the whole situation isn't ideal due to the currently limited way SL deals wi...

It all depends on how long you are recording and how much loop memory was allocated when you created the loop instance. If there isn't room for both parts in the preallocated memory, then only the most recently recorded loop will be available on the undo stack.

I love it when users answer their own questions

Let me know if you run into any issues...

The Jack version of SL should be a 32-bit build. I'll see if I can reproduce this here. Otherwise, it can't hurt to try a new version of JACK...

I'll take a look, if you could create a test concert that demonstrates the issue for me that would save me some time... you can email it to jesse at essej.net if you can't attach it in the forums. Thanks!

Hmm, I definitely built against wx3!

That's correct, the initial error you posted was already fixed in git back in April. That second error looks almost like some kind of wx misconfiguration... those constants have been in wx forever. I will try to build against wx2.8 here and see what happens.

That should be fixed in the git repo.... are you sure you pulled the latest when you tried it? I do need to make a new tar ball release though, once we're sure it can be built with all versions of wxWidgets..