The UDP In DAT is used for receiving information over a UDP connection between two remotely located computers. It captures all the messages without any queuing or buffering, and allows you to send it any messages you want. Once this DAT has received a message it can reply to the sender using the 'send' command. Using the send command before it has received a message will not work because it doesn't know where to send data yet. When in multicast mode it doesn't send out a multicast message, it sends a reply directly to the originator for the last multicast message it got.
Protocolprotocol - ⊞ - Select which protocol to use, refer to the Network Protocols article for more information.
Messaging (UDP)msging -
Multi-Cast Messaging (UDP)multicastmsging -
Network Addressaddress - The multi-cast IP address to listen for.
Portport - The network port to listen on.
Shared Connectionshared - Use the same connection as other networking DATs using the same network protocol.
Row/Callback Formatformat - ⊞ - Determines how the incoming data is parsed.
One Per Byteperbyte - One row is added to the table per byte received.
One Per Lineperline - One row is added to the table per line received. The end of a line is delimited by \n, \r or a null character (\0).
One Per Messagepermessage - One row is added to the table per message received.
Activeactive - This check box enables the connection.
Parameters - Received Data Page
Callbacks DATcallbacks - The Callbacks DAT will execute once for each message coming in. See udpinDAT_Class for usage.
Execute fromexecuteloc - ⊞ - Determines the location the script is run from.
Current Nodecurrent - The script is executed from the current node location.
Callbacks DATcallbacks - The script is executed from the location of the DAT specified in the Callbacks DAT parameter.
Specified Operatorop - The script is executed from the operator specified in the From Operator parameter below.
From Operatorfromop - 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 Outputclamp - The DAT is limited to 100 messages by default but with Clamp Output, this can be set to anything including unlimited.
Maximum Linesmaxlines - Limits the number of messages, older messages are removed from the list first.
Clear Outputclear - Deletes all lines except the heading. To clear with a python script op("opname").par.clear.pulse()
Bytes Columnbytes - Outputs the raw bytes of the message in a separate column.
Parameters - Common Page
Languagelanguage - ⊞ - Select how the DAT decides which script language to operate on.
Inputinput - The DAT uses the inputs script language.
Nodenode - The DAT uses it's own script language.
Edit/View Extensionextension - ⊞ - Select the file extension this DAT should expose to external editors.
datdat - various common file extensions.
From Languagelanguage - pick extension from DATs script language.
Custom Extensioncustom - Specify a custom extension.
Custom Extensioncustomext - Specifiy the custom extension.
Word Wrapwordwrap - ⊞ - Enable Word Wrap for Node Display.
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.
Some operators have a DAT docked to them that contains some python functions. These functions, called "callbacks", get called when something in the operator changes.
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.
Any of the procedural data operators. OPs do all the work in TouchDesigner. They "cook" and output data to other OPs, which ultimately result in new images, data and audio being generated. See Node.