Macros

A patch that sounds good is often a patch with thirty parameters, only five of which you actually want to move. Macros are how you promote those five.

A macro in the Macros panel is a 0 to 1 control assigned to a parameter elsewhere in the patch. Moving it moves the target through its authored control range and taper.

Macros are also the bridge to your DAW. A patch can hold eight macros, in slots 1 to 8, and those slots are what the host sees as automatable plugin parameters. Anything you want to automate from the arrangement needs to be on a macro.

The old Macro graph node is deprecated and no longer appears in Add Node. Existing patches that contain it remain loadable for compatibility, but new patches should use the Macros panel for parameter bindings and host automation.

Assigning a Parameter

1. Right-click the parameter row on a node card.
2. Choose Assign Macro.

That creates a macro on the next free slot, named after the parameter, and binds the parameter to it. The macro appears in the Macros panel where you can rename it and rearrange its display position. In the current beta UI, assigning another parameter creates another Macro rather than adding a second target to the existing one.

To undo a binding, right-click the parameter again and choose Remove Macro.

Once eight macros exist, Assign Macro is unavailable until you free a slot.

What Can Be Assigned

Not every parameter can take a macro. A parameter is unavailable when:

• it is already driven by a cable — a patched input wins, and a macro would be fighting it
• it is already bound to another macro
• it uses an unsupported control shape, such as a toggle, an integer control, or a mode that changes the node's runtime shape — a filter's Topology is one example
• it is a continuous control whose range is not a finite numeric span

Some fixed option menus are assignable. When they are, the Macro steps through their choices rather than sweeping continuously.

The first case is the one that catches people out. If Assign Macro is missing from a parameter you expected to promote, look for an incoming cable on that input first.

Macros and Polyphony

Bindings inside a Polyphony Zone resolve to every running copy of the voice, so one macro moves the same parameter across all sounding voices rather than a single one. Assign from inside the Zone and the macro behaves as you would expect when you play a chord.

Automating From the DAW

Each macro occupies a numbered host parameter slot, so your DAW shows eight automatable controls. Draw automation, assign a hardware controller, or record a knob sweep, and the macro moves every parameter bound to it.

Because the host addresses macros by slot, keep a slot meaning the same thing once you have written automation against it. Rearranging Macros in the panel changes only their display order; deleting one and later reusing its numbered slot changes what existing automation controls.

Choosing Good Macros

• Promote the controls you reach for while listening, not the ones you set once and forget.
• Name macros for what they do to the sound — "Brightness", "Space" — rather than for the parameter underneath.
• Leave a slot free for a performance control you discover while playing, such as a mute or effect amount.

Rules of Thumb

• Eight macros per patch, and they are the only parameters the host can automate.
• A parameter driven by a cable cannot also be driven by a macro.
• Assign with right-click → Assign Macro on the parameter row.
• Macro bindings inside a Zone apply to every voice.
• Rearranging the panel does not change host slots. Deleting and reusing a slot does.