Skip to main content

Macros

The Macros tab in the side remote is where you create, edit, and run OSC (Open Sound Control) macros. Macros are scripted actions that drive Vū Studio over the network — start playback, switch scenes, adjust lighting, fire transitions, and more.

Macros are most commonly used with external automation tools (notably Bitfocus Companion running on a Stream Deck or other control surface) to give operators a one-button workflow in studios and experience spaces.

Opening the Macros Tab​

  1. Open the side remote (the slide-out panel on the right side of the Asset Library or Display Dashboard)
  2. Click the Macros tab at the top of the remote

The tab lists every saved macro for the current system. Each macro has a name and, for parameterized macros, a value input with arrow buttons. A pencil icon next to each macro opens it for editing.

Running a Macro​

For a simple macro (e.g. a named action like Two Shot):

  • Click the macro to run it

For a parameterized macro (e.g. one labeled test slider that accepts a numeric value):

  • Set the value using the arrow buttons or by typing into the input
  • The macro runs against the connected player using that value

Editing a Macro​

Click the pencil icon next to any macro to open its editor. From there you can:

  • Rename the macro
  • Set the OSC address pattern the macro sends
  • Configure arguments and value types (integer, float, string, etc.)
  • Add or remove steps if the macro should chain multiple commands

Save your changes to push them to the connected player.

Companion Integration​

Vū Studio's macros pair well with Bitfocus Companion. The typical workflow:

  1. Create the macros you want operators to fire (e.g. Open Showroom, Switch to Demo, Dim Lights, Fire Camera Move)
  2. In Companion, configure OSC actions that target Vū Studio's OSC listener with the same address patterns the macros are bound to
  3. Map each Companion button to the OSC action

This gives studio operators and event staff dedicated hardware buttons for the moments that matter, without needing to interact with the Vū Studio UI during a live show.

Tips​

  • Name macros after what the operator should be doing, not what they technically trigger ("Start Tour" beats "OSC /tour/start 1")
  • Keep parameterized macros for values that need to slide (volume, brightness, camera move speed); use named macros for binary triggers
  • Document the macro list somewhere your operators can see it (a printed cheat sheet on the control surface works well)