A HOME TPG is configured and managed by HOME in the same manner as other HOME Apps.

Once configured, its parameters are also available (over NATs) via the HOME API. This supports integration with external broadcast control systems such as Lawo's VSM.

Common information that applies to all app types can be found in HOME Apps - General Operation.

This topic provides information that is specific to a HOME TPG.

Configuring the App Server(s)

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.

Preparing a HOME TPG

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.

App Configuration

For a HOME TPG, the options in the app configuration define the video test pattern being generated and the app's output streams.

A HOME TPG provides a single output sender (TX 1) that can be configured to transmit Video (only) or Video and Audio streams.

The video output can be configured to carry one of a number of simple test patterns. In each case, the pattern can be set to Static or Moving with options to support different Pattern Colorimetry.

If you wish to output a video test pattern and audio test tones, then an Output Audio Transport must also be defined. In this instance, the app's test tone generator provides a selection of incremental frequencies from 200Hz to 48kHz, where each audio channel carries a specific frequency: e.g. channel 1= 200Hz, channel 2= 400Hz, etc.; up to 64 channels.

Note that it is not possible to configure the app to output audio test tones only, however, the video sender can be left unconnected if it is not required.

For more information about the app configuration options, please see HOME TPG - App Configuration.

IP Senders and Receivers

For all HOME Apps, the available senders and receivers are pre-defined according to the app configuration options defined by the user. i.e. the number and type of I/O.

A HOME TPG has a single output and no inputs. This means that its sources and destinations are as follows:

Sources (app senders):

  • TX 1 = TPG Output

Destinations (app receivers):

  • None

When considering the app's configuration, the Output Video/Audio  Transport options determine the number and type of flows.

Note that this app can be configured to transmit Video (only); or Video and Audio. Meta streams are not supported.

Once an app is running, its actual senders can be checked and edited from the Senders page. See HOME TPG - Senders. This app has no inputs and so the Receivers page has no function.

Further controls are available via the Advanced parameters page. See HOME TPG - Advanced -> Senders.

Connecting Signals

When viewed from HOME's 'Stream Routing' page, the app's senders appear in the Sources list (as shown below).

HOME uses the following naming convention for the sender: <App Label> / TX n, where the App Label is provided by the user (and can be edited via the  Edit Device Info  dialog).

If both video and audio flows are configured, then the flows are grouped so that they can be connected in one operation. By clicking on the reveal arrow, you can expand the sender group to access the individual flows. This can be useful if you need to deviate from the default routing. For example, to connect the TPG video and audio to different devices.

To connect the app's output using the 'Stream Routing':

  • Choose the TPG sender on the left (e.g. Test Pattern Generator / TX 1), and a suitable destination on the right. Then press Connect.

For more information, please see  HOME Apps - Connecting Signals.

Editing an Existing App

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.

How to use the individual app pages is described in HOME TPG - Reconfiguring an App.

Parameter Control

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.

All possible controls are described in HOME TPG - Advanced parameter control.