...
Note that while this article shows both program and preview channels as web-based channels, you can mix and match program and preview channels to be ndi, sdi or web. For example, a program channel can be SDI while the preview channel can be in a browser.
Branding
Once both the program and preview channels are defined in the web server (or ndi player or sdi player), it’s a matter of taking their unique ip/ports and defining them in the Branding Player. For example, if TSN1 is the program channel:
...
and TSN1 Preview is the preview channel:
Setting up Web Server
First we’ll setup the Web Server (or NDI Player or SDI Player) before we show how it can be used with branding and the CG Sequencer.
We’ll create a program channel called TSN1 and a preview channel called TSN1 Preview:
...
You can see that each has their its own unique endpoint (where the rendering happens) and ip/port. On localhost, TSN1 has endpoint localhost/tsn1 with port 127.0.0.1/8109 while TSN1 Preview has endpoint localhost/tsn1preview with port 127.0.0.1/8108.
Branding
Next up, we need to setup the program and preview channel in the Branding Player. That’s done from the Channel Preferences menu item:
...
If we setup a couple of browser tabs, we can see the output in both program and preview channels (aka endpoints):
...
CG Sequencer
coming soon.We’ll use the same program and preview channel for the CG Sequencer. From Flow, go to the CG pages from the dashboard:
...
We’ll need to setup the players for TSN1 to define a program and preview channel here:
...
After that, go to the Sequencer and you’ll see program and preview support for taking scenes:
...
Pick your scene and it’s a matter of using the program and preview buttons to take it to the desired destination:
...