TouchDesigner is strong at real-time interaction: audio analysis, feedback, masking, multi-screen compositing, and protocol output. Pixel LED Animator 3 is strong at generating the visual in the first place: 145 effect generators, palettes, keyframes, text, and image overlays.
Connecting them gives you both. Pixel LED Animator sends its live preview as an NDI or Spout2 source, and TouchDesigner receives it as a TOP. From there you can make the animation react to sound, multiply it across a wall, or route it into a larger show network.
Which Input to Use
| NDI In TOP | Spout In TOP | |
|---|---|---|
| Platform | Windows, macOS, Linux receivers | Windows only |
| Transport | Network video | Local GPU texture share |
| Same PC | Works | Works, lower latency |
| Second PC | Works | Not applicable |
| Setup | Firewall and discovery | None |
| Best for | Distributed setups, laptops, media servers | One Windows machine, tight live timing |
Start with Spout if both applications run on the same Windows PC. Use NDI when TouchDesigner runs on a different machine or when several systems need the same source.
Step 1: Start the Output in Pixel LED Animator
- Start playback so the preview is moving.
- Set the preview output strip to Spout or NDI, or open the streaming window, choose the matching protocol, and press Start Streaming.
- Confirm the sender name:
Pixel LED Animator 3.
The app sends RGB frames at the canvas resolution. If the canvas is 64 x 32, TouchDesigner receives 64 x 32; it does not receive a scaled 1080p image. Decide the working resolution before building the network.
Step 2: Receive the Source in TouchDesigner
NDI In TOP
- Add an NDI In TOP.
- Select
Pixel LED Animator 3in the source parameter. - Set the resolution to Native while testing, then lock it to the matrix size.
Spout In TOP
- Add a Spout In TOP.
- Select
Pixel LED Animator 3as the sender. - Confirm the resolution in the node’s info popup.
Add an Info CHOP to the input TOP to watch frame rate, resolution, and dropped frames. If the frame rate is unstable before you add any effects, fix the source or network first.
Step 3: Build a Clean Processing Chain
A simple, reliable chain looks like this:
NDI In / Spout In → Null → Level → Composite → Out
Use the Null TOP as the single master input. Every downstream branch references the Null, so you can swap Spout for NDI without rebuilding the network.
Then add only what the show needs:
- Level TOP for exposure, gamma, and opacity.
- Transform TOP for position, scale, and rotation.
- Feedback TOP with a Composite TOP for trails and motion smear.
- Chroma Key TOP if you need transparency; the source has no alpha.
- Cache TOP to smooth short network hiccups.
- Audio In CHOP → Math CHOP → Null CHOP → export to drive level, scale, or color from the music.
For pixel-accurate work, set the input TOP to Nearest filtering. Smooth filtering is useful for organic looks but destroys sharp LED edges.
Step 4: Output to LEDs or a Screen
TouchDesigner can output through its own DMX/Art-Net operators, a media server, or a direct video output. Pick the path that matches the receiver:
- Art-Net/sACN controller: keep the pixel count and universe mapping identical to the controller configuration.
- Media server or Resolume: send NDI or Spout onward instead of re-encoding.
- LED processor: output a video signal at the processor’s native resolution.
- Preview only: use a Window COMP and keep the render resolution at the matrix size.
If TouchDesigner is only doing audio reactivity, send the processed result back to the controller over Art-Net rather than adding a second video encode.
Step 5: Keep Performance Predictable
NDI at 1920 x 1080 and 60 FPS is a heavy stream. A matrix preview rarely needs that.
- Match the source resolution to the matrix, not to the monitor.
- Use 30 FPS for matrix work unless the effect depends on fast motion.
- Prefer Spout for same-machine work.
- Disable unneeded TOPs and keep the network shallow.
- Test with the real controller attached before the show.
Troubleshooting
| Problem | Fix |
|---|---|
| No NDI source listed | Check the NDI runtime, firewall, subnet, and discovery; restart both apps |
| Spout sender missing | Spout is Windows-only; confirm the Spout2 runtime and that the output strip is not Off |
| Black frame in TouchDesigner | Start playback and press Start Streaming in the app |
| Stutter or dropped frames | Lower resolution or FPS, switch to Spout, simplify the network |
| Soft pixel edges | Set the input TOP filtering to Nearest |
| Colors shifted | Check the Level TOP and avoid applying gamma twice |
FAQ
Can TouchDesigner send the result to WLED? Yes, through Art-Net output to WLED configured as an Art-Net receiver. DDP is not a standard TouchDesigner operator, so Art-Net or sACN is the safer route.
Do I need an NDI license? The NDI runtime is free to install and use. Developers shipping NDI support inside a product have separate SDK licensing terms.
Can the two applications run on different computers? Yes, over NDI. Both machines need to be on the same network and allowed through the firewall.
Does the source include alpha? No. Pixel LED Animator sends RGB. Use a Chroma Key TOP or a luma key in TouchDesigner when you need transparency.
Can I use this for projection mapping? Yes. Use TouchDesigner’s mapping tools to warp the generated visual onto the surface, then output to the projector or LED processor.
Explore Pixel LED Animator 3 · See all integrations · Read the OBS workflow · Buy the lifetime license
