...
Although the main Branding Player is minimal, plenty of useful information and preference settings is are made available using dialogs and tool windows. These can be opened form the File menu:
...
For example, open the Assets tool window from the File->Assets… menu item which gives a list of all available assets:
...
Branding Player supports multiple channels and uses ip connections to communicate with the web server for rendering , and for sending branding commands and automation commands. The 3 ip connections are:
...
Assets can also be triggered using a schedule defined in Flow. It uses timecode to trigger the assets.
Branding Port
...
The Branding Port is optional and is used for manually controlling the Branding Player. There are a fixed set of commands that the branding port supports:
...
The port is defined in Flow. In order to use this port for a channel, an ip address and port need to be defined. Branding Player creates a socket server if a port is defined for the channel providing a way for apps to send branding commands to the player.
...
Any app which can create a socket client can connect to a channel’s branding port. Chameleon comes with this support from Flow on the Trigger Assets page and also from the Branding Master app.
Automation Port
coming soon
...