Skip to main content
Glama

Bind parameter to channel

bind_to_channel

Drive one or more TouchDesigner node parameters from a CHOP channel in real time, with optional attack/release smoothing for clean envelope following.

Instructions

Drive one or more node parameters from a CHOP channel by expression — the link that makes a visual react. Point it at an audio_features channel (bass/mid/treble/level) or a tempo_sync channel (ramp/pulse/beat) with a scale and offset, and each target parameter tracks that signal live. This is how you wire extract_audio_features / create_tempo_sync into a visual system. Optionally add attack/release smoothing (in seconds) — or a single smooth time — to insert a Lag CHOP between the channel and the parameter so reactivity follows a clean envelope instead of flickering on raw audio (e.g. a fast attack + slow release for a punchy hit that decays smoothly).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetsYesParameters to drive, each written as 'nodePath.parName' (e.g. '/project1/sys/transform1.scale'). Each is switched to expression mode so it tracks the channel live.
source_chopYesPath of the CHOP that carries the driving channel (e.g. an audio_features Null).
channelYesChannel name to read from the source CHOP (e.g. 'bass', 'level', 'ramp', 'pulse').
scaleNoMultiply the channel value (mapping gain).
offsetNoAdd to the scaled value (mapping offset).
attackNoSmoothing rise time in seconds — how slowly the bound value follows the channel UP. 0 = instant (no smoothing on the way up). A small attack with a larger release gives a snappy hit that decays smoothly (envelope follow).
releaseNoSmoothing fall time in seconds — how slowly the bound value follows the channel DOWN. 0 = instant (no smoothing on the way down). Set release > attack to remove flicker while keeping transients punchy.
smoothNoConvenience: symmetric smoothing time in seconds applied to BOTH rise and fall (sets attack=release=smooth). Use this for simple low-pass-style de-jitter; use attack/release separately for an envelope follower.
smoothing_containerNoWhere to create the Select+Lag smoothing CHOPs when smoothing is active; defaults to the first target's parent network. Ignored when no smoothing is requested.
Behavior4/5

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

Annotations (readOnlyHint=false, destructiveHint=false) provide basic safety info. The description adds behavioral context: parameters are switched to expression mode for live tracking, optional Lag CHOP insertion for smoothing, and envelope follow behavior. This goes well beyond the annotations, though it could mention if existing expressions are overwritten.

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

Conciseness5/5

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

Two sentences: the first states purpose and typical sources, the second expands on smoothing behavior with a concrete example. Every sentence is substantive, no redundancy, and the most critical information (what it does) is front-loaded.

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 the tool's complexity (9 parameters, smoothing options, expression mode) and no output schema, the description covers the primary workflow and smoothing options. It lacks explicit mention of return values or side effects beyond expression mode changes, but overall it is sufficient for correct tool invocation.

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

Parameters5/5

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

All 9 parameters have descriptions in the schema, and the description adds practical meaning: explaining scale/offset as mapping gain, attack/release as envelope follower times, smooth as symmetric convenience, and smoothing_container location. The second sentence provides a usage example that clarifies semantic nuances.

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

Purpose5/5

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

The description clearly states 'Drive one or more node parameters from a CHOP channel by expression' and specifies the scope (audio_features/tempo_sync channels). It distinguishes from siblings by explicitly naming 'extract_audio_features / create_tempo_sync' as complementary tools, making the purpose and context unambiguous.

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

Usage Guidelines4/5

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

The description explains when to use the tool (to wire audio or tempo data into visuals) and how to apply smoothing (attack/release vs smooth). It gives concrete scenarios like 'fast attack + slow release for a punchy hit'. However, it does not explicitly state when NOT to use it or provide direct comparisons to alternatives like 'bind_audio_reactive'.

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