Differences

This shows you the differences between two versions of the page.

--- wiki:seq24togglemiditutorial [2011/01/25 11:10] – autostatic
+++ wiki:seq24togglemiditutorial [2013/06/02 13:45] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== seq24: toggle sequences with a MIDI controller ======
-It is documented in the [[http://www.filter24.org/seq24/SEQ24|SEQ24]] file but I haven't found any reference of anyone using it so I tried to set this up myself because toggling sequences with your keyboard is just not very practical.
+===== Introduction =====
-Ingredients: seq24, a MIDI controller (in my case an AKAI MPK Mini), some time
+Even though this feature is documented in the [[http://www.filter24.org/seq24/SEQ24|SEQ24]] file I haven't found any reference of anyone using it so I tried to set this up myself because toggling sequences with your keyboard is just not very practical.
-After starting seq24 for the first time it will create a .seq24rc file in your home directory, open it and the first section you'll see, [midi-control], is the section we need. The matrix represents the first two screensets (entries 0 up to and including 63) and some control keys (entries 64 up to and including 73). The three fields between the brackets on each line correspond to a MIDI filter, if the incoming MIDI event matches the filter it will either toggle (first field), enable (second field) or disable (third field) the sequence.
+===== Requirements =====
+  * A recent version of [[https://edge.launchpad.net/seq24/|seq24]], preferably the latest version (0.9.2 as of the writing of this article)
+  * A MIDI controller (in my case an [[http://www.akaipro.com/mpkmini|AKAI MPK Mini]])
+  * Some time
+===== Setting up seq24 =====
+After starting seq24 for the first time it will create a //.seq24rc// file in your home directory. Open it and the first section you'll see, [midi-control], is the section we need. The matrix represents the first two screensets (entries 0 up to and including 63) and some control keys (entries 64 up to and including 73). The three fields between the brackets on each line correspond to a MIDI filter, if the incoming MIDI event matches the filter it will either toggle (first field), enable (second field) or disable (third field) the sequence.
 The layout of each filter inside the bracket is as follows:
-[(on/off) (inverse) (midi status byte (channel ignored)) (data1) (data2 min) (data2 max)]
+**[(on/off) (inverse) (midi status byte (channel ignored)) (data1) (data2 min) (data2 max)]**
+**(on/off)**: if the on/off is set to 1, it will match the incoming midi to the pattern and perform the action (on/off/toggle) if the data falls in the range specified.  All values are in decimal.
+**(inverse)**: the inverse field will make the sequence perform the opposite action (off for on, on for off) if the data falls outside the specified range.
+**(midi status byte (channel ignored))**: a MIDI status byte number in decimals. You can look them up in the [[http://www.midi.org/techspecs/midimessages.php|MIDI messages tables]], the relevant data is in the [[http://www.midi.org/techspecs/midimessages.php#2|second table]]. As the channel on which the events are sent is ignored you should always use the values for channel 1.
+**(data1)**: the actual MIDI event message number in decimals. This could be a note on/off event or a control/mode change event for example.
-If the on/off is set to 1, it will match the incoming midi to the pattern and perform the action (on/off/toggle) if the data falls in the range specified.  All values are in decimal.
+**(data2 min)**: the minimal value for the filter to match. For note on/off events this is the amount of velocity for example.
-The last three is the range of data that will match. MIDI status byte values can be looked up in the [[http://www.midi.org/techspecs/midimessages.php|MIDI Message Table 1]].
+**(data2 max)**: the maximum value for the filter to match.
-As the channel on which the events are sent is ignored you should always use the values for channel 1 of the MIDI Message Table 1. An example of the [midi-control] section of my .seq24rc file I use with the MPK Mini:
+An example of the [midi-control] section of my //.seq24rc// file I use with the MPK Mini:
   [midi-control]
@@ Line 104: / Line 121: @@
 [0 0   0   0   0   0] [0 0   0   0   0   0] [0 0   0   0   0   0]
-What this example does is listening for notes 96 up to and including 111 and it toggles the sequences on note on events and toggles it off on note off events. But what about queuing sequences? Well, the Akai MPK Mini has a Sustain button and I've set this MIDI event up as the queue modifier (see above, the fields after entry 70 which corresponds with 'mod queue'). So when I hold down this button and press one of the pads on my MPK Mini the corresponding sequence gets queued.
+What this example does is listening for notes 96 up to and including 111 and it toggles the sequences on note on events and toggles them off on note off events.
+===== Queuing sequences =====
+The Akai MPK Mini has a Sustain button and I've set the Sustain MIDI event (with MIDI status byte 176 and control/mode change number 64) up as the queue modifier in the 'mod queue' entry:
+  # mod queue
+[0 0   0   0   0   0] [1 0 176  64 127 127] [1 0 176  64   0   0]
+So when I hold down this button and press one of the pads on my MPK Mini the corresponding sequence gets queued.
+===== Final steps =====
+Start seq24 and connect your MIDI controller (File - Options - MIDI Input). Now you should be able to toggle and queue any patterns in your seq24 session if you set up your .seq24rc file correctly.