Difference between revisions of "MIDI In DAT"

From TouchDesigner Documentation
Jump to: navigation, search
Line 76: Line 76:
 
|Parorder=3
 
|Parorder=3
 
|OPtype=midiin
 
|OPtype=midiin
|Parsummary=
+
|Parsummary=Filter by the MIDI message content. Example "Control Change"
 
}}
 
}}
 
{{ParString
 
{{ParString
Line 84: Line 84:
 
|Parorder=4
 
|Parorder=4
 
|OPtype=midiin
 
|OPtype=midiin
|Parsummary=
+
|Parsummary=Filter by the MIDI message channel. Channels range from 1 to 16.
 
}}
 
}}
 
{{ParString
 
{{ParString
Line 92: Line 92:
 
|Parorder=5
 
|Parorder=5
 
|OPtype=midiin
 
|OPtype=midiin
|Parsummary=
+
|Parsummary=Filter by the MIDI message index. Indices range from 1 to 128.
 
}}
 
}}
 
{{ParString
 
{{ParString
Line 100: Line 100:
 
|Parorder=6
 
|Parorder=6
 
|OPtype=midiin
 
|OPtype=midiin
|Parsummary=
+
|Parsummary=Filter by the MIDI message value. Values range from 0 to 127.
 
}}
 
}}
 
 

Revision as of 17:45, 16 November 2018

  • Invalid title: ""

Summary
[edit]

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.

See also the MIDI Event DAT, MIDI In Map CHOP, MIDI In CHOP, MIDI Out CHOP, Tscript midi() Command, MIDI Device Mapper Dialog.

PythonIcon.png[[{{{opClass}}}]]


Parameters - Page

Template:ParToggle Template:ParDatRef Template:ParString


Parameters - Page

Template:ParToggle Template:ParToggle Template:ParToggle Template:ParString Template:ParString Template:ParString Template:ParString


Parameters - Page

Template:ParDatRef Template:ParMenu Template:ParNodeRef Template:ParToggle Template:ParInteger Template:ParButton Template:ParToggle


Parameters - Common Page

Language language - - Select how the DAT decides which script language to operate on.

  • Input input - The DAT uses the inputs script language.
  • Node node - The DAT uses it's own script language.

Edit/View Extension extension - - Select the file extension this DAT should expose to external editors.

  • dat dat - various common file extensions.
  • From Language language - pick extension from DATs script language.
  • Custom Extension custom - Specify a custom extension.

Custom Extension customext - Specifiy the custom extension.  

Word Wrap wordwrap - - Enable Word Wrap for Node Display.

  • Input input - The DAT uses the inputs setting.
  • On on - Turn on Word Wrap.
  • Off off - Turn off Word Wrap.

TouchDesigner Build:

DATs
Art-Net • CHOP Execute • CHOP to • Clip • Convert • CPlusPlus • DAT •  Execute • DAT xport • Error • EtherDream • Evaluate • Examine • Execute • FIFO • File In • File Out • Folder • In • Indices • Info • Insert • Introduction To DATs id • Keyboard In • Lookup • Merge • MIDI Event • MIDI In • Monitors • MQTT Client • Multi Touch In • NDI • Null • OP Execute • OP Find • OSC In • OSC Out • Out • Panel Execute • Parameter • Parameter Execute • Perform • Render Pick • Reorder • Script • Select • Serial • Experimental:SocketIO • SOP to • Sort • Substitute • Switch • Table • TCP/IP • Text • Touch In • Touch Out • Transpose • TUIO In • UDP In • UDP Out • UDT In • UDT Out • Experimental:Web Client • Web • Experimental:Web Server • WebSocket • XML

An Operator Family that manipulates text strings: multi-line text or tables. Multi-line text is often a command Script, but can be any multi-line text. Tables are rows and columns of cells, each containing a text string.

TouchDesigner's original built-in Command scripting language prior to Python.

The generic thing that holds an Operator, and includes Flags (display, bypass, lock, render, immune) and its position/size in the network. Whether you "lay down an Operator" or "lay down an Node", you're doing the same thing.