SooperLooper Forum

Hi guys Has anyone else found that when slaving Ableton's tempo to SL (running as an AU inside Ableton) the audio gets really glitchy as Ableton's tempo fluctuates? I think it is because Ableton runs tempo with 2 floating points (eg. 127.45bpm) while SL is sending a tempo with only 1 floating point ...

Ok figured it out! Saw this post from Jesse: viewtopic.php?f=17&t=1290
The message needs a -2 in it, so becomes /sl/-2/set selected_loop_num 0 (or 1, or 2 etc)
Great! Thanks for your help.

Hmmm can't seem to make an OSC message do it. Tried the message: /sl/set sf selected_loop_num 0.0 but nothing happens.
Also tried /sl/set selected_loop_num 1.0
Still nothing.
I wonder is there a glitch in the OSC engine regarding this?
Thanks a million for your help. Would love to get this working.

Hi Kasbah
Thanks for the reply, can you clarify how do I set a target range in the OSC message?
Or is that only applicable to midi?
Justin

Hi Jesse
I'm setting up Pure Data patch to send OSC commands to control SooperLooper. Is there a way I can send OSC messages to 'select_loop_1' and 'select_loop_2' as I can with key bindings 1 and 4?
This would sort out my home-made foot controller!
Thanks a million
Justin

Hi Jesse Thanks for building such a powerful bit of software. I'm just discovering what it can do. Here's my problem. I'm sending audio into SL as a vst~ object in Max/Msp which I then want to output the audio from 3 separate loops into different output lines to be processed separately. However even...