A HOME DSK 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 DSK.

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 DSK

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 DSK, the options in the app configuration define the number of keyers and the app's input and output streams.

A HOME DSK supports up to three independent key layers over an A/B background mix. Each keyer provides a Key and a Fill input, can be controlled separately and operates in one of three keying modes: Luma, Linear or Self-Key. Underneath the keyer(s), the app allows for A/B mixing of two video background sources. This can provide 'Make-Before-Break' type switching with a choice of transition types including Cut, Fade and Cross Fade. 

Note that the Number of Keyers defines how many input receivers are provisioned. This can be used to save input receiver resources if not all three keyers are required.

Optionally, the Advanced Audio feature can be enabled to provide gain, mute and phase control for all audio channels passing through the app. Note that this option is licensed.

Once the app is configured and running, parameters such as the keying mode, transition type, etc. can be adjusted from the app's Advanced menu: see Advanced -> Video Keyer Controls and Advanced -> Video Mixer Controls.

For more information about the app configuration options, please see HOME DSK - 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 DSK has two outputs (Program and Preview) and two inputs (Background A and Background B), plus a further two inputs (Key and Fill) for each configured Keyer.

If all three Keyers are configured, then the available senders (TX) and receivers (RX) are as follows.

Sources (app senders):

  • TX 1 = Program Output
  • TX 2 = Preview Output

Destinations (app receivers):

  • RX 1 = Background A
  • RX 2 = Background B
  • RX 3 = Key 1 (defined when Number of Keyers ≥1)
  • RX 4 = Fill 1 (defined when Number of Keyers ≥ 1)
  • RX 5 = Key 2 (defined when Number of Keyers ≥ 2)
  • RX 6 = Fill 2 (defined when Number of Keyers ≥ 2)
  • RX 7 = Key 3 (defined when Number of Keyers ≥ 3)
  • RX 8 = Fill 3 (defined when Number of Keyers ≥ 3)

When considering the app's configuration, the Number of Keyers option determines how many Key and Fill receivers are provisioned; the Video/Audio Transport options determine the number and type of flows.

Each output is configured separately, and can transmit the following streams: Video (only), or Video and Audio.

For the inputs, the Keyers do not support audio and so there is a difference between the stream (essence) types that can be received:

  • Background A and Background B - Video (only), or Video and Audio. 
  • Key n and Fill n - Video (only).

Once an app is running, its actual senders and receivers can be checked and edited from the Senders or Receivers page. See HOME DSK - Senders and HOME DSK - Receivers.

Further controls are available via the Advanced parameters page. See HOME DSK - Advanced -> Senders and HOME DSK - Advanced -> Receivers.

Connecting Signals

When viewed from HOME's 'Stream Routing' page, the available senders and receiver appear in the Source and Destination lists (as shown below).

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

In addition, for the HOME DSK, the IP sender and receiver names have a suffix that describes their function within the app. e.g. 

  • <App Label> / TX 1 - Program
  • <App Label> / TX 2 - Preview

If the senders (or receiver) are configured to handle multiple flows, then the flows are grouped so that they can be connected in one operation. By clicking on the reveal arrow, you can expand a sender (or receiver) group to access the individual flows. This can be useful if you need to deviate from the default routing. For example, to connect a different audio source to a DSK Background audio receiver.

The steps below describe how to connect the app using the 'Stream Routing':

  • To connect a signal to the DSK Background A input: choose a suitable source on the left, and the DSK receiver on the right (e.g. DSK 1 / RX 1 - Background A). Then press Connect.
  • To connect the DSK's Program output to a destination, choose the DSK sender on the left (e.g. DSK 1 / TX 1 - Program), 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 DSK - 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 DSK - Advanced parameter control.