Player 4.2.32 · release · Manual updated 31 October 2026
Discovery, device identity and integration
Identify a player during a scan, then use authenticated capabilities for monitoring, programming, control and facility metadata.
Public read-only discovery
A scanner can probe a known host/port without web login. This is an HTTP identity probe, not a built-in subnet scan.
| GET / HEAD path | Response |
|---|---|
/api/player/v1/discovery | Minimal JSON with schema/product, running version, installation ID, licence-issued serial and public leaf certificate metadata/PEM when available. |
/.well-known/dcp-cine-player | Alias of the discovery JSON. |
/api/player/v1/discovery/recipient-certificate | Public leaf PEM download; unavailable certificate returns a structured error. |
/.well-known/dcp-cine-player/recipient-certificate | Alias of the public PEM download. |
curl --fail --max-time 2 http://PLAYER-IP:8080/api/player/v1/discoveryAccept a candidate only if schema is d-cine.player-api.discovery.v1 and product is dcp-cine-player. Unknown optional fields are null with warnings. No content, operational state, private key, credentials, site contacts or configured network inventory is returned. Certificate presence alone proves neither a live licence nor trusted KDM authorisation.
Keep the identifiers separate
| Identifier | Meaning / lifetime |
|---|---|
| Installation device ID | Persisted installation UUID. Normal restart, upgrade and certificate rotation preserve it. Provision an offline clone with a fresh installation identity. |
| Issued product serial | Follows the activated licence registration, not the certificate. Reactivating that licence retains its serial; changing licences changes it. An unregistered/deactivated demo reports null. |
| Certificate serial / fingerprint | Identifies the recipient certificate. Rotation may change these without changing the licence serial or installation UUID. Legacy /identity.serial is the certificate serial; its alias is certificate_serial_number. |
| SOAP compatibility identity | Legacy Barco labels serve existing SOAP clients. They are not the player’s real manufacturer/model or equipment serial. |
Declare real screen metadata
An administrator opens Config → System Details → Device identity and screen capabilities. Use confirmed publisher D‑Cine and software-product model dcp-cine-player where appropriate to this product; do not invent a chassis model. The licence-issued product serial and installation ID are read-only. Leave unknown editable identity fields blank; they are stored as null. Identity fields accept at most 50 characters.
Installed screen audio formats offers Unconfigured (unknown), None installed (an explicit empty declaration), and 5.1/7.1/IAB toggles. This describes the complete screen. It does not change audio routing, active CPL selection or decoder licences. Decoder support is reported separately; a mismatch warns while preserving the operator declaration. Declaring IAB does not enable IAB decoding.
Screen digital 3D and Screen closed captions each offer Unconfigured, Unsupported and Supported. They are declarations, not hardware certification or an inference from a subtitle file. Save explicitly.
Authenticated native API
Negotiate /api/player/v1/capabilities before consuming optional features. Authenticated GET /api/player/v1/device-info supplies actual identity, running software components, decoder capabilities and screen declarations without depending on a recipient certificate. Status and API feature support remain separate from installed auditorium audio.
Connected-equipment inventory is currently unsupported in this metadata contract; no automatic projector/processor discovery is implied. Catcher owns its facility mapping, operator override handling, FLM validation and publication. The player does not publish FLM XML.
For SOAP clients retain Legacy Barco compatibility until the actual TMS is qualified for Real product identity. Native metadata always reports real product identity and separately identifies compatibility mode.
Programming and command recovery
The native TMS API supports show programming before delivery, readiness/preflight, scheduling, durable ingest and state-aware playback controls. A new booking omits its locally generated ID so the player assigns it. Updates use the existing native identity and revision guard. Remote controllers must wait for both command completion and confirmed timeline/state before the next action; never replay an uncertain control to bypass a pending or recovery state.
Seeking/navigation preserve playing/paused state and suppress skipped automation cues. Test actual automation and media/KDM delivery separately from synthetic navigation. Configure API credentials through the documented deployment workflow; discovery does not grant control access.
Contracts and technical handoff
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.
