On 3/25/07, Paul Sobczak <sobczak.paul@...> wrote:
> I can tell you that the record function did not care if it was a note value
> (velocity did not matter, I used several different velocities) or a CC
> value. All of the other functions on the MIDI bindings worked, well.
>
> A fix would be great as the record and the overdub functions are of the
> greatest importance as you well know. This is kinda
I cannot reproduce this, are you running SL standalone? Using Midi
Patchbay without any weird options? What else should I know about
your system, OS version, hardware, etc?
jlc

It would be nice with a way to record n length of loop k, instead of
stopping it by using the record button?
F.ex, set it up to only record one length of loop 1.
--
Esben Stien is b0ef@... s a
http://www. s t n m
irc://irc. b - i . e/%23contact
sip:b0ef@ e e
jid:b0ef@ n n

I don't have a screen shot of the MIDI bindings, sorry.
I can tell you that the record function did not care if it was a note value
(velocity did not matter, I used several different velocities) or a CC
value. All of the other functions on the MIDI bindings worked, well.
A fix would be great as the record and the overdub functions are of the
greatest importance as you well know. This is kinda
I am not sure if this will appear in the correct place as I have not been
sent any emails back from this account concerning the replies to my topic.
Thank you for your time.
Paul
On 3/7/07, Paul Sobczak <sobczak.paul@...> wrote:
>
> I have a M-Audio Ozone and I am using it as the audio i/o as well as the
> Midi interface with my macbook.
>
> I have installed all of the midi program and I can get Sooperlooper to
> reconize the midi I send,...... sometimes.
>
> The problem I am having is that the midi binding will never initiate the
> overdub function, it just doesn't ever go in to that mode I have tried using
> a note value and also a #cc to control it, to no avail.
>
> also when controlling using midi, not all the functions work properly:
> for example I record a loop, then mess around with it, then hit record
> again to work or a new loop, and nothing happens, no response at all.
>
> It seems like sooperlooper is seeing my midi events, but not responding to
> them, what could be the problem?
>
> Paul
>

On 3/20/07, Joel Cherney <joel.cherney@...> wrote:
> > /register_update tap_tempo CALLBACK_URL CALLBACK_PATH
>
> Yup, this is what I was looking for, I think. Much better than
> converting seconds to 96ths, and having a Record button on my
> footcontroller that is also a global restart for my collaborator's
> rig. I'll see if I can get it to work... Thanks, Jesse.
Just a warning, I really don't know if it will be precise enough for
you... as currently it is only used to update the GUI tap tempo
button. But try something anyway.
jlc

> The more elegant way was if I implemented midi clock output!
I can't argue with that! It seems pretty low-priority to me,
> Unfortunately I doubt that will happen any time soon enough for you to
> use it. Another possibility is to register for the OSC global
> tap_tempo control, which is sent out every 8th.
> /register_update tap_tempo CALLBACK_URL CALLBACK_PATH
Yup, this is what I was looking for, I think. Much better than
converting seconds to 96ths, and having a Record button on my
footcontroller that is also a global restart for my collaborator's
rig. I'll see if I can get it to work... Thanks, Jesse.

On 3/20/07, Joel Cherney <joel@...> wrote:
> I'm preparing to perform a set with another electronic musician, and I
> was trying to figure out how to get my collaborator's sequencers and
> delays to sync with my looper. It's easy enough if I want to sync
> SooperLooper to an external midi sync source, but I haven't yet found
> a way to send information in the other direction. I scanned the OSC
> implementation, and I suppose that I could use Plogue Bidule to get
> the loop length in seconds, convert it, and use it as a variable in a
> midi clock. Is there any more elegant way to do this?
The more elegant way was if I implemented midi clock output!
Unfortunately I doubt that will happen any time soon enough for you to
use it. Another possibility is to register for the OSC global
tap_tempo control, which is sent out every 8th.
/register_update tap_tempo CALLBACK_URL CALLBACK_PATH
jlc

