Audiovisual control · Practical guide
Medialon: prepare a show-control project and rehearsal
An opening can bring together video, audio, and a lighting cue. Before programming it, decide where the project will run and what information the operator needs to authorize each step.
- Operator: authorizes the opening
- Manager: task and variables
- Documented interface: AV destination
- Available feedback + observation of the output
Choose the architecture before building cues
The manual distinguishes Product License from Current Target. The license enables runtime use; the target limits editing resources to the selected product. Selecting Showmaster as the target does not grant a license or establish hardware compatibility.
Confirm whether the project runs on a Windows PC with Manager or a compatible Showmaster. A unit running Showmaster Core 2.x must not be upgraded using the Manager 7.1 installer: 7thSense reserves that migration for its staff. Record model, hardware generation, installed version, target, and license before estimating changes.
Prepare a copy another operator can understand
- Keep the original and assign a revision to the working copy. Organize devices, tasks, variables, and operator screens separately.
- Define one initial action, such as opening_video, and record its expected file, destination, and completion criterion.
- For each destination, record the MxM/MRC, version, transport, and documented response. If feedback is unavailable, state what the operator will observe.
- Identify who authorizes GO and how to return to holding content. An accepted command and a visible image require separate checks.
What changes between preparation and runtime
In Stop, the manual states that internal tasks do not run and external equipment communication does not occur. Debug keeps programming tools available while the project interacts with destinations; User restricts accessible objects and Run hides programming tools. Use a disconnected copy for a document review.
If you only need one attended action, compare a documented manual trigger with a broader sequence. A timed task does not establish synchronized outputs: agree on the required tolerance and how to measure it during an authorized rehearsal.
Rehearsal plan: what to record
To rehearse the opening and return to the speaker, define the file, return point, and what you expect to see or hear at each destination. The table sets out checks and records for that proposed rehearsal.
| Case | Expected result | Evidence to retain |
|---|---|---|
| Authorized GO | One opening using the approved revision | Revision, cue, time, operator, and observed output |
| Video not ready | Operator retains holding content and decides how to proceed | Available status, notification, and decision |
| Return to speaker | Agreed background and audio under department control | Separate video and audio confirmation |
| Next performance | Opening requires fresh authorization | Initial state and pending cues reviewed |
Section 8.4.8 documents Log Traces and warns about file growth. For a future rehearsal, select the activity to record and a file size limit. A cue log supports diagnosis; observing the output remains a separate check.
Three decisions that change the proposal
- Is a Showmaster already installed? Its model and version determine which architecture can be retained.
- How many operator interfaces are required? Confirm WebPanel connections and edition before selecting resources.
- What should happen if the clip is not ready? Agree on holding content, department calls, and a manual alternative.