Audiovisual control · Practical guide
WinScript Live and V16X: prepare a sequence and manage changes
A useful sequence must be readable, editable, and recoverable to a known revision. For an opening with several destinations, the programming file is only one part of the system.
- Proposed rundown and operator GO
- WinScript Live: edit the copy
- V16X: intended runtime
- AV destinations: response and output to verify
Identify the controller and resources
WinScript Live is the programming environment; V16X is the controller in this example. The controller runs the programming once the installation is prepared. Do not infer ports, synchronization, or compatibility from a V16Pro document.
Prepare a record of the exact model, firmware, editing operating system, WinScript version, and product files. If a destination’s model and version are missing, identify its interface as an item to confirm.
Separate decisions from timing
WinScript 6 documentation distinguishes Logical and Timed sequences. Logical sequences provide control flow; Timed sequences place events on a timeline. For a proposed opening, separate start authorization from the audiovisual block with a defined duration.
- Name the block and resources by function: opening, main_video, and speaker_background are original examples.
- Assign each event a destination, expected parameters, and an output observation. Retain the identifier when the editorial order changes.
- Agree on holding content if a file is missing and who calls the return to the speaker.
- Define the required timing tolerance between media; matching event times do not establish aligned outputs.
Prepare a change while retaining the previous revision
Save a new copy of your own example and describe the change: replacement clip, duration, or return point. Compare events, resources, and comments before and after. When another operator supplies a file, preserve their original and agree on which copy you will edit.
When importing a WinScript 5 script, the manufacturer documents possible changes to Product Files, Audio Player routing, sequence types, and timing. Review the import log. Conversion alone does not validate behavior.
What to check in a future rehearsal
| Review | Expectation | Record |
|---|---|---|
| Read the copy | Resources and events match the rundown | File, version, and differences |
| Opening GO | One start after authorization | Cue, status, and observed output |
| Clip change | Approved version is used | Name, duration, and destination |
| Manual return | Operator restores the agreed background | Decision and department confirmations |
Testing Sequences describes Live Mode connection and Live Log. Before using those tools, agree on the rehearsal environment and permission to operate the controller. Then compare the logged event with what is seen and heard at each output.
Information that defines the scope
- New V16X or existing installation? Hardware review avoids applying another generation’s instructions.
- Does the sequence follow a presenter or a fixed timeline? This changes where decisions belong.
- Who retains the approved copy? Define ownership, revision, and recovery before changing it.