Engine Model
CITO is organized around one engine authority. TouchDesigner operators act as package-facing nodes, but the work is compiled into an engine plan and processed against typed streams.
Why This Matters
Section titled “Why This Matters”The package can present many operators in OP Create while keeping scheduling, plugin loading, stream typing, and runtime state in one place. That is why CITO can feel like a broad operator category without each operator becoming its own isolated runtime.
Plugin Contract
Section titled “Plugin Contract”Each engine plugin declares:
- a canonical engine name
- accepted input stream types
- emitted output stream types
- parameter schema
- latency class
- telemetry channels
- process callbacks
The TouchDesigner shell uses that declaration to expose usable parameters and routing while the engine keeps graph execution consistent.
Package Shape
Section titled “Package Shape”The current audio package ships the engine, plugin folder, TD wrapper DLL, package TOX, and package-facing TDFam masters. It does not ship source code or build tools.