@hybridlabor-api/aos 4.2.0 → 4.4.0

package/mcps/tdmcp/docs/guide/dashboard-foh.md

@@ -1,93 +0,0 @@
----
-description: "Build a front-of-house control surface for your TouchDesigner show with tdmcp — a web cockpit, a touchscreen panel, a phone remote, and live video/audio scopes."
----
-
-# Front-of-house dashboard
-
-Once the show is built, you need to *run* it — from the booth, from a phone in
-the crowd, from a touchscreen at the lip of the stage. This arc is the
-front-of-house (FOH) layer: control surfaces and monitors that sit on top of the
-network and give an operator cue buttons, faders, a panic switch and a view of
-what the signal is actually doing.
-
-Reach for these when the build is done and you're thinking about the
-performance: who taps what, on which screen, with how many seconds of warning.
-
-## The web cockpit: `create_stage_dashboard`
-
-`create_stage_dashboard` (Layer 2) is the primary FOH tool — a unified
-web-based cockpit served by a Web Server DAT inside TouchDesigner and reachable
-from any browser or phone on the network. It gives you cue-launch buttons,
-master faders, a VU meter, a beat indicator and a PANIC safety control
-(Blackout / Freeze).
-
-It has two layouts, selected with `layout`:
-
-- **`v1`** — the original cockpit.
-- **`v2`** (the "dashboard-v2" pass) — adds a stereo VU meter, a BPM display, a
-  cue timeline strip (driven by `cue_times` and a `tempo_channel`), an
-  FPS/cook-time overlay, and a sticky confirm-tap PANIC bar so you can't blackout
-  the room by mistake.
-
-> *"Build a v2 stage dashboard for `/project1/mainstage` with my four scene cues,
-> a master fader, and the BPM display, on port 9982."*
-
-Because it runs entirely inside TD, there's no separate app to install — open the
-URL it prints and you're driving the show.
-
-## Compact surfaces
-
-When you don't want a browser:
-
-- **`create_control_surface`** (Layer 2) builds a playable Container COMP of
-  vertical faders and cue buttons, meant to be opened in Perform/Panel mode on a
-  touchscreen or second monitor. Faders drive parameters live; buttons recall or
-  morph to named cues (from `manage_cue`) with optional crossfade.
-- **`create_phone_remote`** (Layer 2) serves a mobile-optimized single-page web
-  remote that auto-discovers a COMP's numeric custom parameters and renders them
-  as range sliders — the quickest way to put a few live knobs in your pocket.
-- **`create_control_panel`** (Layer 2) is the generic building block: a custom
-  parameter page (sliders, toggles, menus, RGB swatches, pulse buttons) bound by
-  expression to drive node parameters. Many Layer-1 tools call it internally to
-  expose their own controls.
-
-> *"Put a touchscreen control surface on my master mix: four scene cue buttons
-> and faders for blur, feedback and master brightness."*
-
-## Watch the signal: scopes & meters
-
-FOH is also about *seeing* what's going out:
-
-- **`create_video_scopes`** (Layer 1) builds a broadcast-style monitor with up to
-  four panels — waveform (luma), RGB parade, vectorscope and histogram —
-  composited into one TOP. Default source is a synthetic test pattern, so it
-  builds with no camera permission; opt into `device` for the live camera.
-- **`create_waveform`** (Layer 1) is the time-domain audio oscilloscope — the raw
-  signal scrolling left to right — and feeds the dashboard's audio readouts.
-
-> *"Add a 2×2 video scope monitor on the master output so I can check levels
-> before doors."*
-
-## Safety lives here too
-
-The dashboard's PANIC control and the show's
-[`create_safety_blackout_chain`](/guide/show-timelines#live-safety) are two
-ends of the same idea: a kill switch the operator can always reach. Wire the
-blackout into the master output, surface its toggle on the dashboard, and the
-booth has a guaranteed way to cut to black.
-
-## How it fits together
-
-Build the show ([Show timelines & setlists](/guide/show-timelines)), then put a
-surface on it: `create_stage_dashboard` for the networked web cockpit,
-`create_control_surface` for a wired touchscreen, `create_phone_remote` for a
-pocket of sliders. Add `create_video_scopes` / `create_waveform` to monitor the
-signal, and keep the panic path one tap away.
-
-## See also
-
-- [Live performance & control](/guide/prompt-cookbook#live-performance-control)
-  and [Output & mapping](/guide/prompt-cookbook#output-mapping) in the prompt
-  cookbook.
-- [Show timelines & setlists](/guide/show-timelines) for the cues and transport
-  the dashboard drives.

package/mcps/tdmcp/docs/guide/faq.md

@@ -1,62 +0,0 @@
----
-title: FAQ — TouchDesigner MCP server
-titleTemplate: false
-description: "FAQ about tdmcp, the TouchDesigner MCP server: is there an MCP for TouchDesigner, can Claude or Cursor control it, is it free, which clients work, and how it works."
----
-
-# Frequently asked questions
-
-## Is there an MCP server for TouchDesigner?
-
-Yes — **tdmcp** is an open-source (MIT) Model Context Protocol server for
-[TouchDesigner](https://derivative.ca). It connects AI assistants like Claude,
-Cursor and Codex to TouchDesigner so they can build real node networks from
-plain-language prompts.
-
-## Can Claude or Cursor control TouchDesigner?
-
-Yes. With tdmcp connected, you describe a visual in plain language and the
-assistant creates, wires, inspects and previews the actual operators inside your
-TouchDesigner project.
-
-## Do I need to know how to code, or which operators to use?
-
-No. You describe the result you want; tdmcp carries an embedded reference of
-TouchDesigner's real operators, so the AI picks and wires them for you. See
-[What is tdmcp?](/guide/what-is-tdmcp).
-
-## Is tdmcp free?
-
-Yes — it's free and open-source under the MIT license, and it works with the free
-non-commercial edition of TouchDesigner.
-
-## Which AI assistants work with tdmcp?
-
-Claude Desktop (the easiest, [one-click install](/guide/install)), Claude Code,
-Codex and Cursor — any MCP-capable client.
-
-## Does it work offline, without a paid API?
-
-It ships a [local LLM copilot](/reference/cli) (`tdmcp chat`) that handles simple
-tasks through a local model, and the server stays usable even when TouchDesigner
-is closed.
-
-## Does tdmcp run on macOS and Windows?
-
-Yes, on both — anywhere TouchDesigner and Node.js 20+ run.
-
-## Is it safe to run?
-
-The bridge runs inside your own TouchDesigner on localhost. For untrusted networks
-you can require a bearer token and disable the code-execution endpoints — see
-[Security](/reference/architecture#security).
-
-## How is tdmcp different from other TouchDesigner MCP experiments?
-
-It pairs a real operator knowledge base with a bridge that executes inside
-TouchDesigner in a create → verify → preview loop — so the AI uses real operators
-and fixes its own mistakes instead of guessing.
-
-::: tip Portuguese
-This documentation is also available in Portuguese — [start here](/pt/).
-:::

package/mcps/tdmcp/docs/guide/first-visual.md

@@ -1,76 +0,0 @@
----
-description: "Make your first visual with tdmcp, the TouchDesigner MCP server — ask in plain language and watch the node network build, verify and preview itself."
----
-
-# Your first visual
-
-You've [installed tdmcp](/guide/install) and seen `bridge running` in
-TouchDesigner's Textport. Now let's make something.
-
-## 1. Ask for it
-
-In your AI assistant, type a description of what you want. Try this:
-
-> *"Create a feedback tunnel from noise with blur and displace, add bloom, and
-> show me a preview."*
-
-The AI will build the network in your TouchDesigner project, check it for errors,
-and show you a thumbnail of the result. Switch to TouchDesigner and you'll see the
-nodes appear, wired up and neatly arranged.
-
-::: tip Confirm the bridge first
-If it's your first prompt of the session, the AI may run a quick health check
-(`get_td_info`) to make sure TouchDesigner is reachable. If it says it can't
-reach TouchDesigner, see [Troubleshooting](/guide/troubleshooting).
-:::
-
-## 2. Iterate in plain language
-
-You don't start over — you just say what to change:
-
-- *"Make it warmer."*
-- *"Add a feedback trail."*
-- *"Slow the movement down."*
-- *"More contrast, and push the blur."*
-- *"Add a subtle glitch."*
-
-Each request adjusts the existing network. Preview again whenever you want to see
-where you are: *"show me a preview."*
-
-## 3. Make it react to sound
-
-> *"Make an audio-reactive particle galaxy that responds to my music, and show me
-> a preview."*
-
-::: warning macOS: microphone permission
-The first time a visual listens to your microphone, macOS pops up a permission
-dialog. **Click Allow** — until you do, TouchDesigner may appear frozen. If you'd
-rather not use the mic while testing, ask for a *test tone* source instead. Full
-details in [Troubleshooting](/guide/troubleshooting#macos-microphone-camera-permission).
-:::
-
-Many systems arrive **already playable** — they come with a little control panel
-(a Feedback knob, a Sensitivity knob, particle Drag/Turbulence/Gravity, an
-evolution Speed) you can grab and tweak live in TouchDesigner.
-
-## 4. Show it full-screen
-
-When you like it:
-
-> *"Output it to a full-screen window on my second monitor."*
-
-You can also ask to record it, send it over NDI/Syphon to other software, or map
-it onto a projector. See the [prompt cookbook](/guide/prompt-cookbook) for more.
-
-## 5. Save your look
-
-- *"Save these control settings as a preset called 'opening'."*
-- *"Save this whole network as a reusable recipe."*
-
-## Where to go next
-
-- [Prompt cookbook](/guide/prompt-cookbook) — ready-made prompts grouped by what
-  you want to make.
-- [Recipe gallery](/guide/recipes) — pre-built systems you can ask for by name.
-- [Glossary](/guide/glossary) — plain-language definitions of the TouchDesigner
-  words you'll hear.

package/mcps/tdmcp/docs/guide/generators.md

@@ -1,230 +0,0 @@
----
-description: "A reference for tdmcp's Layer-1 generators — what each one builds and when to reach for it, for every generator shown in the prompt cookbook."
----
-
-# Layer-1 generators reference
-
-The [prompt cookbook](/guide/prompt-cookbook) shows these generators *in action*
-— grouped by what you want to make. This page is the companion **reference**: one
-short "what it builds + when to reach for it" entry per generator, so you can pick
-the right altitude when two tools look similar (the GPU particle field versus the
-flock; the color grade versus the color wheels; kinetic text versus the crawl).
-
-Layer-1 generators each build a whole, wired, previewable network in one call.
-Most expose live controls and default to a self-contained synthetic source so they
-preview with no camera, no audio device and no plugin. You rarely name them — the
-AI picks them from your prompt — but knowing the vocabulary helps you steer.
-
-Generators that belong to a dedicated arc (pose/hands, show transport,
-front-of-house, MediaPipe) are listed below with a one-liner and a link to their
-guide rather than re-described here.
-
-## Generative & abstract
-
-- **`create_strange_attractor`** — Integrates a chosen ODE system (Lorenz /
-  Aizawa / Halvorsen) into a glowing, ever-drawing polyline. Reach for it when you
-  want deterministic, mathematically organic line-flow. The CPU-geometry sibling
-  of `create_growth_system` (L-systems) and `create_particle_flock` (boids).
-- **`create_sdf_field`** — A programmable signed-distance-field raymarcher in a
-  single GLSL TOP: a CSG tree of spheres / boxes / tori with smooth blending and
-  live camera/step/color controls. Reach for it for clean procedural 3D forms with
-  no geometry pipeline.
-- **`create_generative_art`** — The catch-all evolving visual: picks a technique
-  (reaction-diffusion, noise landscape, attractor, voronoi, fractal, custom GLSL)
-  and exposes a Speed knob. Reach for it when you want "something generative and
-  moving" without committing to a specific algorithm.
-- **`create_jfa_voronoi`** — A Jump-Flooding Voronoi / stained-glass cell pattern
-  in GLSL, with palette, seed-count, jitter and edge controls. Reach for it for
-  crisp cellular tessellation looks.
-- **`create_reaction_diffusion`** — A Gray-Scott reaction-diffusion GPU sim with
-  live F / K / Da / Db sliders and coral/spots/stripes/mitosis LUT presets. Reach
-  for it for organic, growing, biological patterning.
-- **`create_simulation`** — Reaction-diffusion, slime, or fluid-style feedback
-  trails with a Decay knob. Reach for it for drifting, advected, "alive" texture;
-  step up to `create_generative_art` for more procedural techniques.
-- **`create_volumetric_field`** — A stacked-slice fake-volumetric noise field
-  (smoke / nebula / ember / ice / toxic / mono) accumulated Beer-Lambert style.
-  Reach for it for atmospheric depth without a true raymarcher.
-- **`create_voxel_stack`** — An isometric voxel-stack renderer driven by any TOP's
-  luminance (Monument-Valley pastel ramps included). Reach for it for blocky,
-  data-driven 3D relief.
-
-## Particles & 3D
-
-- **`create_gpu_particle_field`** — A high-count GPU point field (up to ~262k)
-  simulated in feedback-TOP loops, optionally energised by audio or camera motion.
-  Reach for it for dense particle drift well beyond the CPU emitter.
-- **`create_particle_flock`** — The boids variant of the GPU field: separation /
-  alignment / cohesion with live knobs. Reach for it for flocking behaviour rather
-  than curl-noise/gravity drift.
-- **`image_to_particles`** — Turns an image into a particle field where each
-  particle's rest position and colour is its pixel; audio scatters and re-forms it
-  — the "image dissolves into points on the drop" look.
-- **`create_depth_displacement`** — Pushes a subdivided plane into true 3D relief
-  by a depth/luminance map. Reach for it for a 2.5D landscape that shifts with the
-  camera (use `create_depth_silhouette` for a flat 2D mask instead).
-- **`create_depth_pop_field`** — A depth-driven GPU POP scatter field that samples
-  a depth/mask TOP for displacement and emission; auto-spins a MediaPipe
-  segmentation chain if you give it no depth source.
-- **`create_depth_silhouette`** — Extracts a white-on-black body silhouette/mask
-  from a depth or video source, optionally colour-filled. Reach for it for
-  camera-reactive installations and masks.
-- **`create_depth_from_2d`** — Wraps the community TDDepthAnything v2 TOX to turn
-  any 2D image/video into a depth map (NVIDIA GPU only). Feed its output into the
-  depth tools above. Requires the user-installed TOX.
-- **`create_gaussian_splat_scene`** — Drops the community TDGS TOX and loads a
-  `.ply`/`.splat` Gaussian-Splat asset with camera binding. Requires the
-  user-installed TOX.
-
-## Audio-reactive
-
-- **`create_audio_reactive`** — The all-in-one: an audio analysis chain plus a
-  spectrum visual (bars / radial / particle / feedback / LED grid). Reach for it
-  when you want a finished audio-driven visual in one call.
-- **`create_transient_reactive`** — Splits audio into normalized `transient`
-  (percussion) and `sustain` (tonal floor) channels for `bind_to_channel`. Reach
-  for it to drive different visuals from hits versus pads.
-- **`create_chroma_reactive`** *(experimental)* — A 12-channel pitch-class chroma
-  vector for harmonic/key-aware binding.
-- **`create_energy_structure`** *(experimental)* — A self-calibrating song-structure
-  detector emitting energy, state (breakdown/build/drop) and edge pulses. Reach for
-  it to trigger scene changes off the arrangement, not just the beat.
-- **`create_midi_note_reactive`** — A MIDI-note → per-note velocity/trigger chain
-  with bindable `note0…noteN` channels. Reach for it to drive visuals per key.
-- **`audio_fingerprint_to_visual`** — Samples a few seconds of audio, fingerprints
-  it, and auto-picks and dispatches a matching generator. Reach for it as a
-  one-shot "match the music" starter.
-
-## Camera & motion reactive
-
-- **`create_optical_flow`** — A cheap CPU motion-energy field (bright = motion)
-  built from stock TOPs, a drop-in for displacement/particle chains. Not a true
-  dense-flow solver — reach for it for fast, no-CUDA motion texture.
-- **`create_blob_reactive`** — Tracks the *positions* of multiple blobs/hands in a
-  camera and exposes `blob0_x`, `blob0_y`, `blob0_size`, … for binding. The
-  per-object counterpart to single-value motion reactivity.
-- **`create_vector_lines`** — A pulse-driven image-to-vector-lines system (Trace
-  SOP) for clean line-art overlays. Intentionally non-realtime: you press
-  Vectorize to update.
-
-Body-pose reactivity lives in its own arc — see
-[Body & pose tracking](/guide/body-tracking):
-
-- **`create_pose_reactive`** — Derives scalar reactive channels (hand height, arm
-  openness, elbow angle, velocity) from a tracked pose for `bind_to_channel`.
-- **`create_pose_controlnet_driver`** — Renders a canonical OpenPose stick figure
-  TOP from a pose CHOP, ready to send to a ControlNet / Stable-Diffusion node.
-
-## Video & camera, scopes
-
-- **`create_video_scopes`** — A broadcast monitor (waveform / RGB parade /
-  vectorscope / histogram). See [Front-of-house dashboard](/guide/dashboard-foh).
-- **`create_waveform`** — A time-domain audio oscilloscope. See
-  [Front-of-house dashboard](/guide/dashboard-foh).
-- **`create_histogram_scope`** — A standalone luminance (and per-channel RGB)
-  histogram scope for any TOP, ready for preview or `bind_to_channel`.
-
-## Text & titles
-
-- **`create_text_overlay`** — Composites styled text over a visual (or on
-  transparency) — a finished title/lyric/credits layer ready for `setup_output`.
-- **`create_kinetic_text`** — A single word/line that flashes, pulses or slides,
-  the signature live-VJ lyric-flash. Reach for it for animated typography; bind the
-  LFO to a beat CHOP to lock flashes to tempo.
-- **`create_text_crawl`** — Multi-line scrolling ticker / vertical credits roll /
-  typewriter reveal. Reach for it for multi-line copy and continuous scrolling
-  (use `create_kinetic_text` for a single animated string).
-- **`create_text_3d`** — Extruded 3D glyphs with optional spin — title cards and
-  3D text drops. Use `create_kinetic_text` instead for flat 2D animated text.
-
-## Signature effects & looks
-
-- **`create_slit_scan`** — The "time-as-space" slit-scan look: each output row
-  samples a different past frame from a Cache ring buffer.
-- **`create_pixel_sort`** — Kim-Asendorf-style luminance-thresholded pixel-sort
-  streaks, with luma/hue/saturation sort keys.
-- **`create_ascii_render`** — Turns any TOP into a character-grid ASCII render
-  (phosphor-green CRT default).
-- **`create_dither`** — Retro ordered-Bayer / error-diffusion dithering to a 2/4/16
-  colour palette (Game-Boy duotone default).
-- **`create_chrome_blobs`** — A liquid-chrome / Y2K metaball generator with metal
-  tints and animated specular highlights.
-- **`create_kaleidoscope`** — Folds a source into N mirrored wedges with live
-  Segments / Rotation / Zoom / Center.
-
-## Colour & finishing
-
-- **`create_color_grade`** — A lift/gamma/gain + HSV + optional LUT finishing
-  stage — the "make the final output look graded" tool.
-- **`create_color_wheels`** — Three-way (shadows/mids/highlights) colour wheels
-  with per-channel lift/gamma/gain. Reach for it when `create_color_grade` is too
-  coarse.
-- **`apply_post_processing`** — Chains several distinct effects (bloom, glitch,
-  rgb_split, vignette, …) in series over a source. Reach for it to stack effects;
-  use a dedicated single-effect tool when you want its own exposed controls.
-- **`enhance_build`** — Scores a build and asks the LLM for allowlisted tool calls
-  to raise the weakest sub-scores (optionally auto-applying them).
-
-## Shaders & imports
-
-- **`import_isf_shader`** — Imports an ISF (`.fs`) shader as a GLSL TOP with
-  auto-generated controls (raw source, file, or URL).
-- **`import_shadertoy`** — Builds a GLSL TOP from a Shadertoy URL / ID / pasted
-  source, wiring iChannels and exposing Speed/Mouse.
-
-## Installations & studies
-
-- **`moodboard_to_system`** — Ingests 1–6 moodboard images and builds a matching
-  generative system (palette + motion + generator pick) via the vision LLM or a
-  deterministic grammar.
-- **`create_facade_mapping`** — A multi-projector architectural facade rig
-  (per-projector crop / corner-pin / edge-blend), shipped as a calibration
-  skeleton. See [Output & mapping](/guide/prompt-cookbook#output-mapping).
-- **`create_kinect_wall_harp`** — A projected wall instrument with laser-like
-  strings, two-hand wall-touch tracking, an OSC Kinect input mode and an internal
-  pluck synth. Reach for it when a depth camera and projector become the
-  instrument, and follow the [physical installations](/guide/physical-installations)
-  checklist before making live tracking claims.
-- **`create_test_pattern`** — A projector calibration/alignment source (grid,
-  crosshair, colour bars, ramp, circle-grid) with optional per-projector ID
-  overlay.
-
-## Performance & automation
-
-These build engines and lanes rather than visuals — see
-[Show timelines & setlists](/guide/show-timelines) for the full transport arc:
-
-- **`create_autopilot`** — A beat-driven auto-VJ that, every N beats, randomizes a
-  target's controls or cycles its stored cues.
-- **`create_automation_lane`** — Records a live parameter sweep into a ring buffer
-  over N bars, then loops it back on a bar-phase clock.
-- **`create_chop_recorder`** — Captures a source CHOP over a window and plays the
-  take back (persisted across reloads), ready for `bind_to_channel`.
-- **`compose_cue_list`**, **`create_setlist_runner`**,
-  **`create_phrase_locked_cue_engine`**, **`create_safety_blackout_chain`** —
-  covered in [Show timelines & setlists](/guide/show-timelines).
-
-## Body, hands & MediaPipe
-
-Covered in their own guides:
-
-- **`create_pose_tracking`**, **`create_pose_skeleton`**, **`create_body_reactive`**,
-  **`create_hand_hologram`** — see [Body & pose tracking](/guide/body-tracking).
-- **`setup_body_tracking`** and the face/hand/segmentation adapters — see
-  [MediaPipe adapters](/guide/mediapipe-adapters).
-
-## Output & mapping
-
-- **`setup_output`** — Routes a finished TOP to a window, NDI, Syphon/Spout,
-  recording or Touch Out — usually the last step.
-- **`create_multi_output`** — Fans a master TOP across N projectors with optional
-  edge-blend feathering. See [Output & mapping](/guide/prompt-cookbook#output-mapping).
-
-## See also
-
-- [Prompt cookbook](/guide/prompt-cookbook) — these generators in worked,
-  copy-paste prompts.
-- [Recipe gallery](/guide/recipes) — validated first-party starters for several of
-  them.
-- [Tools reference](/reference/tools) — the full, generated, per-tool reference
-  with every parameter.

package/mcps/tdmcp/docs/guide/glossary.md

@@ -1,123 +0,0 @@
----
-description: "Glossary for tdmcp, the TouchDesigner MCP server — MCP, the bridge, operators, TOP/CHOP/SOP and other TouchDesigner terms in plain language."
----
-
-# Glossary
-
-Plain-language definitions for the words you'll hear. You don't need to memorize
-these — the AI handles the technical side — but they help when reading previews or
-talking to other artists.
-
-## TouchDesigner basics
-
-**TouchDesigner (TD)**
-: The software you're building visuals in. It's "node-based": you connect little
-boxes (operators) to build an effect.
-
-**Operator (OP)**
-: One box/node in TouchDesigner. Each does one job — make noise, blur an image,
-read audio, etc. You wire them together.
-
-**Network**
-: A bunch of connected operators. Your whole visual is a network.
-
-**Parameter**
-: A setting on an operator — a number, a color, a toggle. The "knobs" you tweak.
-
-**Cook**
-: TouchDesigner's word for "compute this frame". A slow visual has expensive
-*cook times*; optimizing means making cooking cheaper.
-
-**Textport**
-: TouchDesigner's built-in console (menu **Dialogs → Textport and DATs**). You
-paste the one-line bridge installer there.
-
-## Operator families
-
-You'll see these short names in previews and explanations:
-
-**TOP**
-: Texture Operator — anything **image/video** (noise, blur, feedback, the picture
-itself).
-
-**CHOP**
-: Channel Operator — **numbers/signals over time** (audio, animation, MIDI, an LFO).
-
-**SOP**
-: Surface Operator — **3D geometry** (shapes, meshes, particles).
-
-**COMP**
-: Component — a **container** that holds a whole network, and the panels/knobs you
-perform with.
-
-**DAT**
-: Data Operator — **text and tables** (scripts, data, the bridge's callbacks).
-
-**MAT**
-: Material — how 3D surfaces are **shaded/lit**.
-
-## Performance & live terms
-
-**Feedback**
-: Feeding a frame back into itself so it evolves — the basis of tunnels, trails and
-many hypnotic looks.
-
-**LFO**
-: Low-Frequency Oscillator — a slow, automatic wave that moves a knob for you
-(gentle pulsing, sweeping, breathing).
-
-**Preset**
-: A saved snapshot of your knob settings you can recall instantly.
-
-**Cue**
-: A named look you can jump or smoothly *morph* to during a performance.
-
-**Tempo / BPM sync**
-: Locking movement to a musical tempo so it pulses on the beat.
-
-**GLSL / shader**
-: Code that runs on the graphics card to draw an image pixel-by-pixel — used for
-the fastest, most custom effects.
-
-## Inputs & outputs
-
-**OSC / MIDI**
-: Common ways to control parameters from hardware or other apps (a fader, a pad, a
-DAW).
-
-**DMX / Art-Net**
-: Protocols for controlling stage **lighting** and LED fixtures.
-
-**NDI / Syphon / Spout**
-: Ways to send your video **to other software** (e.g. OBS, Resolume) over the
-network or locally.
-
-**Projection mapping**
-: Warping your visual so it lines up with a physical surface a projector points at.
-
-## tdmcp terms
-
-**MCP (Model Context Protocol)**
-: The open standard that lets an AI assistant use external "tools". tdmcp is an
-MCP *server*.
-
-**The bridge**
-: The small piece that runs **inside TouchDesigner** so the AI can actually create
-and preview nodes. You switch it on once (see [Install](/guide/install)).
-
-**Recipe**
-: A pre-built, tested network you can ask for by name — see the
-[Recipe gallery](/guide/recipes).
-
-**Vault**
-: An Obsidian folder of notes tdmcp can read and write —
-recipes, setlists, moodboards, presets and a show diary.
-
-**`.mcpb`**
-: The single extension file (MCP Bundle) you install in Claude Desktop. The tdmcp
-server is bundled inside it. Formerly called `.dxt` — older `.dxt` files still
-install, but `.mcpb` is the current format.
-
-**`.tox`**
-: A TouchDesigner component file you can drag into any project — including a
-reusable copy of the bridge.