The short answer
Reach for Baryon when the source is the thing you care about — when the geometry has to follow the music, not decorate it. Reach for a host environment like Resolume or TouchDesigner when the missing piece is clip launching, layering, mapping, or full show control. Syphon and Spout are bridge requirements, not the source of the visual idea.
Why a runtime instead of a decorative source
Generic audio-reactive sources map levels to motion. Routed over Syphon or Spout, that signal is still decorative — it stops mattering the second the music gets quiet. A cymatic runtime treats audio as structure, so the source stays legible regardless of dynamics. Routing then has something worth carrying.
A practical pipeline
- Audio enters Baryon — mic, line, DAW send, or loopback.
- The runtime resolves it into a real-time cymatic field.
- The render leaves Baryon through whatever output path the current desktop release supports.
- Your host environment composites, cues, projects, or captures from there.
When this is the wrong call
If you do not already have a host environment, Baryon alone will not run a show. It is intentionally a primitive, not an environment. Pair it with whatever your pipeline already uses for clip launching, mapping, and broader cueing.
Evaluation checklist
- Does the source need to be structurally tied to the audio?
- Are you already running a host environment for the broader show?
- Do you need live GPU output or a network video bridge rather than rendered files?
- Will the browser be the easiest way to evaluate, with the desktop app taking over for live routing?