Player 4.2.32 · release · Manual updated 31 October 2026

Troubleshooting

Capture the exact message, time and content/show identity before changing files, keys or settings.

Find the narrowest cause

SymptomFirst checks
APT permission noticeUse the readable-cache commands in Install and upgrade. Do not loosen home-directory permissions or disable APT sandboxing.
Missing installation dependenciesConfirm Ubuntu 26.04 amd64 and enabled/reachable repositories; follow the documented apt --fix-broken install recovery.
Dedicated media drive not reflectedInspect Dashboard media path/device/mount and the configured media root. Verify persistent mounting and access as the actual player account; attaching a disk alone does not configure it.
Content not found / not readySource path, mount, read/traverse permissions, package structure, exact CPL UUID, missing OV/assets, indexing/integrity and free space.
Missing cue warningMedia may still play. Repair the referenced cue/macro or deliberately create standard empty names; an empty placeholder does not perform the intended automation.
KDM rejected or outside windowRecipient certificate, CPL/key IDs, full session window and trusted time. For EAR check the complete two-component key material.
Show did not startSCHED state, correct calendar instant/timezone, trusted time, readiness/licence, already-active playback/Casting and scheduler skip/failure. Correlate observed SPL/CPL events.
Manual controls dimmedCheck SCHED, active Casting, pending command/timeline, account permission and current native state. Resolve the owning mode; do not bypass its interlock.
No picture / wrong signalActual display/SDI selection, connector/input, active timing versus EDID preferred mode, cabling, native error and applicable HDCP/DDL policy.
No or wrong soundSelected local/SDI audio path, matrix/routes/gains, mute, processor input, speaker order and sync; use safe-level channel tests.
Dropped framesRecord CPL/timecode and check CPU, decode mode/workers, disk delivery, buffered frames and actual output timing. Follow the performance checklist.
Automation failedExact cue identity, endpoint/arguments, network/transport result and physical equipment state. Missing/ambiguous references do not trigger a guessed action.
Wrong time on a remote calendarCalendar uses browser-local dates/times; align the browser/OS timezone with the venue. Status event timestamps use the player timezone.
Cannot find a new featureCheck the header’s installed version and perform a normal browser refresh. Publishing a package does not upgrade players.
Shift+Q does nothingFocus the local playback window first and hold either Shift key while pressing Q. The browser is a separate window. Use the Power page’s Close Application alternative.
EAR authentication failurePreserve evidence and reacquire a validated delivery/key set. Do not edit descriptors or encrypted assets to suppress authentication errors.

AirPlay does not connect or play

  1. Confirm 4.2.32, Config → Casting enabled, receiver name, selected interface/IPv4 and saved configuration.
  2. Read the unavailability reason. Confirm the native engine/helper and licence are available, playback is stopped, Delay Play is cancelled and SCHED is off.
  3. Enter Casting and wait for Ready to connect. Use the current code; it changes on a fresh entry.
  4. Check sender reachability and mDNS on that network. Wi‑Fi isolation, VLAN/multicast filtering or a missing selected IP can prevent discovery.
  5. Windows requires a compatible AirPlay sender; built-in Miracast does not connect. Protected streaming applications may refuse screen mirroring.
  6. For connected-but-black/no-sound, check Receiving screen versus Connecting, the configured output/audio path and supported sender media. Qualify the exact sender and physical chain.
  7. Leave Casting/Stop and wait for confirmed cleanup before other playback. Needs attention or a retained reservation requires the displayed recovery/error to be resolved.

Preserve evidence and recover deliberately

  1. Stop if picture, sound, equipment movement or security is unsafe.
  2. Record the message, version, instant/timezone, CPL/SPL/occurrence and operating mode.
  3. Collect Status/Syslog and audit where available; use the monitoring guide to distinguish selected, booked and actually played content.
  4. Correct the specific cause, then make one intentional retry. Preserve uncertain command identity and use reconciliation rather than repeated dispatch.
  5. Escalate with sanitised logs and reproducible steps. Exclude private keys, credentials, pairing codes and full licence codes.

Use Media storage consistency to inspect unindexed/missing content before deletion or re-import. A complete catalogue check is not a substitute for cryptographic integrity or output qualification.

Written by James Gardiner · Documentation updated 2026-10-31. For more information visit tools.d-cine.net. Check procedures against the installed release and venue policy.

2026 © D-Cine.net.
Developed by James Gardiner