...

Setups can be created in BrightAuthor:connected or the 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, enabling their CMS to be used as the user interface for player provisioning.

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

Partners also have the ability to use our APIs to connect their CMS directly to the Control Cloud, enabling their CMS, rather than the Control Cloud, to function as the user interface for player provisioning.

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.bsn.cloud, an autorun.brs file is automatically created on the player.

Partners can write custom Player Apps according 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.

...