Re: Mobius Scripting question...

[Robert Craig Thomas <robert@robertcthomas.com>]

Per, thanks for the detailed answers, very very much appreciated.

What you mentioned here I've discovered by accident, but I wasn't (and still am not sure) how to control it...

"Oh, I just remembered another thing with Multiply that may be  confusing if your not aware of it: If you go NextLoop and then give a
Multiply command in the lame-duck-period the audio of the first Loop  will be copied into the new loop. Can be quite useful."

Actually, I'm only using the NextLoop and NextTrack Multiply commands after I've recorded my first Loop (usually 2 or 4 bars of a basic rhythm), so the base-time stays within multiples of the initial base-loop (Track / Sync Settings are all set to Track/Loop).  

But I prefer Multiply to the simple Record command (even though both function the same way once the base-loop-size is set) because with Multiply it's easier to see how many Loop-cycles I've used as I record (having a mouth-open Pacman circle rather than just having the steady red dot).

Anyway, I wonder how many other mysterious but important things I still need to know (like the Wait Loop) command.. I hope not too many... ;-)

Thanks again,

Bob Thomas

On Fri, Feb 12, 2016 at 4:41 PM, Per Boysen <perboysen@gmail.com> wrote:

On Fri, Feb 12, 2016 at 4:10 PM, Robert Craig Thomas
<robert@robertcthomas.com> wrote:
> re: NextLoop + Multiply ... I've discovered that I need to use "Wait Loop"
> when I want to use "NextLoop" + "Multiply" in a script...

Yep, "Wait Loop" an underestimated line :-)

> for some reason
> Mobius waits automatically when reading a script "NextLoop" + "Record"

I suppose that reason has to do with the globally set SwitchQuant
setting? If a command typically waits for a SwitchQuant cusp to kick
does so no matter if triggered from a MIDI pedal, an on-screen button
or a script.

BTW, why do you want to throw a Record when arriving into a new loop?
Record also erases the global tempo in case you by mistake give it
when on the master track (the track you created the first loop on)
with only one loop. I personally prefer to set the global pref's for
Time Copy to create a new loop of one cycle's length in Multiply mode.
Then you can just start adding new audio to loop #2 on the track,
safely knowing that the length of the loop will keep multiplying, by
adding one cycle, until you give a Multiply command to set the new
loop length and stop overdubbing.

Oh, I just remembered another thing with Multiply that may be
confusing if your not aware of it: If you go NextLoop and then give a
Multiply command in the lame-duck-period the audio of the first loop
will be copied into the new loop. Can be quite useful.

A good way to get a hang of scripting is to search out forum threads
for the looping maneuvers you are interested in and simply copy
scripts other users have posted on the forum. Then you can make
changes to the scripts and learn on the way.

Greetings from Sweden

Per Boysen
www.perboysen.com
http://www.youtube.com/perboysen

--

Robert C Thomas, Gütersloh, Germany
Handy 0176 504 36157 - Home 05241 307 1777