Skip to content

Setup d3Net

d3Net Manager

d3Net Manager is a UI widget in Designer that is used to setup a Director/Actor/Understudy network.

To open d3Net Manager:

  1. Open the Program Settings menu by right-clicking d3 from the d3 State editor (bar at the top of the screen).
  2. Left-click d3Net Manager in the d3Net tab.

d3Net manager

d3Net Manager properties

d3Net manager

d3Net Manager can be configured to contain all of the Disguise machines in the Director/Actor network. These machines are represented by virtual machine objects.

The Actors, Understudies and main sections of the d3Net Manager (described in greater detail below) are used to create an Actor, Understudy or Director machine.

Disguise media servers can act as any of the roles in combination with any other media servers Except for the following models which have some restrictions (outlined on their respective pages):

Director

The role of the Director is to control any Actors and Understudies running within the session. Any session with multiple machines (even editors) must have a director assigned.

Dedicated vs Non-Dedicated Directors

Directors can either be Dedicated or Non-Dedicated. This changes the way the director will display content.

  • A Dedicated Director will render content on all screens in the visualiser and all displays included in it’s assigned Feed Scene. This is intended for previsualisation.
  • A Non-Dedicated Director will only render content on displays included in it’s assigned Feed Scene. This is an optimisation feature to maximise performance of output content.

Non-Dedicated Directors are not as performant as Actors, because they are also responsible for managing the session and rendering the GUI.

Actors

The role of the Actor is to output video from the project timeline of the Director running in session. Each Actor will output according to its assigned Feed scene. The first output on the Actor machine, which is usually used for a GUI monitor on the Director machine, can also be used as a display output.

Understudies

The role of the Understudy is to take over from either the Director or Actor in the event of failure. The machines the Understudy should take over can be chosen from the Understudy targets section of the machine editor. For more information please scroll down to the section Understudy targets below.

Editors

The role of the Editor is to make edits to a project that are then shared to the Director in real-time. Read more about setting up Editors in the Setup Editors chapter.

Failover Timeout

The amount of time in seconds until the Understudy automatically takes over from the failed machine. Note that the value 0 disables this function.

Failover Normal preset

The default matrix preset when all machines are functional and outputting their assigned Feed scenes. Read more about matrix presets in the Matrix & Switches subchapter.

Machine editor

To open the Machine editor, right-click the machine from the Machines manager or the d3Net manager.

d3Net manager

Host Name

The Hostname of the machine. This can be selected from a list of discovered machines in the d3Net network, opened by left-clicking the arrow.

Network manager monitors the health of the Actors using their frame rates

The failover section of the Network manager monitors the health of the Director and all of its Actors using frames-per-second readouts. For more information on frame-rate readouts please scroll down to the section ‘Monitoring Actors’ below.

Type

Each machine can be set as a certain type. Changing this value sets the capabilities of the machine for Video Input Patch and Audio Output. The value is auto-detected when the Disguise machines are connected. When machines are disconnected (for example when building your project in Disguise Designer) you can specify the type manually.

Feed

Assigns a specific Feed scene to the machine. The Feed scene contains specific outputs and can be created directly from the d3Net manager. Alternatively, Feed scenes can be created and configured before assigning them to a machine using the Output Feeds level. Please see Switching Feed scenes for more information.

Audio

Controls how audio is outputted from the machine.

  • off disables all audio from the machine
  • timeline only plays audio from the Timeline
  • video files only plays audio from video clips only
  • on enables all audio.

Typically this property is used to allow audio from video clips to play through a PA whilst suppressing the Timeline audio, which is used for reference purposes on the Director only.

GUI

Controls whether to start up with the GUI; options are off when Actor, always on and always off.

Matrix Control

This is a preset number to be automatically sent to the Matrix by the Understudy when one of the machines fails. A preset number should only be set in the Director and Actor machines. In case of a machine failure, that machine’s preset number will be sent to the matrix by the Understudy.

You can also enter the information for which input on the matrix each head on the machine is connected to for Direct Matrix routing. For more information please see the Direct Matrix routing subchapter.

If there are multiple matrix devices Designer will send the same preset to all matrix devices in the Devices manager list. For step-by-step instructions on how to create a device please see the Creating devices subchapter.

Alternate feed

Specifies the alternative Feed scene the Understudy should switch to if one of the machines fail. If set to None, the Understudy will switch itself to the standard Feed scene specified in the previous property. This is mainly used if the Understudy’s Feed scene has different output head size settings than the machine it is replacing. Please see the explanation of the Feed property above for information on how to create Feed scenes using the Output Feeds level.

Understudy targets

The machines the Understudy should take over can be chosen from the Understudy targets section of the Machine editor. However, in order to see this section:

  1. Create an Understudy Machine. When creating an Understudy, leave the Feed property (described below) blank. This is because it should be able to use any other Feed scene assigned to the failed machine.
  2. Close and reopen the Machine editor. A new section called Understudy targets will now exist at the bottom of the editor.

d3Net manager

Understudy targets section of the Machine editor is used to add machines the Understudy should take over

If no machines are added to this list, then the Understudy will take over from any machine on the network.

If a Matrix device has been added to the system, the Understudy can be configured to send a preset command to the connected matrix device.

File distribution in a Director-Actor network

Once the d3Net manager has been set up correctly, copy the specific Project folder to all of the Actor and Understudy machines in the network. The video files must be distributed in such a way that every machine has all of the content files it will need to play during the show. For information on where the specific Project folder is located please see the subchapter Projects location.

Remote control service

The Disguise machines are installed with a Windows services, named d3Service. When starting Designeron the Director, the Director automatically sends out a start Disguise network command, which attempts to start the Actor(s) with the specific project. When the Actor machine starts, it looks at the d3Net manager, identifies itself in the list and switches automatically to its assigned role and Feed scene.

Monitoring Actors

The Director machine can monitor the health of all of its Actors. By default, the bottom right corner of the Disguise screen contains a frame-rate readout showing the number of frames Designer is outputting per second (fps).

  • 60 fps is the optimum frame rate and indicates a healthy machine by showing in green;
  • <60 fps is unhealthy and shows in red.

If you select a 50Hz output mode, a smooth 50 fps shows as green.

The Number of frames in Designer is outputting per second in this example is is a healthy 60 fps.

In Director mode, the frame readout will be accompanied by a readout for each Actor. If the Actor is not running for any reason, the readout will be in red with a - instead of a number.

In Director mode the Director machines readout will be accompanied by a readout for each Actor.