Wintermute User Guide - concepts:macros

macro_variables

Anonymous (anonymous@undisclosed.example.com) — 2025-05-17T20:51:58+00:00

Macro Variables Macro variables are variables that are local to a particular macro on a particular node. Unlike the more complex variable system that sits under zones, they are simply represented by name/value pairs, like: thisVar=cheese They can be set one of three ways:

midi_trigger

Anonymous (anonymous@undisclosed.example.com) — 2025-05-17T20:51:58+00:00

MIDI Macro Triggers The trigger on a macro attached to a MIDI In port consist of two parts - the data and the mask. The mask defines which parts of an incoming MIDI packet need to match the data for the trigger to fire. The mask is derived automatically from the data given for the trigger - the more data, the more specific the mask.

parser_directives

Anonymous (anonymous@undisclosed.example.com) — 2025-05-17T20:51:58+00:00

Macro Parser Directives Parser directives are commands that can only be run from within macros. They all need to start with # and are used for controlling the flow of commands: #label: A label that can be used by the jump commands as opposed to a delay target

start

Anonymous (anonymous@undisclosed.example.com) — 2025-05-17T20:51:58+00:00

Macros If you've spend any time with this documentation, you should have a sense of how most things can be achieved by shuttling commands back and forth between Wintermute and Qlab. So far so good! Macros may seem fiddly, but once you've got the hang of them, they will make many tasks easier - think of them as mini cue lists that run within Wintermute.