User Tools
trigger:MIDI
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
trigger:MIDI [2025/02/25 21:11] peternlewis [Controller Change] |
trigger:MIDI [2025/02/28 21:53] (current) peternlewis [Packet] |
||
|---|---|---|---|
| Line 52: | Line 52: | ||
| - | ====== Raw Packet ======= | + | ====== Packet ======= |
| This is a rather advanced trigger that requires some knowledge of the MIDI protocol (v8+). You can configure the minimum and maximum size of the packet, as well as the range of the first two bytes, and a regex that matches the specified packet (the format will be a sequence of space-separated hex values). | This is a rather advanced trigger that requires some knowledge of the MIDI protocol (v8+). You can configure the minimum and maximum size of the packet, as well as the range of the first two bytes, and a regex that matches the specified packet (the format will be a sequence of space-separated hex values). | ||
| Line 58: | Line 58: | ||
| This should allow you to capture things like SysEx and HUI protocol packets and the like. | This should allow you to capture things like SysEx and HUI protocol packets and the like. | ||
| - | The [[token:TriggerValue|%TriggerValue%]] token will the space-separated hex values representing the packet, followed by a comma, followed by the source device. | + | The [[token:TriggerValue|%TriggerValue%]] token will the space-separated hex values representing the packet, followed by a comma, followed by the source device. You can get the two parts with. |
| - | If you extract just the bytes (ie, everything up until the first comma), then you can easily access the individual parts using the token array notation, eg `%TriggerValue[3] %` will be the third value (8.0.4+) — note the `[space]` in `][space]%`, the space is the separator for the array, instead of the default comma. | + | ^ Token ^ Value ^ |
| + | | %TriggerValue[1]% | Data | | ||
| + | | %TriggerValue[2]% | Device | | ||
| + | |||
| + | If you extract just the bytes (ie, everything up until the first comma), then you can then easily access the individual parts using the token array notation, eg `%DataVar[3] %` will be the third value (8.0.4+) — note the `{space}` in `]{space}%`, the space is the separator for the array, instead of the default comma. | ||
trigger/MIDI.1740535880.txt.gz · Last modified: 2025/02/25 21:11 by peternlewis
Page Tools
