Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
wiki:seq24togglemiditutorial [2011/01/25 12:37] – autostatic | wiki:seq24togglemiditutorial [2013/06/02 15:45] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 11: | Line 11: | ||
* Some time | * Some time | ||
- | After starting seq24 for the first time it will create a // | + | ===== Setting up seq24 ===== |
+ | |||
+ | After starting seq24 for the first time it will create a // | ||
The layout of each filter inside the bracket is as follows: | 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/ | ||
+ | |||
+ | **(inverse)**: | ||
- | (on/off): if the on/off is set to 1, it will match the incoming | + | **(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]], |
- | (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. | + | **(data1)**: the actual MIDI event message number in decimals. This could be a note on/off event or a control/ |
- | (midi status byte (channel ignored)): | + | **(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:// | + | **(data2 max)**: |
- | 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 2. 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] | [midi-control] | ||
Line 115: | Line 121: | ||
73 [0 0 | 73 [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 | + | 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 |
+ | |||
+ | ===== Queuing | ||
+ | |||
+ | The Akai MPK Mini has a Sustain button and I've set the Sustain | ||
+ | |||
+ | # mod queue | ||
+ | 70 [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. |