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
Provisioning specifically refers to using BSN.cloud to configure a player. 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.
...
| Info |
|---|
Given that BSN.cloud is the primary method of configuring players, the term provision is very often used to refer to the process of configuring a player. |
...
...
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 network settings (Ethernet, WiFi, etc.), player identification (name and description), logging, and more. One of the most important player settings is the Publishing Mode which defines the method of content delivery to the player. Various Publishing Mode options exist and are described in more detail here.
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.
...