Player Configuration

When a fresh-from-the-factory BrightSign player is unboxed, it cannot do much without first being provisioned configured.

Provisioning Configuring a player is the process in which a Setup is applied to the player and a Player App is installed on the player. The Setup applies various settings to the player (network settings, logging, etc.) while the and includes a Player App which provides instructions for what the player should do upon startup.

...

Image Added

...

A Setup establishes various player settings and may include the following:

• Network settings (wired, wireless, username/password, etc.)

• Player name and description (more descriptive info for the player beyond its unique serial number)

• Time zone (especially relevant for geographically dispersed players)

• Publishing mode (tells the player how to retrieve content; more details about these modes here)

• Diagnostic web server (enables access to a wealth of diagnostic info on the player)

• Logging (enables various logging options)

• Debugging (enables access via various logging tools)

• BrightSignOS version (enables the assignment of a specific OS version to the player)

Player Provisioning

As mentioned, provisioning refers to using BSN.cloud to configure a player, and given that BSN.cloud (either the Control Cloud or Content Cloud tiers) is used the vast majority of time to configure players, the term provision is often used when referring to player configuration.

The primary cases where a player might be configured instead of provisioned (i.e., BSN.cloud is not used to configure the player) are:

• Standalone player configurations where the Setup is manually copied to a storage device and then the storage device is connected to a player.

• Uncommon situations where a partner chooses to configure players without using BSN.cloud.

With BSN.cloud, provisioning a new player can be nearly automatic - if things are properly set up beforehand, new players can be automatically provisioned just by plugging them in! For customers who can’t or don’t want to connect to the internet, offline provisioning options are also available.

Setup

Setups can be created in BrightAuthor:connected or the aforementioned free and unbranded Control Cloud at control.bsn.cloud (more detail about this on the next page). In both cases, Setups can be saved to a library for future use.

Partners can use our APIs to connect their CMS directly to the Control Cloud. This enables their CMS to be used as the interface for player provisioning.

, modified, and applied to other players.

Once created, Setups can be applied to a player or group of players using either BrightAuthor:connected or control.bsn.cloud. Alternatively, the information contained in a Setup information can also be directly incorporated into the Player App (described below) and then manually copied to the player’s storage device.

More info about Setups can be found here and more info about provisioning can be found here.

Player Settings

The Setup establishes various player settings which include things like Publishing Mode, network settings (Ethernet, WiFi, etc.), player identification (name and description), logging, and more.

Player App

The set of files and folders that instruct the player what to do upon boot up is collectively known as the Player App. At a minimum, the Player App must contain an autorun.brs file (the .brs extension denotes a BrightScript file) which instructs the player what to do upon startup.

When a Setup is applied to a player via either BrightAuthor:connected or control.bsnBSN.cloud, an autorun.brs file is automatically created on the player.

Partners can write custom Player Apps to perform certain actionsaccording to their specific needs. For example, the Player App may be designed to connect to the partner CMS to download content from the CMS for the player to display. Many partners use our basic autorun.brs as a foundation for writing their own Player App.

Next - BSN.cloud What's Next? >