Differences

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

--- trigger:MIDI [2025/02/26 02:11] – [Controller Change] peternlewis
+++ trigger:MIDI [2026/05/07 02:44] (current) – August
@@ Line 1: / Line 1: @@
+====== MIDI Trigger ======
 The *MIDI trigger* lets you execute a macro when a MIDI packet is received.
@@ Line 52: / Line 54: @@
-====== 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).
@@ Line 58: / Line 60: @@
 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.
+^ Token      ^ Value ^
+| %TriggerValue[1]%    | Data            |
+| %TriggerValue[2]%    | Device          |
-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.
+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.