Console player

Important

Beta version 2.1. What is described here exists only in beta version 2.1: it is installed from the beta repository and only with a licence; the stable version 2.0.2 and the demo edition do not have it. The beta version comes without warranty, and support is best effort (Beta testing programme).

The console player plays the OTT delivery of a stream or an adaptive bundle right in the browser, in a separate tab, with no external player and no login typed into the link by hand. It is there to see quickly what the viewer sees: the picture, the sound, the subtitles and the DVR archive.

Where it is available. The player opens only from a console session signed in by auto sign-in (the account’s “Auto-login” switch, Users / Logins), for any role. Player sessions opened from such a session are not counted in connection limits, in billing or in viewer statistics.

Viewing key. Since version 2.1.2.609, the player watches the stream with its own viewing key, which the node issues to the console session; the auto sign-in key does not get into the playlist and segment addresses. The viewing key opens only HLS, LL-HLS and DASH delivery together with the archive: the node API and direct MPEG-TS delivery do not accept it. It is valid while the console session it was issued from is alive, on any node of the domain; watching does not extend that session. The key is not in the node logs or in the client list, and the player sessions are marked “Console” on the “Clients” screen (Clients). A node of an earlier version issues no key, and the player works with such a node as before.

When the console session ends. Signing out of the console, revoking the auto sign-in session, turning off “Auto-login” for the account, changing its password or deleting the account closes the key at once, and the node stops playback already under way within a few seconds. On a refusal the player asks for a key once more: if this browser has signed in to the console again by then, playback continues with the new key; otherwise the player stops and reports that the session has ended. Right after a node restart, while it is restoring the domain’s sessions, the node answers HTTP 503, and the player repeats the request after the time the node gives, up to 10 times in a row.

How to open. The player opens in a new tab:

  • with the ▶ icon (tooltip “Open the player in a new tab”) in the stream row on the “Streams” screen — next to the OTT badges (Streams) — and on the mosaic tiles (Mosaic);

  • with the “Play” (▶) button in the stream statistics window, tab “OTT / DVR” (Stream statistics), and in the OTT links of an adaptive bundle (Adaptive bundle).

The link leads to a stream that is serving HLS, LL-HLS or DASH right now. A paused stream publishes no links and has nothing to play.

Controls. The player fills the whole window; the controls lie over the picture and hide while they are not used.

  • “Protocol”: HLS, LL-HLS or DASH, from those the stream serves (Delivery modes).

  • “Mode”: “Live” or “Archive”. In the archive there is an “Archive timeline” under the picture over the window of the recorded archive; the caption shows “Archive position: …”, and the “Back to live” button returns to live, where “Playing live” is shown. With a node of version 2.1.2.626 or newer the position and the timeline show the real time of the recording, including after gaps in the archive (Archive playback (VOD)); with an earlier node the position is counted from the start of the chosen window. The archive is so far available only for a single stream, not for an adaptive bundle (OTT and DVR).

  • “Audio” and “Subtitles”: the choice of track; each list has “Off”.

  • For an adaptive bundle the “Playing: …” caption names the member and the quality the player is playing.

Diagnostic log. Under the picture a collapsed “Diagnostic log” shows the number of lines: the player writes playlist and segment loads, switches and errors into it. The “Copy log” and “Clear log” buttons; the access key is hidden in the log and in error texts. The log is handy to attach to a support request.

If it does not play. The player retries the load by itself after a network error and recovers playback after a decoding error; if that did not help, it shows the reason:

  • “The player opens only from a console session signed in by auto-login…”: sign in to the console with auto-login switched on and open the player again;

  • “Sign in to the console in this browser first…”: the browser has no console session;

  • “Nothing to play: the stream serves no HLS, LL-HLS or DASH right now…”: the stream has no OTT delivery or is paused;

  • “This stream or adaptive group is not on the node any more.”;

  • “The console session behind this player has ended (…)…”: sign in to the console again and open the player again;

  • “The node is still restoring its sessions after a restart (HTTP 503)…”: the retries did not help: open the player in a minute;

  • “The node refused the playback (HTTP …)…”: most often the console session has ended: sign in again;

  • “This browser cannot play …”: choose another protocol or browser.

The “Open the console” button returns to the node’s console.