Player Settings - Controlling and Configuring Media Players in the CMS

Using the Player screen to monitor players, send commands, program information, create and manage player groups

Written By Ed Kinne

Last updated 3 months ago

Media Players, or simply Players, represent end-node devices running the Korbyt player software to display Signage Content.

This article will review the settings and options for configuring your media players in the Korbyt CMS. Please see Adding Players to your Korbyt Tenant - Provisioning if you need assistance adding players to your CMS.

The Players Screen

To Access and View the Player Screen

  • Click on the Mega Menu, in the Device Management column, click on Players

Viewing Options of the Player Screen

  • You can set the view to be a List, Cards, or a Custom List using the view controls in the upper right

    • The List View displays columns of information about players

    • Card View displays the most recently captured screenshots

      Player Screenshots are normally captured when players reboot, or when the Get Screenshot command is sent. If continually updating screenshots are something you require see Korbyt Instant Screenshots

      • There is a toggle button to overlay player details

    • At A Glance view allows a user to create a custom list view

      • When you click the At A Glance selector, you will see a pop-up window to select which data points you want as columns in your custom list view

      • Drag the datapoints to the right that you want to add, then scroll to the bottom of the pop-up and click continue

Player Groups provide an alternative way to view player details. Information about this view can be found in Player Groups and Access Permissions


Heartbeats and Check-ins

In the different views, you can see two duration-based information fields, Last Heartbeat and Last Check-in.

  • Heartbeat

    • A small connection from the player to the service that happens every minute

    • It is used to synchronize activity between the player and the service

    • When working correctly, the Last Heartbeat should read as “just now”.

      • Some activities, such as a software update or reboot, will disrupt heartbeats for short periods.

  • CheckIn

    • A full review of the content assigned to the player through playlists which happens every 15 minutes.

      • Any changes that have been made in the system (items being deleted, content added that flows to a playlist through clever rules or tags) will be synchronized to the player through the check-in

    • Some actions will cause an immediate check-in to happen, not waiting for the 15-minute cycle, such as sending the check-in command or clicking save a playlist that is directly assigned to a player

      • When an action causes a check-in, it also resets the “every 15-minute” timer for the next check-in

Hearthbeats and Check-ins are also used to determine a player’s status.


Player Status

A player can be in 1 of three states

  • Active Status

    • A player who is communicating normally

    • Heartbeats and Check-ins are happening as expected

  • Inactive Status

    • A player who has stopped communicating normally

    • The reason for the disruption could be that the player is powered off, the network cable has been unplugged, a network outage, or a software crash.

    • A player will report as Inactive after two missed check-ins, or approximately 35 minutes of missed heartbeats.

      • The player returns to Active status when the Heartbeast and Check-Ins begin again

  • Pending Status

    • Pending is a temporary status for a player between the player being provisioned to the tenant and their first successful check-in

    • A player that is powered on and connected to a network should only be in Pending for a few minutes.

      • Slow network connections might take longer

      • A player that is unexpectedly in Pending for a long time should have its network connection and functionality examined

    • Once a player achieves Active Status, it will not move back to pending

It is possible to configure notifications on players status changes through Player Groups
See Player Groups and Access Permissions and the Player Notifications seciton for details


Taking Actions on Players with the Action Icons

  • The Actions icons for each player allow different interactions with the player

    • Pencil = Edit Player Details

      • View and Edit the Player Detail screen

      • Only Available to Administrator and Tenant Administrators

    • Eyeball = Player Preview, opens a new tab

      • Preview the content assigned to the Player on all of its playlists

      • Not a live view of what the player is showing at that moment

      • Available to all users who can see the player

    • Calendar = Schedules, opens a new tab

      • The Schedule of playlists assigned to the player

      • Can be a Month or Week view

      • Clicking on a Playlist name will open the playlist in a new tab

      • Only Available to Administrator and Tenant Administrators

    • Trashcan = Remove

      • Asks for confirmation

      • Deprovisions the player from the tenant


Editing Player Details

Clicking the pencil icon for a player will open the Player Details page and allow you to send action commands or set player details

If you change any value in the player you have to click the Save button in the upper right


Player Screenshot

