Player 4.2.32 · release · Manual updated 31 October 2026

Status, audit and performance

Separate a selected show, a scheduled booking, command acceptance and observed playback when investigating an incident.

Read the Status table

Status presents readable event times in the player’s timezone and configured 12/24-hour format, with seconds and a timezone label. Hover a timestamp to retain its original UTC value. Filters can match readable or raw time. This is deliberately separate from browser-local calendar editing.

Routine protocol progress/position/status chatter updates state without flooding the operational table. Named SPL/CPL or item starts, ends and interruptions include identifiers and outcome. Cue/macro requests and completion/failure provide automation evidence. Use Download Syslog for retained detailed logs; historic heartbeat lines can remain in that download.

Did the scheduled show actually play?

1. Record the booking’s exact start instant, show name/UUID, relevant timezone and scheduler state.
2. Look for scheduler dispatch, skip or failure at that instant. Check readiness, missing CPL UUIDs, KDM validity, trusted time, licence and any already-active playback/Casting mode.
3. Correlate the run with an observed SPLStart, each intended CPLStart / CPLEnd (or black/item events), and the SPL end/outcome. Repeated CPLs require the actual occurrence/item identity.
4. Distinguish a natural end from stop/interruption. A selected/loaded SPL or accepted Play command is not proof that it was presented to completion.
5. Use the operational audit export where available to preserve the evidence and its coverage limits. Investigate any missing journal coverage instead of treating absence as a pass.

These are engine-observed events. Physical projector, processor and auditorium output still require their own confirmation. An SPL with missing media must be repaired or supplied; missing automation references warn and may let media play while the intended cue fails.

Operational Audit

Open Config → System → Operational Audit with the appropriate role to inspect journal health, retention and the read-only test-export facility. Managers/admins have audit read/export permission; retention/configuration changes require administrator access. Exports are asynchronous and capability-negotiated.

The persistent journal records operational playback, automation and other activity. It is unsigned operational evidence, not a certified security log. Export snapshots, sequence numbers, explicit coverage and expiry must be preserved by a collecting TMS. Collector and export contract.

Investigate dropped frames

1. Record the CPL/show UUID and occurrence, timecode, output mode and whether the symptom is repeatable at the same point.
2. Compare Telemetry → Playback, video/audio/sync findings and the local HUD. Review actual versus target frame rate, decode workers/mode, dropped-frame growth, CPU, bitrate and decoded-buffer history.
3. Check media-disk health/free space, competing ingest/check jobs and the final display/SDI refresh, link and audio path. A falling decode buffer can indicate insufficient delivery/decode headroom.
4. Rehearse representative material on the intended hardware and compare one controlled setting at a time. Retain before/after evidence; a fast synthetic black test does not qualify JPEG 2000 playback.

Do not attribute one advertisement’s dropped frames to its name or duration alone. Decoder workload, disk delivery, scheduling/rendering, output timing and background activity need evidence. Worker, output and calibration changes can be interlocked while the player or scheduler is active.

Read the header carefully

Active scheduler/playback/SDI indicators remain coloured in dark mode. Clock offset is green within the UI’s tolerance and red when more than ten seconds apart. That offset compares the player with the browser; a green comparison is not the same as qualified trusted time. Check trusted-time state before time-sensitive operations.

HUD and display diagnostics · Problem checklist