Audiovisual control · Practical guide
Ross DashBoard: operator panel and show states
A panel can bring opening-show information together so the operator does not have to move between equipment windows. First define what each field means and where its information comes from.
- Documented data source
- Panel parameter: source and freshness
- Operator: explicit decision
- AV action + independent feedback
Distinguish local data from device status
CustomPanel supports data sources and local parameters. A local parameter can represent an operator selection; it does not establish that a destination changed. Associate each indicator with its source and retain an unconfirmed condition when information is missing.
For a specific device, record model, firmware, plugin or interface, version, and parameter. RossTalk, OGP, and other transports must be checked for that destination; another product’s panel does not establish integration.
Original panel diagram for an opening
The table proposes a layout for opening-show information. It is an original conceptual diagram with no active controls. Adapt the state names to the rundown and the feedback each device actually provides.
| Panel area | Example information | Operating decision |
|---|---|---|
| Program | Revision R03 · opening C010 | Verify revision before authorization |
| Selection | Requested content: opening_A | Compare file and destination |
| Feedback | Video: unconfirmed | Retain holding content and contact the video operator |
| Block state | Preparing / running / held / complete | Interpret within the rundown stage |
| Planned actions | Prepare / authorize GO / hold / manual return | Allow each action only in its context |
| Freshness | Last received update | Treat stale data as unconfirmed |
Use explicit text alongside color. Separate GO from cue selection so changing panel focus does not trigger content. An audiovisual pause needs defined behavior for each medium; it is not an emergency stop.
Prepare the panel and review
- Retain an independent copy with a revision, dependencies, and editor.
- Classify every field as requested, received, or confirmed by a person.
- Document the display when a device does not respond and who retains manual control.
- Compare panel reopening with the expected state: restored data may not represent the equipment’s current state.
Verification plan and alternatives
Propose a walkthrough with the operator: select content, authorize one start, hold after a change, and return to the holding background. During a future authorized test, record revision, action, received data, time, and observed output.
For a small task, a device’s native panel and a department call may be sufficient. With multiple destinations, compare CustomPanel maintenance effort with its operating benefits. Before planning a migration, confirm the operating system and DashBoard 10 dependencies on the intended workstation.