Viz Channel Branding User Guide
Version 5.2 | Published June 05, 2024 ©
Requirements
There are compatibility requirements, access policies and rights for the software components in a Viz Channel Branding work flow.
IMPORTANT! Always check component software Release Notes, bundled with the software installers at download.vizrt.com and in the Documentation sub-directory of the program directory once the program is installed.
General
There are some general requirements for any Vizrt system to run. These requirements apply when setting up a complete system with integration to other Vizrt and third party software products:
-
All machines should be part of the same domain and workgroup.
-
Users of the Vizrt machines should ideally be separated into at least two groups: administrators and designers/operators.
-
Most machines running desktop applications must be logged in with sufficient privileges to run Vizrt programs, while services by default do not require users to be logged in.
-
Vizrt servers must have static IP addresses.
Caution: Third party systems that provide Vizrt systems with files must only use Microsoft Windows operating system compatible characters as the file name.
-
Vizrt has license restrictions on all Viz Engine and Viz Artist instances. To have an output of Vizrt generated graphics (preview and program channels), either a USB or a parallel port dongle on the renderer machine is required.
Hardware
Hardware requirements vary depending on the system purchased; however, every system delivered by Vizrt has an accompanying hardware specification sheet that matches the requirements on the software for a new system.
For older hardware, such as Viz Engine, that is used with newer versions of Vizrt software, it is always recommended to check the current hardware specifications for the new software version to make sure that the set-up will work.
Additional hardware must always be checked to see if it is compatible with existing hardware. For example, the GPI cards supported by Vizrt must fit into the Media Sequencer servers.
For more information on hardware specifications, please contact your local Vizrt customer support team.
Software
The following sections describe software requirements for the product described in this manual and a range of components that may be integrated with it.
IMPORTANT! Always read the Release Notes for late minute changes or requirements, if any. If there are differences in the hardware or software requirements listed here, the Release Notes supersede this manual.
Viz Channel Branding
The Viz Channel Branding client is used by the traffic department to schedule programs that are controlled by automation systems in the master control room. It has a TCP connection to Media Sequencer. The client gives the user access to creation, editing and playout of pages with graphics and video clips.
Component |
Requirement |
Software |
Media Sequencer 4.1 or higher. Microsoft .NET Framework 4.8. Microsoft Visual C++ 2010 Redistributable Package (free download from http://www.microsoft.com/en\-us/download/details.aspx?id=5555). Viz Engine 3.6 or higher. Viz Engine 5.0 recommended. If you are using a local Viz Engine to preview video clips from Viz One, Viz Engine must be installed with video codecs: (Windows 7 = K-lite Codec Pack full) Viz One 5.11 or higher if using Viz One integration. |
Operating system |
Windows 10 64-bit Windows 7 64-bit Windows Server 2008 R2 |
Integration with Viz One
Viz Channel Branding integrates with the Viz One MAM system.
Network Ports and Connections Ports and Connections
Component |
Port |
Who may use it |
Media Sequencer |
8580, 8594 |
Integrations Hub, |
Integrations Hub |
9991 |
Playlist Importer |
Integrations Hub |
9990 |
Integration Modules, |
Promo Server |
9980 |
Failover Helper |
Quick Scheduler Server |
9970 |
Quick Scheduler |
Promo Server |
9005 |
Integrations Hub, |
Viz Engine |
6100, 6800 |
Media Sequencer, |
Preview Server |
5400, 21098 |
Viz Channel Branding Client |
Viz One |
80 |
Integrations Hub, |
Failover Helper |
9960 |
Any browser |
External Component |
Port |
Who may use it |
Harris Automation |
10050 |
Harris Integration Module |
Marina Automation |
18083 |
Marina Integration Module |
Ports in table above are TCP. Read the From and To in the table as initiator and receiver. Example: Viz Channel Branding client uses TCP-port 8580 and 8594 when exchanging data with the Media Sequencer. Not all ports are used at all times, but they can be used and must be available. Traffic can be assumed bi-directional, i.e. from and to the services using the ports indicated in the table.
Note: Viz Channel Branding Marina Integration sends traffic on port 18083 to the Marina Automation and uses port 12212 bi-directional.
IMPORTANT! Some ports are configurable. For instance the Viz Engine uses port 6100 (and additional port 6800 for dual-channel engines) but can be configured to use other ports.