Your stepping stone to TouchDesigner
TouchDesigner is the industry standard for real-time visuals — and eventually worth learning properly. But it means a real install, a license decision, and six different kinds of operator to get oriented in before you've made anything. VerkLabs teaches the same underlying idea — typed nodes wired together, driving shading, motion and live behavior in real time — free, in your browser, no install. Work through this path, and the instincts, the vocabulary, and a lot of the individual building blocks will already feel familiar when you get to TD.
Materials & shading
closest match to TD's MAT familyStart here — this is the one place the vocabulary translates almost node-for-node. Every object gets its own graph, structurally a GLSL MAT: one network compiling to that object's shader, exactly the way every Geometry COMP in TD carries its own MAT.
| Later, in TouchDesigner | Here, in VerkLabs | Why it matters |
|---|---|---|
| PBR MAT / Phong MAT | RGBA · PBR Lighting | Same lighting math, plus six ready presets in RGBA → Lighting: Matte, Plastic, Rubber, Satin, Brushed Metal, Polished Metal — so you're not dialing metallic/roughness from scratch. |
| GLSL MAT | Math · f(x)→Float … Vectors · f(v,w,x,y,z)→Vec3 | The same write-your-own-shader escape hatch, one expression per node instead of one big block. |
| Constant MAT / color picker | RGBA · RGBA Color, HSLA · HSLA Color | Same idea. |
| Vertex displacement | Vertex Out · →Position, Vertex Out · →Position & Normal | TD splits this across a Point SOP and a GLSL MAT; here it lives in the same graph as shading. |
Textures & image effects
covers most of TD's TOP familyEvery 2D-image idea from TOPs has a node here — noise, blur, feedback, edge detection, color grading. The one thing missing is the standalone pipeline: in VerkLabs a texture always lives inside one shape's shader, not as something you can preview or route on its own.
| Later, in TouchDesigner | Here, in VerkLabs | Why it matters |
|---|---|---|
| Movie File In / Camera In | Source Data · Video, Image, Camera | Direct match. |
| Noise TOP | Animated Values · UV Simplex, UV Fractal Brownian, UV Turbulence Noise, UV Ridge Noise | The same four noise families, as separate nodes instead of one dropdown. |
| Feedback TOP | Source Data · Feedback, Feedback Depth | Direct match — last frame's render, read back as a texture. |
| Composite TOP | Mixing & Selecting · Alpha Blend, RGBA + RGBA, Screen, Overlay | Direct match — over/add/screen/overlay blending. |
Motion & control
a real strength, not just a CHOP substituteCHOPs are how TD turns an LFO, an audio band, or a timeline into motion. But wiring up a whole show — several tracks mixed together, visuals precisely timed off them — is usually something you build yourself, from Timeline CHOPs, Audio Device/File In CHOPs and custom logic tying it all together. VerkLabs gives you that as one authored surface from the start: the Runsheet.
Mix multiple audio tracks, then drive camera moves, parameters and on-screen overlays off exact frames or beats — all authored directly on one timeline, with no external sequencer or scripting required to get a synced show running. A Camera track · Move or Camera track · Path event sets your camera's position every frame, the same job an exported CHOP channel does driving a Camera COMP's transform in TD. A Params track sets a numbered parameter slot over time, the same way you'd bind a channel to a custom parameter. Audio, video, on-screen text and visibility all run on that same timeline, in sync — the carefully-timed, audio-reactive show TD can build, but doesn't hand you ready-made.
| Later, in TouchDesigner | Here, in VerkLabs | Why it matters |
|---|---|---|
| LFO / Wave CHOP | Animated Values · Square Wave, Sinus Wave, Sawtooth Wave | Direct match, feeding one shader input. |
| Audio File In + Analyze CHOP | Source Data · Microphone, Audio Track — Source Values · Frequency Volume | 10-band or 256-band frequency data from mic, mixdown, or a file — direct match. |
| MIDI In / OSC In | not yet | The biggest gap here — no live MIDI or OSC input today. |
| Drive any parameter from a timeline | the Runsheet | Reaches into camera, audio, parameters and overlays — not into the node graph itself. |
Geometry
thin, on purposeTD builds meshes procedurally, SOP by SOP. VerkLabs' Builder tool creates your geometry instead — the node graph only displaces the vertices a mesh already has, and drives point-based effects like particles through a small GPGPU-style state system.
| Later, in TouchDesigner | Here, in VerkLabs | Why it matters |
|---|---|---|
| Sphere / Grid / Box SOP | use the Builder tool | Primitives aren't node-based here. |
| Point SOP / Noise SOP | Vertex Out · →Position, State category | Closest match — a live per-vertex computation, not an editable point cloud. |
| Particle SOP | State · Particle Index, Var A/B | Build-your-own from the compute-state primitives. |
5 · What's waiting for you in TouchDesigner
Work through the steps above and you'll arrive at TouchDesigner already thinking in real-time nodes — typed sockets, shading, control signals, the habit of building complex behavior from small pieces. Here's what's genuinely TD-only, so you know what you're graduating to.
Tables, JSON/XML, Python scripting, OSC and MIDI I/O — TD's DAT family. VerkLabs' raw-expression nodes cover shader math only.
Procedural primitives, booleans, copy/extrude/subdivide — TD's SOP family, node by node.
Nesting whole sub-networks — cameras, geometry, on-screen control panels — as reusable objects with their own hierarchy.
MIDI controllers, OSC, DMX — patched straight into any parameter, for real hardware in a real room.
That's the real reason to make TouchDesigner your destination, not your starting point: everything you practice here — the node-graph instincts, the vocabulary, a lot of the individual building blocks — carries straight over, so this list is what's left to learn, not everything.
Why practice here before you install TouchDesigner
Open a link, start wiring nodes today. TouchDesigner means a real download and a license decision before you've made anything.
Share a project the way you'd share a CodePen — useful for classmates, a portfolio, or a teacher checking your work. A TD patch is a file you email or drop in a folder.
Point a webcam at yourself and start experimenting. TD's equivalent usually wants a Kinect or a paid plugin.
Mix multiple tracks and drive camera, parameters and overlays off exact frames or beats — no external sequencer or custom scripting required to get a synced show running.