E-Stop
The round red button in the bottom-left corner of every page is the e-stop. When it’s engaged it glows, and the server stops passing show control.
It’s on screen on every page, for everyone, whether or not you’re allowed to press it.
What it stops
Section titled “What it stops”While engaged:
- The router drops everything. Messages arriving from your devices are discarded rather than routed on. Because macro triggers are evaluated after routing, an incoming OSC message can’t fire a macro either.
- Haze watch stops running its triggers. Each trigger sends its configured e-stop message and holds in the
eStopstate. The trigger loop won’t start while the e-stop is engaged.
Engaging and disengaging are both written to the Events log, so there’s always a record of when the -stop went on and off.
Who can press it
Section titled “Who can press it”Engaging and disengaging are separate permissions:
settings -> global -> eStop -> engagesettings -> global -> eStop -> disengage
Stopping the show and restarting it are different trust decisions. It’s entirely reasonable to let everyone in the room stop the show while keeping the decision to resume with one key individual.
If you press the button without the matching grant, you’ll get a message saying so and nothing happens.
Other ways to fire it
Section titled “Other ways to fire it”From a macro. The System command type has an Emergency Stop action. Put it on the end of a macro and any trigger you like becomes an e-stop trigger.
From the OSC API. Two addresses:
/sndwrks/server/v1/estop/engage/sndwrks/server/v1/estop/disengageSee the OSC API reference for the details.
As a macro trigger. The Server Event trigger fires on eStopEngage and eStopDisengage, so you can hang your own behaviour off the e-stop — kill a house-light look on engage, restore it on disengage.
From the license. If a subscription lapses long enough, the server engages the e-stop itself. See Cloud — the countdown to that is not subtle, and you’ll have seen it coming for a while.
Engage on startup
Section titled “Engage on startup”Settings → Global → E-Stop Settings has a checkbox that engages the e-stop whenever the server boots.
Worth turning on if you’re running haze control. A server that comes back from a power cut and immediately starts hazing an empty room because a trigger threshold says so is not the surprise you want.