Pathmaker
Introduction to TouchDesigner
A practical introduction to TouchDesigner's node-based workflow for building real-time interactive visuals, audio-reactive systems, and live performance tools. No prior coding required.
About This Course
TouchDesigner is a node-based visual programming environment used by artists, designers, and technologists to create real-time interactive media. It powers live visuals, installations, data-driven graphics, generative art, and performance tools.
Rather than writing conventional code, you connect nodes — each one performing a specific operation — and build systems by defining how information flows between them.
This class teaches you the fundamentals of that workflow across TouchDesigner's five core operator families: TOPs for image and video, CHOPs for data and signals, SOPs for 3D geometry, MATs for materials and rendering, and the output tools that bring it all together.
By the end, you'll be able to build working real-time systems and have a clear foundation for more advanced practice.
What You'll Learn
- 1Navigate the TouchDesigner interface with confidence
- 2Understand node-based thinking and how operator families relate to each other
- 3Build real-time image and video compositions using TOPs
- 4Connect audio and data signals to visual parameters using CHOPs
- 5Create and modify 3D geometry using SOPs
- 6Output finished work to a screen, window, or file
Week by Week
The Interface and Node-Based Thinking
Before building anything in TouchDesigner, you need to understand how the environment works. TouchDesigner is not a timeline-based tool like video editors, and it's not a scripted system like conventional programming.
It's a network: a collection of nodes that each do one thing, connected together so that data flows from one to the next. Understanding this mental model is the most important thing you'll do in this class.
Everything else builds on it.
Explore this week's curriculum
Key concepts
Node: The fundamental unit in TouchDesigner. Each node performs a single operation — generating an image, processing audio, transforming geometry. Nodes are connected together to build systems.
Operator (OP): TouchDesigner's term for a node. Operators are organized into families based on what kind of data they work with: TOPs (textures/images), CHOPs (channels/signals), SOPs (3D geometry), DATs (text/data), COMPs (components/containers).
Network: A collection of connected operators. Building in TouchDesigner means building networks — defining how data flows from one operator to the next.
Real-Time: TouchDesigner processes and renders everything live, every frame. There is no render queue or export step during development — what you see is the output as it's being computed.
Parameters: The settings of each operator, visible in the Parameter Panel on the right. Parameters control what an operator does and can be driven manually, by expressions, or by other operators.
Studio activities
Build Your First Network
Create a simple working network using three connected operators to get familiar with the interface.
- Open TouchDesigner. Take 5 minutes to explore the interface without touching anything — locate the Network Editor, the Parameter Panel, the Palette, and the toolbar.
- Press Tab to open the OP Create Dialog. Create a Noise TOP (Texture Operator).
- Add a Level TOP and connect the output of the Noise TOP into its input. Adjust the Brightness and Contrast parameters.
- Add a Out TOP and connect the Level TOP into it. This sends the image to the viewer.
- Change parameters on the Noise TOP (scale, period, type) and watch the output update in real time.
- Save the file as 'week1_first_network.toe'.
Success criteria
A saved .toe file with a working 3-node network that produces a visible, adjustable output.
Reflection
- What felt intuitive about the node-based workflow? What felt unfamiliar?
- How does changing a parameter upstream (on the Noise TOP) affect everything downstream?
Study guidance
- Resist the urge to learn every operator immediately. Focus on understanding the flow: data enters a node, is processed, and exits. That logic applies to every operator in the software.
- The OP Create Dialog (Tab key) is your primary tool for adding nodes. Get comfortable with it early.
- TouchDesigner's free non-commercial license is fully functional for learning. You don't need the commercial version to complete this class.
Discuss with Professor Reed
Choose a question to discuss with Professor Reed. Copy it and paste it into your conversation with him. The copied text includes this week's lesson and assignment; add your own questions or explain where you are stuck.
How does node-based thinking differ from how you've worked in other software?
What would it mean for a system to process everything 'in real time' — what constraints and possibilities does that create?
What felt intuitive about the node-based workflow? What felt unfamiliar?
How does changing a parameter upstream (on the Noise TOP) affect everything downstream?
Ask me one question at a time to check my understanding, then explain any gaps.
Help me plan this assignment without doing the work for me.
TOPs: Working with Images and Video
TOPs — Texture Operators — are the most commonly used operator family in TouchDesigner. They handle anything that is or becomes an image: video files, live camera input, generated patterns, compositing, color grading, feedback effects, and more.
If you're using TouchDesigner for visual work, you'll be spending a lot of time in TOPs. This lesson introduces the core TOPs and teaches you to build a visual compositing network.
Explore this week's curriculum
Key concepts
TOP (Texture Operator): An operator that processes image data — pixels. TOPs generate images (Movie File In, Noise, Constant), transform them (Transform, Flip), composite them (Over, Multiply, Add), and output them (Out, Render).
Composite: Combining two or more images together. TouchDesigner's Composite TOP and Over TOP are the primary tools for layering, blending, and mixing visual elements.
Feedback Loop: A network structure where an operator's output is fed back into its own input (via a Feedback TOP), creating accumulation, trails, echo, and other time-based visual effects.
Resolution: The pixel dimensions of a TOP's output. Resolution can be set per-operator and affects both visual quality and performance. Keeping resolution low during development is good practice.
Studio activities
Build a Video Compositing Network
Create a layered visual composition using at least 4 TOPs, including one composite operation and one color treatment.
- Create a Movie File In TOP and load any video file or image. If you don't have one, use a Noise TOP as your base layer.
- Add a Transform TOP and experiment with position, rotation, and scale parameters.
- Create a second visual source — another Noise TOP with different settings, or a second Movie File In.
- Add an Over TOP or Composite TOP and connect both sources. Adjust the blend mode and opacity.
- Add a Level TOP after the composite to adjust brightness, contrast, and gamma.
- Add an Out TOP at the end of the chain.
- Try adding a Feedback TOP between two nodes to create a trail or echo effect.
- Save as 'week2_tops_composition.toe'.
Success criteria
A saved network with at least 2 visual sources, one composite operation, one color adjustment, and a visible output.
Reflection
- How does the order of operations in a TOP network affect the final output?
- What happened when you introduced the Feedback TOP? How did the output change over time?
Study guidance
- Use the Viewer Active button (the small eye icon on a node) to see its output without interrupting the network flow.
- TOPs process everything as GPU textures. This means complex networks can run at high frame rates, but GPU memory is a real constraint — keep resolutions appropriate to your output.
- Movie File In TOP can load video files or image sequences. It's one of the most versatile TOPs for bringing in external media.
Discuss with Professor Reed
Choose a question to discuss with Professor Reed. Copy it and paste it into your conversation with him. The copied text includes this week's lesson and assignment; add your own questions or explain where you are stuck.
What's the difference between generating an image (Noise TOP) and processing one (Level TOP)?
How would a feedback loop change the feel of a visual system over time?
How does the order of operations in a TOP network affect the final output?
What happened when you introduced the Feedback TOP? How did the output change over time?
Ask me one question at a time to check my understanding, then explain any gaps.
Help me plan this assignment without doing the work for me.
CHOPs: Data, Signals, and Audio Reactivity
CHOPs — Channel Operators — handle numerical data over time: audio signals, sensor input, oscillators, mouse and keyboard input, timers, and more. On their own, CHOPs don't produce images.
What they do is drive parameters — using a CHOP's output to control the position, scale, color, or speed of other operators. This is how you make systems that respond: to audio, to user input, to time, to external data.
CHOPs are what make TouchDesigner feel alive.
Explore this week's curriculum
Key concepts
CHOP (Channel Operator): An operator that processes time-based numerical data as channels — streams of values over time. CHOPs generate signals (LFO, Audio File In), process them (Math, Filter), and export them to other operators' parameters.
Channel: A single stream of values over time within a CHOP. An Audio File In CHOP might output a 'left' and 'right' channel. An LFO CHOP outputs a single oscillating channel.
Export: The mechanism for connecting a CHOP's output to another operator's parameter. You can drag a channel onto a parameter field, or use the Export CHOP for more complex routing.
Audio Analysis: TouchDesigner's Audio Spectrum and Audio Filter CHOPs allow you to extract frequency information from audio — bass, midrange, treble — and use each band to drive different visual parameters.
LFO (Low Frequency Oscillator): A CHOP that generates a repeating wave (sine, square, triangle, ramp). Used to create continuous, rhythmic animation without keyframing.
Studio activities
Build an Audio-Reactive Visual
Connect an audio source to a visual parameter using CHOPs to create a system that responds to sound.
- Start with your Week 2 composition or create a new simple TOP network (Noise TOP → Level TOP → Out TOP).
- Add an Audio File In CHOP and load an audio file, or use an Audio Device In CHOP to use your microphone.
- Add an Audio Spectrum CHOP after the audio source to analyze frequency content.
- Add a Math CHOP to remap the output values to a useful range (e.g., 0 to 1).
- Drag the output channel from the Math CHOP onto the Brightness parameter of the Level TOP.
- Play the audio (or make noise into the mic) and watch the visual respond.
- Add a second CHOP chain driving a different parameter — scale, position, or color.
- Save as 'week3_audio_reactive.toe'.
Success criteria
A saved network where at least two visual parameters respond visibly and in real time to an audio input.
Reflection
- Did the audio-reactive system feel mechanical or expressive? What would change the feeling?
- What other data sources (beyond audio) could you imagine routing through CHOPs?
Study guidance
- The CHOP Viewer shows you the channel data as a waveform. Always check what a CHOP is outputting before connecting it to a parameter — a signal with unexpected range can produce extreme results.
- The Math CHOP is one of the most useful operators in the family. Use it to remap, scale, and offset channel values to the range your target parameter needs.
- Audio reactivity works best when you analyze the audio (Audio Spectrum CHOP) and route specific frequency bands to specific parameters — bass to scale, high frequencies to brightness, etc.
Discuss with Professor Reed
Choose a question to discuss with Professor Reed. Copy it and paste it into your conversation with him. The copied text includes this week's lesson and assignment; add your own questions or explain where you are stuck.
What's the difference between animating a parameter manually and driving it with a CHOP?
How would you use a CHOP to make a visual element respond differently to bass frequencies versus high frequencies?
Did the audio-reactive system feel mechanical or expressive? What would change the feeling?
What other data sources (beyond audio) could you imagine routing through CHOPs?
Ask me one question at a time to check my understanding, then explain any gaps.
Help me plan this assignment without doing the work for me.
SOPs: 3D Geometry and Space
SOPs — Surface Operators — handle 3D geometry: meshes, point clouds, primitives, deformations, and transformations in three-dimensional space. If you want to work with 3D objects, particle systems, generative geometry, or spatial compositions in TouchDesigner, SOPs are where that work begins.
This lesson introduces the core SOP operators and teaches you how to generate geometry, modify it, and render it using the Render pipeline.
Explore this week's curriculum
Key concepts
SOP (Surface Operator): An operator that generates or modifies 3D geometry — meshes, curves, point clouds, and primitives. SOPs output geometry data, not images. To see a SOP, you need to render it using a Camera COMP, Light COMP, Geometry COMP, and Render TOP.
Primitive: A basic geometric shape: box, sphere, cylinder, grid, torus. Primitive SOPs are the starting points for most 3D work in TouchDesigner.
Point: The fundamental unit of 3D geometry. A mesh is made of points connected by edges and faces. Point positions can be modified by SOPs and driven by CHOPs for animation and deformation.
Render Pipeline: The chain of COMPs and TOPs required to display 3D geometry: Geometry COMP (holds the SOP), Light COMP (illuminates the scene), Camera COMP (defines the viewpoint), and Render TOP (outputs the rendered image).
Noise SOP: Displaces the points of a geometry based on a noise function — creating organic deformation, wave-like surfaces, and generative shape variation.
Studio activities
Build and Render an Animated 3D Scene
Set up a complete render pipeline and animate a piece of geometry using a SOP and a CHOP.
- Create a Geometry COMP. Inside it, add a Sphere SOP.
- Add a Noise SOP after the Sphere SOP and connect them. This displaces the sphere's surface.
- Go back to the root network. Add a Light COMP and a Camera COMP.
- Add a Render TOP and assign it the Geometry COMP, Light COMP, and Camera COMP in its parameters.
- Add an Out TOP and connect the Render TOP. You should now see your 3D sphere in the output.
- Go back inside the Geometry COMP. Add an LFO CHOP and connect it to the Amplitude parameter of the Noise SOP.
- Adjust the LFO rate and range to create a rhythmic deformation.
- Optional: apply a Phong MAT to the Geometry COMP for a surface material.
- Save as 'week4_3d_geometry.toe'.
Success criteria
A saved network with a fully rendered 3D scene containing animated geometry driven by a CHOP.
Reflection
- How does the render pipeline model (camera, light, geometry, render) relate to how physical cameras and studios work?
- What would happen if you drove the Noise SOP with the audio signal from Week 3 instead of an LFO?
Study guidance
- SOPs require a render pipeline to produce an image. If you're not seeing output, check that your Geometry COMP, Camera COMP, Light COMP, and Render TOP are all connected and configured.
- MATs (Material Operators) define the surface appearance of geometry: color, texture, reflectivity, transparency. A Phong MAT is the simplest starting point.
- You can drive SOP parameters with CHOPs — connecting an LFO or audio signal to the Noise SOP's amplitude creates animated, reactive geometry.
Discuss with Professor Reed
Choose a question to discuss with Professor Reed. Copy it and paste it into your conversation with him. The copied text includes this week's lesson and assignment; add your own questions or explain where you are stuck.
What's the conceptual difference between working in 2D (TOPs) and 3D (SOPs + render pipeline)?
How would you combine the CHOP skills from Week 3 with a 3D scene?
How does the render pipeline model (camera, light, geometry, render) relate to how physical cameras and studios work?
What would happen if you drove the Noise SOP with the audio signal from Week 3 instead of an LFO?
Ask me one question at a time to check my understanding, then explain any gaps.
Help me plan this assignment without doing the work for me.
Output: Finishing and Presenting Your Work
TouchDesigner is primarily a tool for live output — performances, installations, interactive displays, and events. But knowing how to properly configure, optimize, and output your work is a distinct skill set.
This final lesson covers the practical side: sending output to screens and projectors, recording output to video, performance optimization basics, and how to think about building projects that are reliable in a live context.
Explore this week's curriculum
Key concepts
Window COMP: A component that opens a borderless, fullscreen output window on any connected display. The primary tool for sending TouchDesigner output to a screen or projector in a live context.
Movie File Out TOP: Records the output of any TOP to a video file on disk. Used to export finished work, create loops, or capture performance documentation.
Performance Mode: A setting that hides the TouchDesigner interface and focuses system resources on rendering. Activated in the Perform menu or by pressing F1.
Cook Time: The amount of time TouchDesigner spends processing a network each frame. Monitoring cook time (visible in the bottom toolbar) is the primary way to identify performance bottlenecks.
Component (COMP): A container operator that holds a sub-network. Using COMPs to organize your project into logical modules — audio, visuals, output — makes larger projects manageable and easier to debug.
Studio activities
Final Project: Complete Interactive System
Build a complete, output-ready TouchDesigner project that integrates at least two operator families and produces a polished real-time output.
- Choose a concept: an audio-reactive visual, an animated 3D scene, a camera-driven composition, or a generative pattern system.
- Plan your network on paper first: what operator families will you use? What data flows where?
- Build the network, using COMPs to organize distinct sections (e.g., one COMP for audio analysis, one for visuals).
- Connect a data source (audio, LFO, mouse input) to at least two visual parameters.
- Set up a Window COMP for fullscreen output.
- Test at your target resolution and check cook time. Optimize if frame rate drops below 30fps.
- Record a 30-second clip using a Movie File Out TOP.
- Save the final project as 'week5_final_project.toe'.
- Write a short note (3-5 sentences) describing what the system does and what you'd develop further.
Success criteria
A saved project file, a 30-second recorded output, and a brief written description of the system.
Reflection
- What was the most challenging part of building a complete, output-ready system?
- What would you explore next in TouchDesigner?
Study guidance
- Build your final project with output in mind from the start. Know the resolution, frame rate, and display configuration before you begin designing.
- If performance is slow, reduce resolution first. Going from 1920x1080 to 1280x720 often has a dramatic effect on frame rate with minimal visible quality loss.
- For live performance, keep your network as simple as possible. Complexity that works fine on a powerful workstation may struggle on a venue machine.
Discuss with Professor Reed
Choose a question to discuss with Professor Reed. Copy it and paste it into your conversation with him. The copied text includes this week's lesson and assignment; add your own questions or explain where you are stuck.
What's the difference between building something for a screen installation and building something for a recorded video?
What would you need to consider if you were presenting this work live in front of an audience?
What was the most challenging part of building a complete, output-ready system?
What would you explore next in TouchDesigner?
Ask me one question at a time to check my understanding, then explain any gaps.
Help me plan this assignment without doing the work for me.
Topics Covered
More in This Track
Repair, Reuse, and Material Recovery
Study repairability, disassembly, waste streams, and the design of another useful life.
Biodesign and Material Cultivation
Explore biological materials through accessible making, observation, and documented material testing.
Information Design and Data Storytelling
Turn researched evidence into visual explanations with clear sources and uncertainty.
Ready to begin?
Start your personalized curriculum today — free to try, no credit card needed.