Overview

DearScenario Player is a free video player for scenarios: exhibitions, rooms, interactive installs, and show-control cues. It is not digital signage software.

Signage owns the playlist and the schedule. DearScenario Player plays the picture on the display machine. The system that already owns the scenario — middle-control, show control, a kiosk app, or a custom controller — decides what happens. The player executes playback, rendering, device-level state, and recovery.

If you have worked on-site before, you know the situation: the playback computer is inside an equipment room, behind a screen, or mounted where manual operation is awkward. Put DearScenario Player on that machine, connect it to the control network, and cue it through the API.

What it is for

  • A scenario on the floor. Play the clip the room, exhibit, or cue needs, when it needs it.
  • Middle-control integration. Let your existing system trigger playback, query state, and coordinate multiple displays.
  • Unattended display machines. Keep players running without keyboard and mouse operation.
  • Show-control workflows. Integrate with QLab, TouchDesigner, Companion, Node-RED, custom web apps, or in-house controllers.
  • Pro AV setup tools. Use projection masking, calibration patterns, image overlays, and OSD text when the player needs on-site adjustment.

What it is not

DearScenario Player is not a CMS, playlist manager, or digital signage platform. It does not schedule content, run campaigns, or replace your control layer. That absence is the product boundary: your system decides intent, DearScenario Player executes playback and reports state.

Capabilities at a glance

  • Playback engine. Built on libmpv for broad media compatibility and production-friendly playback behavior.
  • Control API. One command model is available over HTTP and OSC.
  • State readback. Poll /api/status and /api/health for optional playback feedback.
  • Technician tools. The Web Console helps control technicians identify nodes, perform local setup, and troubleshoot on site; show-control software remains the production authority.
  • Pro AV features. Projection masks, calibration patterns, image overlays, and OSD text are available when the endpoint needs visual adjustment.
  • Deployment support. Config files, logging, crash dumps, and watchdog guidance help keep installations recoverable.

Typical architecture

The system that owns the scenario
(middle-control / show control / custom app)
        |
        | HTTP or OSC
        v
DearScenario Player on the display machine
        |
        | local rendering, audio, masking, status, logs
        v
Projector, LED processor, display, or audio chain

In this model, DearScenario Player should be treated like a device with a network control contract. Your controller can send a load command, call play, watch /api/status, and decide how to recover if the venue or network changes.

For exact command schemas, response envelopes, and error semantics, use the Command Reference. These guide pages focus on product fit and integration workflow.

Next steps