Differences

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

--- wiki:seq24togglemiditutorial [2011/01/25 12:55] – autostatic
+++ wiki:seq24togglemiditutorial [2013/06/02 15:45] (current) – external edit 127.0.0.1
@@ Line 13: / Line 13: @@
 ===== 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.
+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:
@@ Line 25: / Line 25: @@
 **(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.
-The last three is the range of data that will match.
+**(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.
-An example of the [midi-control] section of my .seq24rc file I use with the MPK Mini:
+**(data2 min)**: the minimal value for the filter to match. For note on/off events this is the amount of velocity for example.
+**(data2 max)**: the maximum value for the filter to match.
+An example of the [midi-control] section of my //.seq24rc// file I use with the MPK Mini:
   [midi-control]
@@ Line 117: / 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.