Loading...

The Multi-User tab in Pandoras Box allows to setup the Multi-User feature and gives an overview on all Places (i.e. Multi-Users) online with their IP address and network name. The tab is not contained in the default view. To open it, go to the Menu Bar and choose Tabs > Multi-User.

The Multi-User Feature in General

Pandoras Box version 6 introduces the Multi-User feature allowing several operators to work on the same Master file. As the ways to build shows with Pandoras Box are so versatile, Multi-User editing is a flexible feature. This means that you can choose what exactly you would like to synchronize and how often or when you would like to do so.
As soon as another Master (without Output Layers!) is in the same LAN network and shares the Domain it can participate as another Multi-User. Output Layers cannot be added to participating Masters. The new tab Multi-User allows to setup the Multi-User environment and gives an overview on all Users online.

The first possibility for Multi-Users is to work in a "Sync Session" where all changes are synced continuously and seamlessly between all Users. However, you can also activate the "Blind Mode" within the Sync Session for working with an independent Nowpointer and Active Values. This allows you for example to jump to "your" time in the Sequence to store content or to view content in the Preview.
You can leave and (re-) join the Sync Session at any time. When joining a Sync Session you are asked to load the session project.

Alternative to (fully or partly) synchronized programming, you can work asynchronously in a separate project and send ("push") your changes at a certain time, e.g. checked or newly encoded content, warp and softedge settings, parts of a Sequence, etc. The "Run Operation" button in the Multi-User tab opens a dialog to define these Pull and Push Operations.

All settings that are listed in the Global category in the Configuration tab apply to all Multi-Users whilst the other ones apply only locally. The User category now features profiles which are shared with others so they can apply one of them too. This is explained below in more detail.

Setting up a Sync Session

This Multi-User tab shows that there are two Places (= two Users) online. They are in the same network, share the same Domain and the Master software is started. The User Profile is displayed too.

Multiple Masters in the same LAN network (and Domain) participate automatically as Multi-Users. Now they have the choice to work in a Sync Session. As a possible scenario for a Sync Session, imagine, for example, that one operator is assigned to the Warping job whilst another one previews and arranges content in the Project tab and a third operator wants to setup the connection to Clients and their output resolution.

The first Master (from now on the Main Master) clicks the button "Start Session" in the tab. All Clients will automatically connect to the Main Master. His project becomes the so called Session Project.
All other Masters have then the option to join this session. Alternatively, the Startup menu offers the possibility to start a project and a sync session directly and to join one.

When other Masters join, they are asked to load the Session Project and become Sub Masters. A Sub Master can control a Client but the connection is through the Main Master. Important note: If a Sub Master chooses the command "Take Over All Sites in Domain" (from the Backup Menu or the Assets tab) he will become the Main Master!
Sub Master can leave and (re-) join the Sync Session at any time. Please note that other Users are not notified if somebody leaves the session.
The ASIO audio settings in the Configuration tab allow to choose an "Audio Clock Master". Only the Main Master or any Client with a setup ASIO device can be chosen. Sub Masters cannot be clock masters, but only slaves.

The Multi-User tab shows the status next to each system, e.g. "in Sync Session". The status bar shows "MAIN" or "SUB" in the right corner next to the version.

As described above, all Masters are (in-)directly connected to the Clients. In the Device Tree, Clients are shown with the same icon. Either it is the connected one, or the one with the red exclamation mark on top in case the Client is not connected. The icons in the Main Master are colored white as usual. The icons in all Sub Master are colored in beige to emphasize that the connection is through the Main Master.

In short: the Main Master is connected to the Clients, hosts the Sync Session and can be the clock master. As described below, he cannot enter the Blind Mode.

Within a Sync Session all changes are synced between all Users, including the:
- Device structure (for the Device Tree and Sequence),
- Sequences (with all Containers and Cues),
- Resources (meaning folders and content in the Project tab),
- Active Values and Sequence Playback (if not in Blind Mode).

Tip: In a Multi-User setup you might not want to spread all content to all Masters. First, deactivate the Auto-Spread option in the Configuration tab > Resources (Global). The right-click menu in the Project tab then offers options to spread content or folders to specific sources. In addition, the Folder Inspector offers spread options.

Troubleshoot: In case you encounter problems like not seeing another User, please check your network. Make sure that the ports used by Pandoras Box are not blocked (firewall, anti-virus applications, configurable switches etc.). If you are using configurable switches and would like to use IGMP Snooping, make sure that ALL switches in your network are configured accordingly. Otherwise, IGMP Snooping can be deactivated as well.

