[Rosegarden-user] sooperlooper

[steve c. <ste...@gm...>]

Thanks for responding to such an arguably off topic question. After a
bit of tinkering around I have managed to figure things out, mostly.

I am trying to use Rosegarden to control SooperLooper in order to
automate a variety of tasks, thereby freeing my hands from the mouse
and putting them back on my guitar where they belong.

So far I have managed to assign midi binding to the more basic commands.

Pretty straight forward, really. Just go to SL's session->properties
dialog and select the MIDI Bindings tab. Assign events to notes and
then make an RG file containing these notes.

However, I am a bit stymied trying to set up a pitch_shift binding.

When I try to create such a binding in the midi binding tab of the
preferences dialog, I see the target range showing -12 to +12 as I
would expect, but I'm kind of confused by data range options.

Obviously 128 doesn't divide evenly by 25, so I'm guessing I should
limit the range to something that does - say from 88 to 112.

When I do this I get the following line in my .slb file:

0 n 74  set pitch_shift 0  -12 12  norm 88 112


But then where does the data come from? These control events show up
in RG as plain old notes. So the only "data" they're packing is the
velocity.

So I set up and RG file where the are a bunch of note 74 type events
and I give them velocities somewhere in the range of 88 to 112.
(Fortunately for me, 100 is the default velocity for a new note in RG,
which corresponds to a pitch_shift of 0).

Much to my surprise this almost works as expected. The only problem is
that as soon as the notes end, the pitch_shift reverts to the
unhelpful default of -12. This is easily corrected by changing the
event type from "note" to "note on" in the midi event panel at the
bottom right of the midi bindings tab. Why it defaults to -12 is a bit
puzzling though.

One minor glitch is that pitch shifting the loop to which SL is
synching will cause other loops to fail to trigger, so don't do that.