Full Midi Command Reference

Talk about your MIDI bindings and controller setup

Moderator: jesse

Post Reply
kasbah
Posts: 117
Joined: Tue Sep 06, 2011 7:01 pm

Full Midi Command Reference

Post by kasbah »

I have started making a full midi command reference page. So far I have managed to generate a html page which fits into the existing SooperLooper docs style wise and contains all bindable commands. They are mostly stubs though as I have mostly just copied descriptions accross from the GUI command reference so far. Take a look: http://kaspar.h1x.com/sl_doc_html/doc_m ... mands.html

It would be great if everyone could pitch in and write a short description of their favourite command. Each command should be wrapped in code tags and formatting should be as follows.

Code: Select all

[cmd/ctrl/g.ctrl] command_name
Description (insert "<p>" for multiple paragraphs)
**
*Special Ending Description (if there is one, otherwise leave all asterisks off)
***
The command name should start with the type enclosed in square brackets followed by the name. The description should be next. If you need more than one paragraph seperate them with a <p> tag.

If your command description contains a Special Ending segment lay down a line of two asterisks (**) and then put each special ending description bullet point on a separate line starting of with one asterisk. Put three asterisks to denote the end of the special ending box.

Here is an example:

Code: Select all

[cmd] mute
Press to mute loop output. Dry passthough audio will be unaffected. To continue playing the loop in time press MUTE again. To continue playing the loop from the top press TRIG. To play back the loop once and return to mute, press ONCE. 
And one with a special ending note and two paragraphs (note the <p> tag):

Code: Select all

[cmd] multiply
This similar to overdub, except the original loop is repeated underneath you "multiplying" the loop length until you stop it. Thus it can turn a 1 measure loop into a 2,3, etc measure loop. QuantizeMode and RoundMode affect how the overdubbing starts and stops. QuantizeMode affects when the operation begins, and RoundMode affects if the new audio continues to be added throughthe end of the current cycle after hitting the final record.
<p> Keep in mind that the original loop length is a "cycle" and the loop length will be a multiple of that. You can actually make an already multiplied loop have fewer cycles when using Multiply on loops that have already been multiplied. 
**
*If you end a MULTIPLY with a RECORD press it ends the loop immediately and resets the cycle length to the whole loop. 
*The MultiIncrease function is implemented which allows you to increment the cycle count ahead of time, without needing to wait until the exact time to finish the multiply. Basically, press Multiply as if you were finishing it, then before the current cycle plays out, press Multiply again repeatedly to add cycles. The multiply will resume and automatically go into playback after the specified number of cycles. 
***
For those interested here are the scripts and lists I am using to generate that page.

All feedback or suggestions welcome. GET DOCUMENTING! :D

I will update the page as descriptions come in and at some point Jesse will hopefully include a form of this page on the SL site.

jesse
Posts: 530
Joined: Sat Sep 06, 2008 9:46 am
Contact:

Re: Full Midi Command Reference

Post by jesse »

Wow, thanks for taking the time to do this! I'll keep an eye out for any status updates.... I don't have time to work on it myself at the moment (even though only I have some of these answers :)

kasbah
Posts: 117
Joined: Tue Sep 06, 2011 7:01 pm

Re: Full Midi Command Reference

Post by kasbah »

Ok, thanks for the encouragement Jesse. I am just going to start going through these from the top. First I am changing the mute description slightly to:

Code: Select all

[cmd] mute
Press to mute loop output, press again to un-mute. Dry passthough audio will be unaffected. To continue playing the loop from the top press "[cmd]trig". To play back the loop once and return to mute, press "[cmd] oneshot". 
Then there is some easy ones:

Code: Select all

[cmd] mute_off
Press to un-mute loop output.
****
[cmd] mute_on
Press to mute loop output.
****
[cmd] mute_trigger
Press to mute. Press again to un-mute and start the loop from the top (like "[cmd] trigger"). 
rephrasing pause to:

Code: Select all

[cmd] pause
Press to pause loop playback, press again to un-pause. Dry passthough audio will be unaffected. To continue playing the loop from the top press "[cmd] trigger". To play back the loop once and return to mute, press "[cmd] oneshot". 
and some more easy ones:

Code: Select all

[cmd] pause_off
Un-pause the loop playback.
****
[cmd] pause_on
Pause the loop playback.
Now I am at "[cmd] record_exclusive" which I havn't personally used but seems to stem from this thread. I'll get on doing some research in a while if someone doesn't beat me to it.

kasbah
Posts: 117
Joined: Tue Sep 06, 2011 7:01 pm

Re: Full Midi Command Reference

Post by kasbah »

OK, I have done a few more. I am a bit stuck with the record_or_overdub_solo_trig and record_overdub_end_solo_trig as to me they don't seem to do anything beyond their non-trig counterparts. They don't seem to trigger the loop or anything. Anyone use these and care to explain?

kasbah
Posts: 117
Joined: Tue Sep 06, 2011 7:01 pm

Re: Full Midi Command Reference

Post by kasbah »


Danneh
Posts: 1
Joined: Fri Jun 22, 2012 11:20 am

Re: Full Midi Command Reference

Post by Danneh »

It would be nice to include the little description of selected_loop_num jessee made here:
viewtopic.php?f=7&t=36&p=593#p593

Something like this, maybe? Awesome job with this, by the way. Has helped me out quite a bit getting started with this program!

Code: Select all

[g.ctrl] selected_loop_num
Both of the Data Range fields must be set to the same value. The Data Range value represents the loop that will be selected. For instance, if both Data Range values are 0, the first loop will be selected. 1, the second loop, and etc.

kasbah
Posts: 117
Joined: Tue Sep 06, 2011 7:01 pm

Re: Full Midi Command Reference

Post by kasbah »

Thanks Danneh! I think you confused the data and target range fields though. Could give these better names probably. Something like "Sooperlooper Value Range" and "Midi Value Range" maybe. I updated with this clarification:

Code: Select all

[g.ctrl] selected_loop_num
Select a specific loop number. The target range fields specify the the loop number starting from 0 for the first loop. If you set both target range fields to a specific loop number then that number will always be selected when the command triggers.

johey
Posts: 4
Joined: Tue Sep 22, 2015 3:19 am

Re: Full Midi Command Reference

Post by johey »

The link is broken. I would love to read the MIDI command references. Any chance to have it back?

Freasy
Posts: 60
Joined: Fri Aug 29, 2014 5:37 pm

Re: Full Midi Command Reference

Post by Freasy »

johey wrote:The link is broken. I would love to read the MIDI command references. Any chance to have it back?
You can find the MIDI command reference and more documentation over here: Click me, I'm a link!

Post Reply