Blind Preview and Blind Programming

As explained above, all project data is synced in a Sync Session. If you would like to detach the Active Values and Playback status (including the time for the Nowpointer), you can activate the option "Blind Mode". Note that this option is only available for Sub Masters (those that join an existing session). You can either click the according button in the Multi-User tab or the last icon in the Sequence Button Bar above the timeline. Now you can use the partly synchronized Master as a Blind Preview system or a Blind Programming system. It is for example possible to change the timeline to the next cue and preview or verify the content. Or you can edit the scene by activating parameters and storing them to the timeline without interfering with the current output of the show. However, you need to make sure to not work at the time from the Main Master's Nowpointer! Note that content spreading also uses performance on the Main Master. When the Blind Mode is activated, the Multi-User tab of other systems will display the status: "In Sync Session" and "Is in Blind Mode".

Local and Remote Active Values

With the possibility to synchronize active values, the necessity arose to distinguish local active values from remote active values. If active values are synchronized, their effect in the Preview is visible for all Multi-Users. However, the programming behavior is different and the GUI display reveals their origin:
Local active values are highlighted in red whilst a remote active value is colored in beige / yellow.

All "Store Active" commands will only store red local active values!

You can right-click on a Parameter / Layer / Client and choose to either "Reset" (respectively "Reset All Active from Remote") or to "Take over Activity" in order to adopt them to local active values.

Note that the tab "Active Values" displays local and remote active values without distinction.

Remote active values can only exist in a Sync Session without an activated Blind Mode. Hence, they dis-/appear when you toggle the Sync Session state or the Blind Mode on or off. In addition red local active values may change. Please see the following diagram.

Saving and Loading Synchronized Projects

The "Save" and "Save as" option save the session project on all synced systems. The chapter "File menu" difference between both options, and the third saving option "Save as Copy" are

When starting with all Users on another day, the Main Master loads the project and starts the session again. All others can then join it as usual. This option is also included in the Start-up dialog. Note that the saved project data does not include information about other Users.

User Profiles

Since Pandoras Box V8 you can save specific settings from the Configuration tab in so called User Profiles. Per default, User settings apply to the local instance only. However, the profiles are part of the project and also synced with all Multi-Users. Note that if no other profile is created and selected, all Users rely on the "Default" profile. This has the result that changes done locally are synced and applied to other instances too. But any User has the choice to create or select an individual profile. All profiles except the "Default" one can be renamed or deleted, which again is synced. Keep in mind, that profiles must have a unique name and cannot be deleted if another Multi-User uses it. Read more about User Profiles in the chapter "Configuration".

Asynchronous Programming

So far, continuous synching was explained. For some events however it might be more convenient to not sync every small step but to work asynchronously, at least for a certain time until a more or less final state is achieved and should be shared.
Before you begin, it is recommended to decide for a hierarchy as it makes sense that there is a leading Master to which all others send their selected project data.

First, decide whether you want to work in a separate project or whether you want to start with the same project that includes for example already some Clients with named Layers and some Resources in the Project tab. For the later case, there are two possibilities. First, you can open a Sync Session as described above and leave it again after having synced the project once. Alternatively, one Master loads the project. All other Users open the Multi-User tab and click on the "Run Operation" button depicted next to the network address and name of this Master. This opens the "Edit Multi-User Operation" dialog where the drop-down menu offers the possibility to "Pull Project" which copies the project to the local system.

Now every operator can work in his own project and click the "Run Operation" button whenever he needs to.

Run Operation

As described above, the "Run Operation" button is for operators who program asynchronously. If the operator likes to distribute (parts of) his work, he clicks the "Run Operation" button depicted next to the network address and name of another Master. This opens the "Edit Multi-User Operation" dialog where the drop-down menu offers the following possibilities:

TCP and Art-Net Output

In MU scenarios, DMX devices as well as the TCP device  or Widget Devices will behave similar to regular Site. This means they will "manifest" onto the Main system and will not send out any data from Sub Master. Therefore the Art-Net output on Sub Masters can be activated, but no value will be sent. In the event of a "takeover" the new Main Master will establish all TCP connections and start to send Art-Net if specified in the configuration. Doubled Art-Net output is prevented the same way as TCP or WD commands are not sent twice.