I'm preparing to perform a set with another electronic musician, and I
was trying to figure out how to get my collaborator's sequencers and
delays to sync with my looper. It's easy enough if I want to sync
SooperLooper to an external midi sync source, but I haven't yet found
a way to send information in the other direction. I scanned the OSC
implementation, and I suppose that I could use Plogue Bidule to get
the loop length in seconds, convert it, and use it as a variable in a
midi clock. Is there any more elegant way to do this?

Can you send me (offlist) a screenshot of your MIDI bindings preferences tab?
I wonder why this issue is just coming up, I hadn't heard that this
was a problem in some cases until a few months ago.
When I get a chance I will do some more testing to see if I can
reproduce it. Do you know by chance what velocity/level your note/cc
events are sending?
jlc
On 3/7/07, Paul Sobczak <sobczak.paul@...> wrote:
> I have a M-Audio Ozone and I am using it as the audio i/o as well as the
> Midi interface with my macbook.
>
> I have installed all of the midi program and I can get Sooperlooper to
> reconize the midi I send,...... sometimes.
>
> The problem I am having is that the midi binding will never initiate the
> overdub function, it just doesn't ever go in to that mode I have tried using
> a note value and also a #cc to control it, to no avail.
>
> also when controlling using midi, not all the functions work properly:
> for example I record a loop, then mess around with it, then hit record again
> to work or a new loop, and nothing happens, no response at all.

Paul,
I'm experiencing exactly the same problem using Logic Pro as the AU host
and MOTU 828mkII as the MIDI interface.
What I've found is that Program Change messages work in all cases I've
tried, while the note and CC messages get ignored by SL in some
situations. (e.g. once you create a loop, future Record messages are
ignored if they're note or CC)
With Logic Pro, I can work around this problem by using Logic to
translate all my CC messages into PC messages, since the PC messages are
received properly by SL. (You got all those abbreviations, right ? :-)
James
james@...
On Wed, 7 Mar 2007 13:13:43 -0600, "Paul Sobczak"
<sobczak.paul@...> said:
> I have a M-Audio Ozone and I am using it as the audio i/o as well as the
> Midi interface with my macbook.
>
> I have installed all of the midi program and I can get Sooperlooper to
> reconize the midi I send,...... sometimes.
>
> The problem I am having is that the midi binding will never initiate the
> overdub function, it just doesn't ever go in to that mode I have tried
> using
> a note value and also a #cc to control it, to no avail.
>
> also when controlling using midi, not all the functions work properly:
> for example I record a loop, then mess around with it, then hit record
> again
> to work or a new loop, and nothing happens, no response at all.
>
> It seems like sooperlooper is seeing my midi events, but not responding
> to
> them, what could be the problem?
>
> Paul

I have a M-Audio Ozone and I am using it as the audio i/o as well as the
Midi interface with my macbook.
I have installed all of the midi program and I can get Sooperlooper to
reconize the midi I send,...... sometimes.
The problem I am having is that the midi binding will never initiate the
overdub function, it just doesn't ever go in to that mode I have tried using
a note value and also a #cc to control it, to no avail.
also when controlling using midi, not all the functions work properly:
for example I record a loop, then mess around with it, then hit record again
to work or a new loop, and nothing happens, no response at all.
It seems like sooperlooper is seeing my midi events, but not responding to
them, what could be the problem?
Paul

Hello all,
Applescript newbie question here. Perhaps someone can help.
There's a nice Autostart script for Jack OSX (go to http://
jackosx.com/ and click download). I'd like to extend it so that it
does all the necessary things to get SooperLooper going on my setup.
This includes starting the four programs I need: Jack, MIDI patchbay,
Logic and SooperLooper; and making these programs load their required
files. For SooperLooper this would be the studio setup file.
Staring MIDI patchbay and SooperLooper was easy, I just added the lines
tell application "SooperLooper" to run
tell application "MIDI Patchbay" to run
to the script.
Is it possible to load the setup files to these programs
automatically too? I see that the Autostart script can "click a
button" in a Jack pilot window, but to load a setup file it needs to
select an item from the menu.
Ingo