HOME Graphic Inserter - Configuration and Control

If you have not already done so, then it is recommended to check the following options for the App Server(s):

• Automatic deployment and Server Groups - determine how apps are deployed to the available App Server(s).
• Stream Redundancy - required for dual-redundant streaming, compatible with SMPTE ST2022-7.
• Single SRD mode - important for compatibility with some third-party (video) devices.
• Redundancy Groups - can be used to configure app failover (for redundancy).
• PTP Configuration - essential for correct synchronization of the media streams and compatibility with SMPTE ST2110-xx.

For more information, please see HOME Apps - App Server Configuration.

To prepare a new app for operation, there are four main steps:

1. Open a connection to HOME.
2. Create a new app.
3. Start the app.
4. Check the app's health.

To open a connection to HOME, you will need a computer that is installed with a suitable web browser application. The computer must be connected to the same network and subnet as the HOME management system server(s). The HOME UI is accessed by entering the IP address, or domain name, of the HOME server into a web browser and then signing in. Following a successful sign in, the HOME 'Devices' page appears. 

From HOME's 'Devices' pages, you can create an app using the New App function. This can be done at any time, with or without an app server. This step labels and configures the app, and adds it to HOME's 'Devices' list.

Please note: During the app creation process, the user is presented with a range of options that define the fundamental functionality and streaming capability of the app. The choices made here will determine the resources required to run the app: I/O bandwidth, CPU resources, etc. This allows the IP senders and receivers to be tailored to the application and network (to help manage the bandwidth of the switches and NICs). Note that the initial configuration options can be edited later but this is only possible once the app is stopped.

Once an app exists it can be started either from HOME (using Start App) or remotely (via the HOME API). This step deploys the app's processing to one of the available app servers. To start an app successfully, there must be sufficient capacity (on a HOME Apps server) and enough available licenses or credits (on the HOME system). The resources can be checked by looking at the Target App Server and Licensing information (in the 'Start App' dialog).

Once an app is started, you should check the app's health. This step confirms that the processing is correctly deployed. Click on the app's label (to open the ' Device → General ' settings) and check the  Lifecycle  area. If the status shows as " Running on <name of app server> " and " Currently reporting healthy ", then the app is ready to use.

When the user clicks on an app label in HOME, this opens the 'Device → General ' settings (for the app), and provides access to several other menu tabs: Network Ports, Senders, Receivers, etc.

From here, you can view and edit a variety of app-specific parameters such as the label and location, license type, initial configuration, senders and receivers, and so on.

The app's 'Advanced' page provides information and configuration controls relating to the app itself, presented in a simple menu tree structure.

The same parameters can be accessed (over NATs) via the HOME API. This supports integration with external broadcast control systems such as Lawo's VSM.

It should be noted that the available menus and controls may change, depending on the app's configuration. In addition, some controls only become available once the app is running; these appear at the bottom of the parameter tree and host the app's runtime controls. 

The latest settings are saved (by HOME) whenever a change is made. If a restart is required, then this is noted in the documentation.