Audiovisual control · Practical guide
Choose a show-control platform for the project
Start with existing equipment, the available operator, and the result that needs verification. More platform features can add work when a show only needs one attended action.
- Show requirements and available operation
- Runtime architecture
- Exact equipment interfaces
- Maintenance and verification plan
What each approach provides
| Platform | Documented approach | Decisive project information |
|---|---|---|
| Medialon | Tasks, timelines, and panels; PC or compatible Showmaster | Project target, license, and equipment MxM/MRC |
| WinScript Live / V16X | Sequence editing for runtime on Alcorn hardware | Controller generation, firmware, and Product Files |
| Q-SYS | Logic and UCI within a design; real runtime on a Core | Core, design revision, and control scope |
| Ross DashBoard | CustomPanels connecting parameters and data sources | Exact plugin/interface and indicator source |
| Node-RED | Message flows with nodes and logic | Runtime, nodes, initial state, and proposed interface |
The table compares documented functions. Before selecting a platform, verify compatibility with the actual equipment and define how its outputs will be tested; those conditions may change the choice.
Resources and interfaces before selection
- Function inventory: trigger, content change, and required feedback.
- Architecture: where logic runs, what the operator sees, and what happens if the editing computer closes.
- Dependencies: software, firmware, plugins, and product files to retain together.
- Licenses: verify the edition and version of the actual system without carrying over another generation’s requirements.
Choose a workflow your team can maintain
If another team maintains an existing system, compare a focused extension with adding another platform first. A documented manual control may be enough for one action. For multiple zones or sequences, ask to see how the operator identifies cue, status, and a manual alternative.
A network interface does not establish timing precision. If media alignment is required, define tolerance, reference, and measurement using the selected destinations. Logic emulation or review does not replace that test.
What to retain for show maintenance
Keep the approved file, revision, dependencies, documentation sources, control map, and change record. Define who may edit, who approves a new revision, and how to return to the previous one. File recovery and restoring physical equipment state are separate tasks.
Before changing the operational version, an update needs a reason, compatibility review, and rehearsal. For an estimate, include preparation, documentation, an operator, authorized testing, and required support; equipment and service availability are confirmed in the proposal.