...
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.
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.
web server port program/preview channel ports - 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. We support a program and optional preview channel for each channel.
Assets can also be triggered using a schedule defined in Flow. It uses timecode to trigger the assets.
...
The Web Server Port is defined from menu item File->Channel Preferences… Both a program and optional preview ip/port can be defined.
...
Scheduling Assets in Flow
...