Loading...
What a position represents in Buttons, how surfaces fit into it, and how the editor stays separate from the live workspace.
Create a workspace for one operator, describe and size it, assign surfaces, and apply the configuration.
Place elements on a position canvas and choose between buttons, sections, shift, folder, popover, router, shared and role sections.
Create a button on a position canvas, give it an action, test it in the editor, and add feedback that reflects real device state.
Find the ready-made buttons, sections and popovers a connection module supplies and drag them onto a position canvas.
Run several steps per press, react to hold and click patterns, group or condition actions, generate repeater buttons, and use encoders.
Stack several feedbacks on one button, test a variable with an Expression feedback, and generate a feedback per dropdown choice.
Group related controls in a section, enable scrolling for overflow, and protect the section with roles, a PIN or an NFC card.
Give a group of controls a second layer in the same area using a Shift Section with Main and Shift pages.
Arrange controls as navigable folder pages within one area of a position, with generated or custom navigation.
Keep occasional controls behind one trigger button that unfolds a temporary panel, and control it from other buttons.
Maintain one set of controls centrally and place it in several positions so every instance updates when the master changes.
Generate a complete routing panel from chosen sources and destinations, with filters, take behavior and lock controls.
What a Custom Router's shared context tracks, how Auto Take Mode and Control Mode shape its behavior, and how nesting works.
Build a hand-placed ATEM routing panel with source, destination, Take and Clear Selection controls inside a Custom Router.
Was this helpful?
0 of 0 users found this page helpful