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.
MIDI In Parameters
/active - Logs MIDI events when turned on.
/device - Path to the MIDI device Table DAT.
/id - Specify the id of which device to use.
/script - The Script DAT will execute once for each message coming in. The first argument is the message, the second argument is the line number (index starting at 0) in the DAT of the message.
/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).
- Script DAT
/script- The script is executed from the location of the DAT specified in the Script DAT parameter.
- Specified Component
/comp- The script is executed from the component specified in the Component parameter below.
/component - The component who's state change will trigger the DAT to execute its script when Execute is set to On Panel Change. This component is also the path that the script will be executed from if the Execute From parameter is set to Specified Component .
/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 script command, here is an example:
opparm -c /midiin1 clear
/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.