Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »

Branding Player is used to show bugs and snipes. All bugs and snipes are called assets and are defined in Flow using templates that have been published into the Chameleon database.

After launching Branding Player, you can optionally set preferences. This is where your Chameleon credentials are entered:

Followed by a dialog to choose channels and the logos path:

Although the main Branding Player is minimal, plenty of useful information and preference settings is 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:

Branding Player supports multiple channels and uses ip connections to communicate with the web server for rendering, branding commands and automation commands. The 3 ip connections are:

  1. branding port - Acts as an ip server for clients to connect to the Branding Player for sending branding commands. This is the way Flow triggers assets. It’s also how the Branding Master triggers commands. The ip port is defined in Flow on the Branding Players page. Any platform that can send commands over ip can be used to communicate with the branding connection. For example, Ross Video’s Dashboard can easily integrate with the Branding Player using this connection.

  2. automation port - If there’s a requirement to trigger assets using automation, an automation ip connection can be used. Branding Player can be the client or server for an automation connection. While branding commands are fixed, automation commands can be defined in the Branding Player.

  3. web server port - In order to render assets, an ip connection is made between the Branding Player and the Web Server. The Branding Player specifies the graphics project, scene and key/value pairs so the Web Server can render assets. While #1 and #2 are optional, the web server connection is required in order to render the assets.

Assets can also be triggered using a schedule defined in Flow. It uses timecode to trigger the assets.

Branding Port

coming soon

Automation Port

coming soon

Web Server Port

coming soon

Scheduling Assets in Flow

coming soon

  • No labels