This is separate from Parameter Automation.
Parameter automation is inbound control: external tool -> Baryon on
/baryon/control/<key>. Structure export is outbound structure data:
Baryon -> receiver.Defaults
Structure export does not use OSCQuery or Bonjour in v1. Those discovery tools
belong to parameter automation. For structure export, set the receiver host and
port manually.
Use OSC Data Out
- Open Baryon Desktop in Performer Mode.
- Open Control I/O.
- In OSC Data Out, leave Host as
127.0.0.1for a receiver on the same machine. - Leave Port as
9000, or choose the UDP port your receiver listens on. - Turn on the OSC Data Out switch.
- Start live input in Baryon. The OSC Data Out counter should begin showing sent frames.
- Adjust Modes only if your receiver needs fewer or more modal entries.
TouchDesigner Structure Monitor
Download the TouchDesigner structure monitor: baryon_osc_structure.tox Use it like this:- In Baryon, open Control I/O, enable OSC Data Out, and keep
127.0.0.1:9000for local TouchDesigner. - Drag
baryon_osc_structure.toxinto a TouchDesigner network. - Select the parent
baryon_osc_structurecomponent. - Keep OSC Data Port at
9000and Active on. - Start live input in Baryon.
- Select
baryon_osc_structureand pressito go inside the component, then watch theframe,global,coverage,material,modes,colors, andrawDATs update.
global for energy signals, modes for the modal entries, and colors
for per-mode RGB values. raw is mostly a debug table; it shows the incoming
OSC bundle as received, so it can look like a wall of numbers.
The useful monitor tables are:
The
colors DAT is a TouchDesigner-friendly view derived from exported modal
material colors. Use it when Baryon is in spectral color mode and you want a
compact per-mode palette table for instances, ramps, materials, or shaders.
The monitor is a reader, not a controller. It helps you inspect the OSC Data
Out stream before you wire the same data into instancing, geometry generation,
materials, or shader uniforms. To control Baryon from TouchDesigner, use the
parameter automation control surface
instead.
If you are working from a Baryon source checkout, you can rebuild the .tox
from TouchDesigner Textport:
baryon_osc_structure.tox beside the script and under
docs/public/downloads/touchdesigner/. The monitor layout is generated from
Baryon’s canonical OSC Data Out structure schema at build time; it is not a
runtime schema-discovery protocol. Before publishing an updated .tox, run:
- In Baryon, enable OSC Data Out and keep
127.0.0.1:9000. - In TouchDesigner, create an OSC In DAT.
- Set the OSC In DAT network port to
9000. - Start audio or live input in Baryon.
- Watch incoming
/baryon/...rows in the OSC In DAT. - Use DAT-to-CHOP, callbacks, or your own Python logic to turn the rows into geometry, instances, materials, or shader uniforms.
- Find the TouchDesigner computer’s LAN IP address.
- In Baryon, set Host to that TouchDesigner IP address.
- Keep Port aligned with the TouchDesigner OSC In DAT port, usually
9000. - Allow UDP traffic through the receiver machine’s firewall.
Terminal Smoke Test
Before opening TouchDesigner, you can prove the stream with a terminal receiver:127.0.0.1 and Port 9000.
The receiver prints frame sequence, source state, authority, global energy
signals, and the strongest modes. Use -- --port <port> if you changed the
Baryon port:
OSC Messages
Baryon sends/baryon/hello when the UDP port is ready, then sends
self-contained frame bundles while audio frames are available. Disable sends a
best-effort clear message.
Common addresses:
Value Semantics
Exported values are normalized modal/control signals, not calibrated acoustic measurements. For example,coefficient is a normalized modal amplitude,
coefficientEnergy is that coefficient squared for visual weighting, and RGB
values are material hints.
modeCount = 0 does not always mean silence. A frame can be active but
bandwidth-limited, in which case the coverage and authority messages explain
why no modes were exported.