Compere runs on different 7thSense devices performing different roles. This role might be ‘Juggler’, ‘Actor’, ‘Conjurer’. The common thread is that they all read from the same project ‘stage-management’ script, called the project, which instructs them how to act. The script is managed by the project group server, receiving and distributing all edits to the script. The script profiles every element of every connected device, so contains all the connections in, out and between the devices. The script itself is written mainly via the Compere UI, which can be done from any PC with Compere installed. Typically, this will be a dedicated control PC, but it doesn’t have to be. Scripts can be edited and projects managed via external control commands.
The Performers
Compere runs in the Juggler performer role on every Juggler device. Jugglers are first physically connected to each other, to the network and to related devices (see Juggler operating guides and Connecting a System in this guide) and are then connecting internally, from inputs to outputs via whatever processes are required.
Compere runs on R-Series server devices in the Actor and Conjurer performer roles. These provide media inputs and outputs, run the Actor render engine, interact with generative engines and media sources, managing the asset base.
Helpful for new users:
➢Terms and Definitions in Compere
Project Group, Server, Clients
The Project Group
Active instances of Compere, on any device, that have a shared involvement in a project, together form and join a project group. This will include all the Jugglers, as well as Actor or Conjurer devices, plus a control PC that plays a part in managing the project.
The Server
One, and only one, instance of Compere in a project group has the role of server to the rest as clients. This role includes owning the project script, receiving any changes to this from clients, and redistributing any changes to the rest of the project group. The group elects a server according to user-assigned scores.
Compere has a mechanism for server failover whereby other devices can be assigned in cascade to take over. When a server failure is detected and internal ‘election’ is automatically called to assign a new server from the client pool (see Server Failover Configuration).
The Project and the Group
The server loads the project file and distributes it to all group clients in memory. Any member of the group can make changes to the project – the server listens and shares the changes with all members to update them. The project can in this way be wholly dynamic, receiving changes via the Compere user interface or by external control commands, constantly changing and responding. At any time, the state of the shared project can be saved by the server. If not, the next time the project is loaded by the server, it will revert to the last save and share that again will all group members.
Server Election
If the server goes absent from the project group for any reason, the project will keep running in memory on each other member, because all clients still hold the script as last edited. Intercommunication pauses until there is a group server again. A client will automatically be elected to become the server, based on the pre-assigned scores.
The Control PC
The function of the control PC is to be able to use the graphical interface to view and edit the project group and all its members and their roles, and/or to be used for external control. Any device running Compere can join a project group in order to supply the user interface for editing and control. If more than one member of the project group is using the control UI, this is notified in the Status Bar. Under Preferences a control PC can ‘Use Local Render Settings’ to avoid conflicts between simultaneous users who may be undertaking different tasks.
|
Network (all devices)
To start, the network that the Juggler system and associated devices live on needs to be set up in Compere, selecting the devices to take part in a project (see Network Configuration).
Canvas (Jugglers)
The function of Jugglers in a project is to assemble one or more shared visual canvases between them, i.e. a combined total pixel space. These pixels may be displayed anywhere in the real world, and you will place individual inputs into the system onto any number of locations in this overall space. Each Juggler in a system has the advantage of handling a range of input and output connection standards, including (depending on Juggler type) DisplayPort™ 1.2, HDMI® 2.0 and 12G SDI and ST 2110, and when put on a common fibre-optic data bus they can share a single extremely large canvas.
You will now configure where the received (input) pixels will be displayed within the total output canvas ‘map’ available to the Juggler system. This is done in Compere’s Canvas assembly panel. In the overall canvas you will define canvas outputs delivered by the output devices. Inputs are assigned to canvas windows anywhere within these areas. It won’t matter if the window is spread over multiple outputs; all pixels in the total canvas are available to the Juggler system.
Juggler systems can accommodate multiple canvases.
Calibrated canvases can be imported as MPCDI files.
Juggler Nodes
The next task is to describe the connections of the Jugglers so that source devices address the appropriate inputs, and outputs are assigned and configured to the right display devices. You have wired the outside world; the inside world of the system is ‘wired’ in Compere. This is all done in Compere’s Juggler view, in the Nodes assembly panel. Here you will add representations of all the Jugglers in your system, connect up any data bus that the system shares (see the appropriate Juggler Operating Guide), and connect media streams from anywhere in the system, insert media processes, through to display devices and areas anywhere in the system.
Media throughput: NDI® Monitoring
When everything looks right, you want real media to play onto your canvas. You might want to use simple colour or numbered media per channel to start with, to check all your flows. Compere also provides NDI Monitoring (an option in the properties of each Juggler). This enables you to visually trace media input, from timelines, direct capture, through outputs and into canvas windows all from within the Compere UI.
External Control
Everything in a Compere system has its own unique label (UUID). Any of its components or properties, including position, size, opacity, visibility, projector beams etc. can therefore be addressed remotely using External Control commands and a show controller.
➢See M710 Compere JSON External Control Protocol in our PDF Library
Page edited [d/m/y]: 18/07/2024