Three layers, not three competitors
A live audiovisual workflow on macOS or Windows usually has three layers running at once:
- The runtime layer — what produces the visual source. Baryon sits here: a cymatic primitive that renders live sound as real-time geometry.
- The host environment — what runs the show. Resolume, TouchDesigner, mapping software, and broadcast tools sit here.
- The bridge layer — what moves rendered frames between processes. Syphon, Spout, NDI, and similar protocols sit here when a desktop release supports them.
Most “tool comparison” questions are really layer questions in disguise.
When the missing layer is compute
Reach for Baryon when the source itself is the missing piece — when you need a live render that is structurally tied to the audio rather than decorating it. The runtime runs in the browser for evaluation and moves to desktop for performance use.
When the missing layer is environment
Reach for Resolume when the missing piece is clip launching, layering, effects, and live show control. Reach for TouchDesigner when the missing piece is a custom node graph for installations, technical systems, or bespoke routing. Both are environments — the place a show is composed, not a source on their own.
When the missing layer is the bridge
Syphon, Spout, and NDI are not product categories; they are wires. They matter because bridges can let a desktop render speak to a host environment as a live source instead of an exported file. Treat each bridge as a support question for the current desktop release, not as proof that the runtime itself is useful.
How to decide
- If the missing piece is a sound-tied source, evaluate Baryon.
- If the missing piece is show control, evaluate Resolume or a host environment.
- If the missing piece is custom system logic, evaluate TouchDesigner.
- If the missing piece is moving frames between applications, look at Syphon, Spout, or NDI support on your platform.