Wintermute User Guide - commands

backup_restore_commands

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

Backup & Restore Commands Wintermute provides the following commands to backup and restore the state of the show flow (including all groups in the flow and flow queue, and their chat logs) and dynamic objects. object_backupall: object_restoreall: flow_backupall:

command_syntax

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

Command Structure Wintermute accepts commands from Qlab over UDP on port 53000; the general format of this commands is: (condition) command: parameter1 | parameter2 | parameter3... The number of parameters depends on the command; some are optional. If optional parameters are not used, the separating pipe -

deprecated_commands

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

The following commands are described for completeness only - they remain in Wintermute for backwards compatibility, and should not be used going forward. zone_test: {name} | {condition} Returns an OSC command in the form {name}_true or {name}_false depending on the truth value of the condition.

parsing

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

Parsing & Evaluation This page outlines what happens when a command is executed by Wintermute: Naming & Reserved Characters Wintermute uses special characters to navigate the text it executes; as such, when naming Zones, Nodes, Variables, or UIDs or parameters of Dynamic Objects, you should avoid the following characters:

start

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

Syntax Commands with the wrong number of parameters will be rejected, but parameter fields in italics and flags are optional. IMPORTANTTo understand how Wintermute handles commands, read these pages on command syntax and parsing Wintermute also allows the in-lining of variable references and references to

timer_commands

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

In a situation with universal timing – thus, all audience groups move in different tracks or sections but on the same basic timing loop, you should use the timer functionality built into the Flow system. However, if your show works another way, you can address the Flow timer directly with these commands