Differences

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

--- trigger:MIDI [2021/12/30 07:30] – [Raw Packet] peternlewis
+++ trigger:MIDI [2025/03/01 02:53] (current) – [Packet] peternlewis
@@ Line 11: / Line 11: @@
 You can configure the trigger to execute the macro when the note is received from a particular device, from a particular channel or from any device or channel.
-The [[token:TriggerValue|%TriggerValue%]] token will hold `channel,note,velocity,device` for press and release (just the velocity was included prior to version 8.0).  You can easily access the individual parts using the token array notation, eg `%TriggerValue[2]%` will be the controller (8.0.4+).
+The [[token:TriggerValue|%TriggerValue%]] token will hold `channel,note,velocity,device` for press and release (8.0.4+) (just the velocity was included prior to version 8.0).  You can easily access the individual parts using the token array notation:
+^ Token      ^ Value ^
+| %TriggerValue[1]%    | Channel         |
+| %TriggerValue[2]%    | Note            |
+| %TriggerValue[3]%    | Velocity        |
+| %TriggerValue[4]%    | Device          |
 ====== Controller Change =======
@@ Line 36: / Line 43: @@
 You can configure the trigger to execute the macro when the controller change is received from a particular device, from a particular channel or from any device or channel.
-The [[token:TriggerValue|%TriggerValue%]] token will hold `channel,controller,value,device`.  You can easily access the individual parts using the token array notation, eg `%TriggerValue[2]%` will be the controller (8.0.4+).
+The [[token:TriggerValue|%TriggerValue%]] token will hold `channel,controller,value,device` (8.0.4+).  You can easily access the individual parts using the token array notation:
-====== Raw Packet =======
+^ Token      ^ Value ^
+| %TriggerValue[1]%    | Channel         |
+| %TriggerValue[2]%    | Controller      |
+| %TriggerValue[3]%    | Value           |
+| %TriggerValue[4]%    | Device          |
+====== 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 44: / Line 58: @@
 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          |
-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.