Skip to main content
Glama

Sync project to external timecode

sync_timecode

Sync external SMPTE, MTC, LTC, or OSC timecode to the TouchDesigner timeline. Creates input and normalization nodes, optionally drives project frame from house clock.

Instructions

Wire an external SMPTE/MTC/LTC/OSC timecode source into the TouchDesigner timeline. Creates the input op + Math CHOP normaliser + Null CHOP 'tc_out' (channels 'frame' and 'seconds'); optionally adds an Execute DAT that writes project.frame = tc_out['frame'] each cook so the timeline follows house clock. Requires the project to be playing — paused TD will not advance. LTC has no native TD decoder; the tool surfaces a warning and creates the audio input so the artist can attach an external decoder. MTC operator availability is build-dependent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoName prefix for the timecode subsystem COMP (defaults to 'tc_in1').
parentNoCOMP to host the timecode subsystem in./project1
sourceYesTimecode transport: 'mtc' = MIDI Time Code (MIDI In), 'ltc' = Linear Time Code from audio (no native TD decoder — surfaces a warning), 'osc' = OSC In CHOP listening on host:port.
hostNo(osc) Bind interface; ignored for mtc/ltc. Defaults to '0.0.0.0'.
portNo(osc) UDP port (default 7000) or (mtc/ltc) device index (default 0). The device picker can hang on a macOS permission modal — keep the default unless you know the device.
osc_addressNo(osc) OSC address pattern carrying the timecode payload. Defaults to '/timecode'.
fpsNoReference frame-rate for SMPTE→frame conversion (24/25/29.97/30).
drive_timelineNoWhen true, an Execute DAT writes project.frame = tc_out['frame'] each cook. Requires the project to be playing — paused TD will not advance.
cue_on_labelNo(osc) If the payload is a string matching a project cue name, call project.cue(name) instead of seeking.
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses creation of specific operators (input op, Math CHOP, Null CHOP), optional Execute DAT, and macOS permission modal hang risk. Annotations are consistent (no contradiction).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with main purpose, then details. Efficiently structured with separate sentences for warnings and optional functionality, but could be slightly more concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 9 parameters, no output schema, and annotations, the description covers main functionality, prerequisites, and warnings. Leaves little ambiguity about what the tool does and its side effects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents parameters well. The description adds marginal extra meaning, such as explaining the device picker issue, but mostly reiterates what's in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'wire' and the resource 'external SMPTE/MTC/LTC/OSC timecode source into the TouchDesigner timeline', specifying scope. However, it does not explicitly distinguish from sibling tools like 'sync_external_clock', leaving some ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides context such as the requirement for the project to be playing and a warning about LTC decoder limitations. However, it lacks explicit when-not-to-use scenarios or alternatives to other timecode sync tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Pantani/tdmcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server