And the upper left player information

  • In the top left, there will be a Player Screenshot if the Media Player supports them

  • They are captured/refreshed after a Player Reboot or through the Get Screenshot command (described below in Player Actions)

    • If continually updating screenshots is something you require, see Korbyt Instant Screenshots

    • The Player type appears as a watermark in the top left of the screenshot; it is not part of the actual display on screen.

  • Below the Screenshot, you will find

    • A volume control slide

      • If the player allows volume control

    • S link to the Player Configuration page

      • The Player Config Page is available for Korbyt KDA and KWP players and links to the IP Address of the player to log directly into the device

      • For more information, see KDA Player Configuration Page

    • A Preview Eyeball

      • Opens a new tab that will preview the player content, the same as the preview eyeball on the Player Screen


Player Tags and Description

  • Tags

    • Attaches a point of information to a player

    • Can be used to organize, along with the media items that are tagged

  • Player Description

    • Can enter a description of the player that would be helpful to other system users, especially helpful if the player name is too limiting

    • The player description shows in the Player Screen next to the Player Name

      And in the Playlist / Player Assignment window


Player Actions

The Actions section in the upper right allows you to send different instructions to a player. Actions available will vary based on the player type.

When clicking an action, some will send the command to the player on the next heartbeat, some will ask for follow-up instructions, and let you schedule the command

Players have to be Active, with an Active Heartbeat, to receive and carry out Action Commands. If a player is Inactive in Korbty, the command will be listed as Pending until the system receives the player’s heartbeat.

Expand any Action below for more details

Check-in

Reboot

Get Player Log

Get / Update Screenshot

Display/Hide Identity

Upgrade Player Software / Agent Version

Clear Cache

Show/Hide QR Code

Hot Key Commands

Runtime Select

Resolutions

Player Metadata and Settings

Player Metadata allows you to program the player with information about itself.

It can be basic information, such as its address or the name of the room it is in, but 100 blank Custom Metadata fields allow you to give any points of information that distinguish the player and who it serves. This information can then be used to create Clever Playlists or Dynamic Player Groups.

This information can be entered and changed one player at a time in this Player Screen, or you can update several players’ metadata at once using the Bulk Provisioning Process

Expand a Metadata or Settings section to learn more

Locaiton

Custom Metadata

Custom Properties

Sleep/Blackout Schedule

Player Groups

Content Assigned

Scriptlets

Screen Control

Multiscreen Settings

Player Details Section

The Player Details section has multiple areas of information. Some sections only display details about the player, some sections are configurable.

Details that can be Set

Player Alias

  • An optional “Friendly” display name

  • Some Media Players have a limited ability to change the player name for the device

    • Either character limits or format limits

  • The Player Alias is a way to set a more friendly name that will be displayed in the Korbyt CMS in places that are labeled Player Name

Player Name

  • It can be set, but some devices limit how it can be changed

Player Background Color

  • The color that will be seen if the content does not fill the screen completely

    • Letterboxing, or Columnboxing

  • Normal Default is black, but it can be changed

  • Setting to a Company color can help content look more polished if it is not 100% matching the screen ration

  • Enter a color code, or use the color wheel

Details that are only viewed

  • Model - The media player model information

  • IP Address - the IP Address that the player is connecting from

    • Can be used to access the Player Configuration Page if available

  • Provision Code - The code that the player will display if not connected to a tenant

    • Can be useful to check if a type was entered on a player that has been stuck in Pending status

  • MAC Address - The device’s MAC Address

  • Agent Version - The Version of the Korbyt Software that is installed

  • OS Version - The Operating system version for the player

  • Last Heartbeat - The heartbeat should be Just Now

    • Heartbeat should happen every 60 seconds

  • Runtime Version - the Runtime Environment currently selected

    • Can be changed through the Action commands

  • Last Check-in - the last time a check-in was processed

    • Should be every 15 minutes

  • Display

    • Aspect Ratio, Resolution, Orientation

  • Recent Player Events

    • Shows the time that the player has been running, and any unexpected or planned reboots

  • Permissions

    • Shows the User Groups that have access to the player

    • Access to the Player is controlled by Player Groups, this is only a display of any limitation