MIDI In DAT
The MIDI In DAT logs all MIDI messages coming into TouchDesigner from a specified MIDI device. It outputs columns in a table format - message, type, channel, index, value.
However general setup is simpler. Once you have MIDI set up via the Dialogs -> MIDI Device Mapper, TouchDesigner is ready to receive MIDI via Select CHOPs that point to
/local/maps/map1 for device 1, etc.
Parameters - Connect Page
/active - logs MIDI events when turned on.
/device - path to the MIDI device Table DAT
/id - specify the id of which device to use. The id can be found in the MIDI Device Mapper Dialog.
Parameters - Filter Page
/skipsense - does not log sense messages when this is turned on.
/skiptiming - does not report timing messages when this is turned on.
/filter - turning this on enables the message filtering parameters below.
Parameters - Received Messages Page
callback - Runs this script once for each row added to the table (ie. each MIDI event received). See midiinDAT_Class for usage.
executeloc - Determines the location the script is run from.
- Current Node
current- The script is executed from the current node location (for example, where 'cc' points to).
callback- The script is executed from the location of the DAT specified in the Callbacks DAT parameter.
- Specified Operator
op- The script is executed from the operator specified in the From Operator parameter below.
fromop - The operator whose state change will trigger the DAT to execute its script when Execute from is set to Specified Operator. This operator is also the path that the script will be executed from if the Execute From parameter is set to Specified Operator.
clamp - The DAT is limited to 100 messages by default but with Clamp Output, this can be set to anything including unlimited.
maxlines - Limits the number of messages, older messages are removed from the list first.
clear - Deletes all lines except the heading. To clear with a python script
bytes - Outputs the raw bytes of the message in a separate column.