How can we help?

Have confidence in your productions with exceptional 7-day a week support.

What does (and doesn't) get sent to the backup machine when using Network Backup Triggering?

The Network Backup Triggering (built into PVP 3.2 and later) allows you to have one or more backup machines ("slaves") connected to your primary computer. This feature will have the primary computer send commands to your backup machine(s) so that you can quickly switch to them if needed. But what exactly is sent to the backup computers and what is not? Here we will dive into what features will be shared with your backup computer(s) and what won't be triggered on those machines.

There are several ways that the primary computer will (or won't) share information with the backup machines. We will explore each of these below.

Name Matching

Some areas of PVP will trigger on the backup machine based on their name. For example, clicking on a Playlist called "Set 1" on the primary computer will have any slave computers search for a Playlist called "Set 1" and select it if it finds it. Note that Name matches are case sensitive.

Examples of this would be:

  • Playlists
  • Targets
  • Effect Sets
  • Layer Presets

ID Matching (Ordinals)

Some areas of PVP will trigger on the backup machine based on the "ID"; that is, the order in which they appear on the user interface. For example, if you click on the third Layer on the primary computer, it doesn't matter what the names of the Layers are, it will select the third Layer on the backup computer(s). You can think of this as "ordinals" (1st, 2nd, 3rd, etc.).

Examples are:

  • Layers
  • Most items inside of Layer Strips
  • Cues

What doesn't get transferred

Some parts of PVP will not get sent via the Network Backup Triggering feature to the backup machines. Primarily this would be anything that doesn't send a "command" to or directly change the output directly, however, there are some exceptions to this.

Examples of items that are not shared with the backup computer(s) are:

  • Changes to the Graphic User Interface (GUI) such as scaling thumbnails larger and smaller or switching between the Cue and Action views
  • Renaming or changing the color of Layers
  • Editing Cues in any way such as changing their name or editing actions via the Cue Inspector
  • Making changes in the Workspace Editor
  • Selecting the Live Video Playlist or firing any cues from the Live Video Playlist
  • Enabling and disabling the Master Output

Comments

0 comments

Article is closed for comments.