...
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
coming soonOnce 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:
...
You can see that each has their 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.
Next up, we need to setup the program and preview channel in the Branding Player. That’s done from the Channel Preferences menu item:
...
Next up, it’s a matter of taking assets. That can be done from the Branding Player or Flow. From Flow’s Trigger Assets page, it’s a matter of selecting assets and using the buttons to take to program or preview channels:
...
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.