| Info |
|---|
While BrightAuthor:connected users may find the info presented on this page interesting, it is not strictly necessary for them to understand these concepts because BrightAuthor:connected automatically takes care of these details. On the other hand, CMS partners who are looking to integrate with BrightSign’s products may find this basic high-level explanation of player configuration helpful. |
Player Configuration
When a fresh-from-the-factory BrightSign player is unboxed, it cannot do much without first being configured.
Configuring a player is the process in which a Setup is applied to the player. The Setup applies various settings to the player (network settings, logging, etc.) and includes a Player App which provides instructions for what the player should do upon startup.
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.
...
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. Setups can be saved to a library, modified, and applied to other players.
...
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.
...