1. Manuals
  2. Brands
  3. 7th Sense Manuals
  4. Computer Hardware
  5. Pixel Processing Juggler
  6. User manual

7th Sense Pixel Processing Juggler User Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Pixel Processing
Juggler
User Guide
M512-3

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Pixel Processing Juggler and is the answer not in the manual?

Questions and answers

Related Manuals for 7th Sense Pixel Processing Juggler

Summary of Contents for 7th Sense Pixel Processing Juggler

  • Page 1 Pixel Processing Juggler User Guide M512-3...
  • Page 2 Juggler : User Guide Trademark Information The 7thsense logo, and various hardware and software product names are trademarks of 7thSense Design Ltd. Product or company names that may be mentioned in 7thSense publications are tradenames or trademarks of their respective owners, and such trademarks may also be registered in their respective countries.

  • Page 3: Table Of Contents

    Contents Introduction Juggler and Compere System Architecture What Juggler Can Do Front Panel: Controls Front Panel Display Set Juggler Static IP and Subnet Rear Panel Connections Input and Output Options GPIO HD-BNC Ports GPIO Genlock Example Workflow: Create a Juggler System Connect a Juggler Optical Data Bus Connecting to a Network and Devices Compere on Jugglers...

  • Page 4: Contents

    Contents Network Configuration Create a Project Group Display Configuration: Canvas Setup Canvas Output Setup Canvas Window Setup Create and Recall Canvas Arrangements DIsplay Setup via MPCDI Nodes: Connecting Juggler Systems Input / Output Connector Properties Bus Connections in a Juggler System Connecting Inputs and Outputs EDID Spoofing 3D Passive to Active Conversion...

  • Page 5: Contents

    Contents Command Line Arguments Troubleshooting a Juggler System Juggler Physical Specifications Rack Mounting Jugglers Juggler Care and Maintenance Warranty, Support and Service Regulatory Compliance Document Information Index M512-3 Juggler : User Guide © 2021 7thSense...

  • Page 6: Introduction

    Introduction Introduction Juggler™ and Compere™ go together. Juggler is the hardware that processes the pixels and Compere, like an event manager, is the control software and user interface that tells one or more Jugglers what to do. Together, any range of digital inputs can be transformed and directed to an any range of outputs, because Juggler modules can be daisy-chained on a data bus to expand inputs, outputs and bandwidth as required.

  • Page 7: Juggler And Compere

    Juggler and Compere Juggler and Compere For a first-time user, the concepts of the pixel processor can seem a bit confusing, so here is an overall picture of how the key components work together. Why Juggler? Juggler is not just a standalone rack module. We imagine it as stage performer in an event, where as many Jugglers and other performers as you want can join, take part, or leave, all under the direction of a Compere, or stage manager that holds the event together.
  • Page 8 Juggler and Compere All the details and settings are held in the Project file, which governs how every member of the Project Group behaves. Whichever instance of the Compere software takes control (the one assigned as server), like a stage manager, coordinates and distributes this set of stage instructions to all instances of Compere, which includes every Juggler in the Group.
  • Page 9 Juggler and Compere Ø Physical Specifications Ø Rack Mounting Jugglers Ø Care and Maintenance M512-3 Juggler : User Guide © 2021 7thSense...

  • Page 10: System Architecture

    System Architecture System Architecture Every Juggler has four video processing channels. · Each Juggler unit has a flexible design for provisioning a number of inputs and outputs of various · and mixed types. Jugglers can be daisy-chained by utilising a high capacity data bus. ·...

  • Page 11: What Juggler Can Do

    What Juggler Can Do What Juggler Can Do Here are two examples of Juggler applications that demonstrate its potential roles. Example 1: IntelligentSource™ failover Use cases: Ultra-reliable auto failover, per input, or whole system, seamless source switching A large 16K × 4K canvas ·...
  • Page 12 What Juggler Can Do M512-3 Juggler : User Guide © 2021 7thSense...

  • Page 13: Front Panel: Controls

    Front Panel: Controls Front Panel: Controls Power button Juggler must first be connected to an appropriate power source using the supplied IEC power cord. The front panel power button will show a dim blue ring indicating this connection. Press and release the power button to start the unit.

  • Page 14: Set Juggler Static Ip And Subnet

    Front Panel: Controls Video tab This tab provides a direct NDI display of media being processed by the unit, as a row of video channels 1 to 4. Info tab This shows the Juggler name, IP addresses, network mode, Project name and connection status, and a second swipe-to page for editing the static IP address and subnet.
  • Page 15 Front Panel: Controls On the number pad: . (separator) moves to the next octet C (clear) sets the selected octet value to 0 Touch ‘Reset’ to undo all changes, or · Touch ‘Apply’ and then Confirm the changes: · M512-3 Juggler : User Guide ©...

  • Page 16: Rear Panel Connections

    Rear Panel Connections Rear Panel Connections The back panel of each Juggler is factory configurable to order. The required number and type of inputs and outputs for a system of Jugglers is expandable by adding Juggler modules as required. Working from left to right, these connections are available: JTAG Service use only.

  • Page 17: Input And Output Options

    Rear Panel Connections The same orientation is true for fibre-optic modules, but these are keyed. If using the 4-lane ‘half’-bus option to daisy-chain Jugglers, see Connect a Juggler Data Bus : ‘Half bus’. Important! Only SFP modules approved by 7thSense should be fitted to the Juggler unit, fitting non- approved SFP modules may cause damage to the Juggler or prevent the unit operating.
  • Page 18 Rear Panel Connections There are three types of internal connection in a Juggler or a Juggler system: 1. Some Juggler inputs may match its outputs directly, for example providing layers from a media server to a whole-canvas background, requiring no processing on the way. These can save bandwidth by using the ‘Bypass’...
  • Page 19 Rear Panel Connections Data bus Each Juggler has four processing channels. By bussing Jugglers together, additional processing channels can be added to the Juggler system. To bus Juggler modules together, use optical fibre cables. Full 8-lane bandwidth MPO I/O ports (shown yellow) may be used, or 4-lane SFP modules (shown magenta).

  • Page 20: Gpio Hd-Bnc Ports

    Rear Panel Connections GPIO HD-BNC Ports Each Juggler back panel has four HD-BNC connnectors. These can be independently designated as inputs, or outputs that can be assigned to the Juggler’s video channels, in the Juggler properties of Compere. All Juggler ports are configured independently in Compere. Here is the GPIO section in Juggler properties: Name Identifies the physical GPIO.

  • Page 21: Gpio Genlock Example

    Rear Panel Connections These GPIO ports can also be used to support genlocking. For example, on one Juggler in a system, GPIO:1 can be used to collect the VSync of a media input, pass it out to GPIO:2, collect on GPIO:1 of the next, out from GPIO:2 and so on to daisy-chain down the line.
  • Page 22 Rear Panel Connections Its GPIO:1 is set to be an output, using its GPIO:2 as its source (the signal need not be specified). This is repeated down the line, the last of course not needing to be assigned a sending GPIO. Connections Five Jugglers would therefore be cabled as follows: Genlock Mode...
  • Page 23 Rear Panel Connections M512-3 Juggler : User Guide © 2021 7thSense...

  • Page 24: Workflow: Create A Juggler System

    Workflow: Create a Juggler System Workflow: Create a Juggler System Configure the Connections: physical 1. Unbox Jugglers and perform an all-round physical check for any signs of transit damage. 2. Rack the Jugglers so that the units are fully supported at the back and bolted securely at the front.
  • Page 25 Workflow: Create a Juggler System Assemble your display output Note that if your Juggler configuration is for MPCDI display input, Canvas, Outputs and Windows will be imported with the data and do not require intervention. 8. In the Compere Canvas assembly panel , create your overall canvas to size.

  • Page 26: Connect A Juggler Optical Data Bus

    Connect a Juggler Optical Data Bus Connect a Juggler Optical Data Bus Jugglers in a system should be racked adjacent to each other, since optical connections must be short and loop freely. If you are using multiple Jugglers on a data bus, make these connections first, before inputs and outputs;...
  • Page 27 Connect a Juggler Optical Data Bus 4-Lane ‘Half’ Bus Using the ‘half-bus’ optical transceivers, Juggler modules can be bused together using on-board SFP modules. Each fibre optic cable carries 1 lane in each direction. Units are daisy-chained progressively unit to unit, 1 to 3, 2 to 4 and loop back from the last unit to the first in the same way.
  • Page 28 Connect a Juggler Optical Data Bus Bus Configurations Current modes of operation are: bus the complete canvas · bus individual inputs · bus thumbnails for monitoring purposes. · We configure your Juggler system based on your requirements. Care with Optical Connectors Optical connectors are a Class 1 laser product.
  • Page 29 Connect a Juggler Optical Data Bus and any contamination will affect performance or cause failure. Avoid troubleshooting by inspecting first. Inspect before you connect Hand-held fibre inspection microscopes may seem expensive, but prevention is cheaper than troubleshooting, and it is essential to ensure optical connector end-faces are clean before you connect.

  • Page 30: Connecting To A Network And Devices

    Connecting to a Network and Devices Connecting to a Network and Devices Juggler systems must be connected on a single network each with a static IP address . All devices running Compere will be visible in any Compere UI, along with their host names, where their network binding NICs can be assigned along with their roles and any descriptive comments.

  • Page 31: Compere On Jugglers

    Compere on Jugglers Compere on Jugglers Compere is already installed for the internal operation of each Juggler on Linux. It handles all system communications including the front panel display. To configure your system over the Juggler network, install Compere on a local PC on the same network. Versions Juggler projects require compatible versions of the software.

  • Page 32: Compere Mingui

    Compere MinGUI Compere MinGUI Running Compere with the full graphical user interface and controls is CPU intensive. The Juggler Atom CPU runs without this, as client or as server, but also drive the front panel display for information and with a limited set of touch controls. There can be a case for using a PC with a lower than recommended specification as a project group server, but not as a control PC with the full UI.
  • Page 33 Compere MinGUI Installation of Compere is otherwise the same as for the full user interface for a control PC: Ø Installing Compere on a Control PC M512-3 Juggler : User Guide © 2021 7thSense...

  • Page 34: Introducing Compere Ui For Jugglers

    Introducing Compere UI for Jugglers Introducing Compere UI for Jugglers Once Jugglers have been physically connected to each other, to the network and to related devices (see Connect a Juggler Data Bus Connecting a System) they need connecting internally, from inputs to outputs via whatever processes are required. This is all achieved using Compere’s UI on a control PC, to create a complete ‘stage-management’...

  • Page 35: Installing Compere On A Control Pc

    Introducing Compere UI for Jugglers 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 .
  • Page 36 Introducing Compere UI for Jugglers Minimum requirements A control PC to run Juggler need not normally be of particularly high spec., but memory and number of cores govern performance. For system configuration: Minimum quad-core, Intel® Core™ i5 processor · 16 GB RAM (recommended) ·...

  • Page 37: Terms And Definitions Used In Compere

    Introducing Compere UI for Jugglers Terms and Definitions Used in Compere We use a lot of terms that are specific to the Juggler-Compere world, so it’s worth being familiar with them. Tooltips are implemented throughout Compere, with longer descriptions for labels in panels and toolbars.

  • Page 38: The Compere Juggler View

    Introducing Compere UI for Jugglers Term Definition Network Discovery The tab in the Network Configuration panel that lists and profiles all available Compere hosts on the network. Network Server Network device assigned as communication ‘project controller’ across all devices. Nodes panel The assembly panel in which connections between devices and processes are made.
  • Page 39 Introducing Compere UI for Jugglers When you join a network with the Compere UI on a PC, all Jugglers available on that network will be represented in the Project panel on the left side. They will be in a group under a title that shows how many are present.
  • Page 40 Introducing Compere UI for Jugglers The initial default ‘Juggler’ Layout comprises: the main (top) menu · the main toolbar area · the ‘Project’ panel (default: upper left), listing all configurable elements · the ‘Properties’ panel (default: right) for any selected element in a Project ·...
  • Page 41 Introducing Compere UI for Jugglers The Project panel is a branching structure of all elements connected in a system, including Jugglers, input sources and output devices, 3D models, canvases and display surfaces. These can be dragged into assembly panels as appropriate. When you start Compere for the first time, you will find a new empty Project.
  • Page 42 Introducing Compere UI for Jugglers Add, Select, Edit, Remove, Delete objects Objects can be dragged from the Resources panel onto an assembly panel. This simultaneously · adds them as branches of the Project panel. Objects shown in the Project panel can be dragged into an assembly panel. ·...

  • Page 43: Using Compere Layouts

    Introducing Compere UI for Jugglers Nodes This assembly panel creates all the throughput connections and processes within the Juggler system. Representations of each Juggler are shown here, with each video interface connector (bus and AV inputs and outputs), along with information on external connections and internal routing. Nodes is the assembly panel where you configure everything that comes into and goes out from each Juggler, and how these are connected and processed internally.
  • Page 44 Introducing Compere UI for Jugglers Any panel can be closed, and redisplayed from the Panels menu item. If any panel is duplicated, · these are just multiple instances, but can display different areas of the panel simultaneously. For example you may want to see different parts of a complex Project next to each other, or fill a separate display screen with a single assembly panel.
  • Page 45 Introducing Compere UI for Jugglers Assembly panel grids can be dragged around to reposition the view, and zoomed with the mouse · wheel. The Visualise assembly panel grid operates in a 3D space and can be rotated about 3 axes. General mouse and keyboard operations in assembly panels Mouse / key Action...

  • Page 46: Main Menu

    Introducing Compere UI for Jugglers Main Menu File Menu Projects Start a new Project; opens a dialog to name the Project. This is the Project name not the file name, which is given when saving a Project file. Open Open a saved Project file. This will open the Project for all connected servers in the network group.
  • Page 47 Introducing Compere UI for Jugglers Saving to an existing file name raises a warning. If you save a different Project as default, this will replace your previous selection. This is only really relevant for a Project Group server, or an offline instance of Compere UI (for example) assembling parts of a project remotely for integration later (see Save/Load Clone below).
  • Page 48 Introducing Compere UI for Jugglers Panels Menu Selected items can be used multiple times and are added undocked. Closing or undocking any these elements in a Layout does not lose any content. They can be used independently, for example on separate displays.
  • Page 49 Introducing Compere UI for Jugglers Gather Project Group Data Lists logs per Juggler in the Project Group. Click ‘Open’ to create a zip file in this location of all logs and the local Compere Preference.pref file. Network Configuration Opens the Network Discovery and Project Group panel, for configuring a network of Compere devices.

  • Page 50: Debug Menu

    Introducing Compere UI for Jugglers Show About Show the version of Compere on this device. Debug Menu By ticking ‘Enable Debug UI Elements’ in the Configuration > Preferences Panel, this additional menu is added. Its contents are for diagnosis and maintenance only: Peer Data Server-client data for all instances of Compere in the Project Group, including disk and memory usage, machine Ids and IP addresses.

  • Page 51: Status Bar

    Introducing Compere UI for Jugglers Note the server (Juggler), clients, and the Windows PC. Juggler Front Panels Replicates a front panel display of the current Compere host. ThreadComms Log Extended system logging information that can be cleared or saved. Distribute File Used to select certain systems files to be delivered to all Jugglers in the Project Group.

  • Page 52: Task Tracker Panel

    Introducing Compere UI for Jugglers In this example, Compere running this UI is in the project group ‘Auditorium’, with Juggler 4567 acting as group server to 2 client peers. The list available in ‘Peers’ shows their names and IP addresses. The symbol next to the server shows its operating system icon: Juggler (Linux), Windows or MacOS.

  • Page 53: Contextual Menus

    Introducing Compere UI for Jugglers There is a progress bar for each task and each subtask. Blue progress will change to green on completion. For longer tasks, click the arrow (here next to ‘MPCDI’) to expand the list for progress of subtasks.
  • Page 54 Introducing Compere UI for Jugglers Contextual menus typically have two sections when called for an object rather than the containing panel. The upper section relates to the panel in general, the lower part to the selected object. In this example, the interaction mode is ‘Window’, so the two-part right-click menu contains generalised options such as Zoom, above object-specific options such as ‘Move Window’, which in this case has a further option menu.

  • Page 55: Preferences Panel

    Introducing Compere UI for Jugglers Some context menu items repeat the toolbar button actions. When the menu is divided, the upper section applies to all objects and the lower to the selected object(s). Preferences Panel Menu: Configuration > Preferences M512-3 Juggler : User Guide ©...
  • Page 56 Introducing Compere UI for Jugglers Search Filter properties Type (not editable) Local Preferences file location File location where preferences are stored on local machine. UDP remote transmit port UDP port number to which external control will transmit. UDP receive port UDP port number external control socket will listen on.
  • Page 57 Introducing Compere UI for Jugglers Network binding NIC Shows the IP address of the current instance of Compere. UDP discovery port UDP port used when discovering other Compere applications on the network TCP connection port TCP port on which connections will be made between instances of Compere for Project updates.

  • Page 58: Compere Projects

    Introducing Compere UI for Jugglers Compere Projects There is always a Project Once Compere runs, on a control PC or as a Juggler, a Project is always present. This is true whether offline, or in the role of client or server. If this is an unconnected instance, Compere will, on opening, start a new empty project, or run a ·...
  • Page 59 Introducing Compere UI for Jugglers Compere can be used offline – as a client but switched to offline – or as a client without a Project Group server present. Project edits while offline will not be saved or distributed, but can be exported locally.

  • Page 60: Render Settings

    Introducing Compere UI for Jugglers This will then show as the Project name in the Project panel. The name can be subsequently edited in the Properties panel. Render Settings Render Settings are the display properties of the Compere layout panels themselves. This might be to see, or to set, how or from where the panel contents are viewed, or the zoom level.
  • Page 61 Introducing Compere UI for Jugglers The orange box contains all objects. The lighter area is the current view scope and can be dragged around to view the required Juggler(s) without having to zoom out or in to find your bearings. M512-3 Juggler : User Guide ©...

  • Page 62: How Juggler Is Seen In Compere

    How Juggler is Seen in Compere How Juggler is Seen in Compere Each Juggler in a Project has its build configuration of available ports recognised by Compere, and this is exposed in the Properties and Project panels. When a Juggler is added to the Nodes panel, the build options of the Juggler are represented as connector pins: square for external and round for...
  • Page 63 How Juggler is Seen in Compere See further: Ø Juggler Properties Ø Nodes: Connecting Juggler Systems M512-3 Juggler : User Guide © 2021 7thSense...

  • Page 64: Juggler Properties

    Juggler Properties Juggler Properties Name By default, the Juggler serial number. Rename, perhaps to reflect real-world tagging or purpose in your project. Enable NDI Confidence Monitors Check this to introduce confidence monitoring on Juggler I/O connectors and in the Canvas assembly panel.
  • Page 65 Juggler Properties Canvas Select from list of Canvas names created (there may be only 1). Applies to all video channels of the Juggler (same setting as in the Juggler title bar in the Nodes panel). Warp Mode There are two current versions of Juggler firmware: warp and blend or windowing. For warp and blend units there are 3 warp modes: 1 ×...
  • Page 66 Juggler Properties Defaults Default properties relate to Juggler properties held not in the Project, but in the Juggler module’s firmware on its internal SD card. Note: If edited, you must click save data and reboot to effect any changes. SD Card The SD card inside a Juggler holds essential configuration files, including EDID, MPCDI, warp, blend and colour correction files.
  • Page 67 Juggler Properties To clear all added files, select the Juggler in the Nodes panel, and from the context menu select ‘Juggler Reset SD Contents’. M512-3 Juggler : User Guide © 2021 7thSense...

  • Page 68: Network Configuration

    Network Configuration Network Configuration Compere Roles: Server and Client Every Juggler is already running its own instance of Compere. Any PC added to the network, running Compere, provides a user interface (UI) into the network and can join a Project Group, but it does not need to remain present.
  • Page 69 Network Configuration One instance of Compere (only) is assigned as Project Group server, all others are clients. If the server fails, a different client can be configured as the Project Group server. A control PC (e.g. a laptop) is able to assign any Juggler as server. The control PC can therefore be taken away or reinserted once the system is configured and running.
  • Page 70 Network Configuration Comment Edit this for clarification of location, role, etc., for your own use. IP address Shows the current IP of each unit. Note: The internal IP range for all Jugglers is 172.30.n.n so do not use this range for your network of Jugglers and other devices.
  • Page 71 Network Configuration You must have one instance of Compere running as server per Project Group. Where the role is server, there must be a binding NIC: in the lower panel you can see details of available NICs. If joining a Group with no server, there will be a warning message to alert you here, and in the Discovery list: M512-3 Juggler : User Guide ©...
  • Page 72 Network Configuration M512-3 Juggler : User Guide © 2021 7thSense...
  • Page 73 Network Configuration You cannot have two servers on binding NICs in the same range, and an orange warning will appear to indicate any conflict. You cannot have two servers in the same Project Group. Trying to add a second will be prevented, with a red warning message displayed. Locked Secure your settings by checking this box.
  • Page 74 Network Configuration The server-assigned Compere will hold the initial configuration for the Project. The Project file can then be saved locally and as server, it will be distributed to all other instances of Compere in the Project Group. In the event of losing a server connection, any Juggler can subsequently be handed the role of server and redistribute the project.

  • Page 75: Create A Project Group

    Network Configuration ... as an online server If you are joining a Project Group that has no current server (maybe it has failed or been withdrawn), you will be asked if you want to create a new Project. If not, then as a server your current Project will be distributed to the client Group, which will be reconnected.
  • Page 76 Network Configuration You do not need to create a new Project Group unless you want more than one, or wish to name it. Each Juggler on the network belongs to the ‘Default’ Group, or can be assigned to your own Group(s). If you need only two Groups, create two new named Groups, rather than using the Default Group plus one named Group.
  • Page 77 Network Configuration Add as many Groups as you need. Groups can also be deleted and any members will revert to the Default group. The colours are used in the Discovery tab: M512-3 Juggler : User Guide © 2021 7thSense...

  • Page 78: Display Configuration: Canvas Setup

    Display Configuration: Canvas Setup Display Configuration: Canvas Setup A Canvas in a Juggler system comprises all available pixels in a Juggler system as a whole. Within this, Outputs to the resolution of available devices are positioned. Depending on the firmware type for your Juggler, direct one-to-one feeds can be made to these Outputs, or to Windows as areas anywhere in the Canvas, even across output boundaries.
  • Page 79 Display Configuration: Canvas Setup Below the canvas, the Interaction Mode is shown: This mode switches the selection layer between the Canvas (none) , Outputs, and Windows. Pressing ‘m’ switches between the three types of canvas objects so they can be selected and moved independently.

  • Page 80: Canvas Output Setup

    Display Configuration: Canvas Setup Allow Canvas View layer changes Unchecked, the layering will be fixed. Relative MPCDI Path If using MPCDI data, enter the relative folder path where you choose to keep MPCDI data files. Canvas bounds :X and Y, width and height Specify the dimensions of a Canvas.* If using more than one Canvas, these are all inserted at 0,0 X,Y coordinates, so set the X and Y offsets to displace a second Canvas.
  • Page 81 Display Configuration: Canvas Setup Again, since it is selected it will have an orange bounding box. The Output is now visible as a branch in the Project panel, and by selecting an Output in the Project panel, you can configure it in the Properties panel. Add all your Outputs in the same way: M512-3 Juggler : User Guide ©...
  • Page 82 Display Configuration: Canvas Setup Note how the position and dimensions of the selected object is shown in the toolbar. Change the Interaction Mode to ‘Output’ by pressing the ‘m’ key while in the Canvas assembly · panel until it reads ‘Output’. The same toggle is available on the toolbar button or right-click menu as ‘Interaction Mode’.
  • Page 83 Display Configuration: Canvas Setup The Up/Down/Left/Right arrow keys move the object towards that boundary of the canvas, 1 px · at a time. Add Shift to move in 10 px increments. · Add Ctrl+Shift to move in 100 px increments. ·...

  • Page 84: Canvas Window Setup

    Display Configuration: Canvas Setup Edit the properties of an Output by selecting it in the Project panel to populate the Properties panel. Outputs and Windows are branches of the Canvas, which can be expanded or collapsed. Output Properties Name Name the output logically and clearly. Multiple outputs are by default numbered sequentially. Names can also be changed in the Project panel by double-clicking the name there.
  • Page 85 Display Configuration: Canvas Setup As with the Canvas Output, an unassigned asset adopts a default resolution. The Canvas Window has been added as a branch to the Canvas in the Project panel. Select it there and its properties become available in the Properties panel. Interaction Mode: Use the ‘m’...
  • Page 86 Display Configuration: Canvas Setup The other toolbar button is now active to move selected Windows around to common positions. The Window can also be toggled to fill the Canvas and return to its set size. Shortcuts are listed in the toolbar menu.

  • Page 87: Create And Recall Canvas Arrangements

    Display Configuration: Canvas Setup Create and Recall Canvas Arrangements How can you quickly rearrange your canvas setup? For many venues, there will be a requirement for a number of flat-screen scenarios for different times of days or events, or just to reset at the end of a session.
  • Page 88 Display Configuration: Canvas Setup Into this, all the windows can be added and given dimensions. Once released within the canvas bounds, windows can be moved off into the space outside the canvas bounds, where they will not appear on the actual display. Only those required for a particular arrangement are placed inside the canvas: 2: Create window arrangement Presets Once set up, the arrangement can be captured as a Preset.
  • Page 89 Display Configuration: Canvas Setup Select File > Presets > Save As > Canvases M512-3 Juggler : User Guide © 2021 7thSense...
  • Page 90 Display Configuration: Canvas Setup The default file location for Presets is set in Configuration > Preferences. Name the preset. Now rearrange the windows again as required for the next Preset: M512-3 Juggler : User Guide © 2021 7thSense...
  • Page 91 Display Configuration: Canvas Setup Save this as another Preset with a new name. Create further arrangements as required. M512-3 Juggler : User Guide © 2021 7thSense...
  • Page 92 Display Configuration: Canvas Setup 3: Recall Presets From this example, the only changes will be the window positions and/or sizes. Method 1: From File > Presets > Recall, select and apply the arrangement required. As the values for each window are inserted, they will be repositioned in the Canvas panel and the actual display. Method 2: Send an External Control command to recall the Preset.

  • Page 93: Display Setup Via Mpcdi

    Display Configuration: Canvas Setup DIsplay Setup via MPCDI The non-Windowing (Warp/Blend) version of Juggler firmware instead allows for the placement of MPCDI data to define media location, warp and blend for a projection system. In File Explorer, browse to the MPCDI file (*.mpcdi format) and drag it into the upper Canvas assembly panel.

  • Page 94: Nodes: Connecting Juggler Systems

    Nodes: Connecting Juggler Systems Nodes: Connecting Juggler Systems The Nodes assembly panel is where representations of Jugglers and other parts of the system can be connected: to each other, to outputs, to other devices, and to processes. Here you decide how the receive (Rx) ports of Jugglers –...
  • Page 95 Nodes: Connecting Juggler Systems Title bar Identifies the Juggler name and allows the Canvas to be selected for all video channels in the Juggler. GPIO These four indicators correspond to the GPIO HD-BNC ports on the back panel 1-4 left to right. Grey: not enabled (in Juggler properties) Red: enabled but no signal present Green: enabled and connected...
  • Page 96 Nodes: Connecting Juggler Systems Temperature For internal monitoring of the Juggler. Unit ID Last 2 digits of the Juggler module’s IP address, to provide an identifier within the Project Group. IP Address Full IP address of the Juggler module. Internal Comms Indicates the status of communication within the Juggler module.
  • Page 97 Nodes: Connecting Juggler Systems Video Processing Canvas Select: select a named Canvas within which this channel will be displayed. The list is populated from Canvases added and named in the Canvas assembly panel. This can be set from the title bar for all available video channels per Juggler. Window: select a Window of the selected Canvas, in which the channel media will be displayed (if required).
  • Page 98 Nodes: Connecting Juggler Systems ‘Show selected object links’, for example, will show links to, from and inside a selected Juggler only. The square pins in the Bus block (upper right of each Juggler node) are the bus connections. These pins will show green when valid media is available on the bus lane. Multiple selection Whilst properties cannot be displayed for more than one object, you may want to move or arrange multiple Jugglers.
  • Page 99 Nodes: Connecting Juggler Systems Show a miniature map of all nodes and the position of the current view. Make the position of a selected node the viewpoint for any node then selected in the Project panel. This toggle button is not enabled until one and only one node is selected. When the position of that node is pinned, any node then selected centres all nodes around that point.

  • Page 100: Input / Output Connector Properties

    Nodes: Connecting Juggler Systems Input / Output Connector Properties Each Juggler module is delivered with firmware capable of the hardware functionality purchased. The firmware determines how each module will be seen in Compere and can be programmed. The Compere software manages what functionality can be configured, per Juggler module. Ø...
  • Page 101 Nodes: Connecting Juggler Systems Example: DisplayPort Rx and Tx properties The combination of Name, Hardware Id, and Channel Identify the Connector within the Juggler. Use the Identify checkbox to see in in the media display. Name Type, Tx or Rx and number (1-4). Hardware Id The internal recognition identifier in the respective Juggler.
  • Page 102 Nodes: Connecting Juggler Systems DisplayPort: base 000 (so numbered 001, 002, 003, 004) SDI: base 100 (so numbered 101, 102, 103, 104) HDMI: base 200 (so numbered 201, 202, 203, 204) Genlock Mode (Tx only) Internal mode for genlock: the pin proving the genlock signal (see: GPIO Genlock Example Genlock Ratio (Tx only) This is ratio of input to output frame rate:...

  • Page 103: Bus Connections In A Juggler System

    Nodes: Connecting Juggler Systems Bus Connections in a Juggler System The Juggler bus can be configured in two ways: as a 4-lane ‘half’ bus via SFP modules, or a an 8-lane ‘full’ bus with MPO connectors (see: Connect a Juggler Data Bus ).
  • Page 104 Nodes: Connecting Juggler Systems Any Juggler can therefore place media onto the bus, from where any other(s) can stream it off as an input. The red/green Rx marker on the left of the Bus nodes indicate whether a bus input exists (green). ·...
  • Page 105 Nodes: Connecting Juggler Systems BusRx Selecting ‘BusRx’ here will simply pass on this Juggler’s received bus, so Juggler 1 BusRx:1:1 will connect internally to Juggler 1 BusTx:1:1 and be passed on to Juggler 2 BusRx:1:1 and so on, as in the diagram above. Video Channels The 4 video channels listed are the media channels of this Juggler.
  • Page 106 Nodes: Connecting Juggler Systems Bus Properties Bus properties can be shown by selecting the Bus from a Juggler in the Project panel, or by expanding the Bus section from all properties of selected Juggler in the Properties panel. These are the common properties for the bus as a whole: Name: If you wish, for clarity with your own naming convention, rename your bus pins clearly and consistently throughout.
  • Page 107 Nodes: Connecting Juggler Systems Name: BusRx 1:1 indicates bus 1, receiving lane 1. Signal Name NDI source name. Hardware Id The internal recognition identifier in the respective Juggler. Be sure to understand the correlation with the physical interface panel identification. Connectors in Compere project are identified by type and number: Bus: base 300 (so numbered 301, 302, 303, 304) Is Display Port MST Active...

  • Page 108: Connecting Inputs And Outputs

    Nodes: Connecting Juggler Systems Tx Bus Id The number of the Bus being transmitted on (normally there is only one but two are possible) Tx Lane Id The number of the Bus lane being used to transmit. Tx Src Video channel from this Juggler, added to this bus pin. The selector is populated the same as the selector in the Juggler node of the Nodes panel.
  • Page 109 Nodes: Connecting Juggler Systems In the Processing block, you decide where this is to go next. There are other processes you can add, but for now, just ensure you have the canvas you want to use. In the Video #2 Output block for this channel, ensure the Tx has the appropriate destination port selected.

  • Page 110: Edid Spoofing

    Nodes: Connecting Juggler Systems This checkbox is ‘push-to-show’, and will temporarily cause the output device to flash red and then green. Now assign the video channel to a Canvas Window in the Video Processing block. The selector list is populated by the addition of Windows in the Canvas assembly panel. Canvas windows can be positioned anywhere in the Canvas, so what you see on the output display will require this Window to be positioned somewhere over the selected Canvas Output for this video channel, as here: EDID Spoofing...

  • Page 111: 3D Passive To Active Conversion

    Nodes: Connecting Juggler Systems When an Input or Output is assigned to a Juggler video connector, it adopts the EDID of that connector. 3D Passive to Active Conversion To convert a 3D passive input to 3D active, drag the Passive to Active Node from the Resources panel onto the required Juggler: The resource is added to the Juggler in the Project tree, from where it can also be renamed or deleted.

  • Page 112: Intelligentsource

    Nodes: Connecting Juggler Systems The resource is added to the Juggler in the Project tree, from where it can also be renamed or deleted. Connect the appropriate processing input pin and the required video output pins. This node has the effect of directing interleaved frames to two independent 2D output channels. To use this 3D converter, a 3D sync input is required.
  • Page 113 Nodes: Connecting Juggler Systems The ‘IS’ icon will be grey until IntelligentSource is enabled. It is enabled, per required video channels for a Juggler, in the Properties panel for that channel: Frame Count and Frame Time will be incrementing when all is well. ·...

  • Page 114: Ports Used By Juggler And Compere

    Ports Used by Juggler and Compere Ports Used by Juggler and Compere Function Configurable Port Compere UDP Default, editable via comms.ini or in 9999 Preferences Compere TCP Default, editable via comms.ini or in 5555 Preferences 5553 (early versions of Compere) Multicast discovery UDP Fixed 5353...

  • Page 115: External Control

    External Control External Control Principle Every element of a Compere Project (the branching tree you see in the Project panel) has a unique identifier (UUID) and a common text name that you give to it. The same is true for every parameter that you can see, and may want to change, in the Properties panel for that element.
  • Page 116 External Control Commands and their parameters are case insensitive. Each parameter’s actual value is case sensitive. Individual commands are activated in text strings by line ending characters \n, or in xml, by opening and closing tags <command> </command> or, for empty tags, <command />.
  • Page 117 External Control group commands="GroupSet/Group/proj1/position/x=0.2; [...];GroupSet/Group/proj2/heading/roll=0.2" Scope of external control With complex multi-Juggler systems, External Control is the route to both systems management, and dynamic interaction with all the elements. Whether used directly or through show controllers, it removes the need to use Compere for complex daily interaction with devices, models, projectors, sources, processes and interconnections.
  • Page 118 External Control To use an action: actions type="[name]" enacts a specific action of this name Example Import an MPCDI file from a given location: actions type="import MPCDI" file="C:\[MyPath]\MPCDI\example.mpcdi" Real use case example: actions type="Import MPCDI" file="C:\Users\[UserName]\Downloads\MyFile01.mpcdi" Options Any of the commands below could be used to set the x position of a Canvas Window value to 800: M512-3 Juggler : User Guide ©...

  • Page 119: Wildcards

    External Control Using names <command cmd="set" path="/GroupSet/Group/Canvas 1/Window 1/canvasposition/x" value="800"/> Using class names (i.e. non-specific) The element path="juggler", for example, addresses all objects of type ‘juggler’. <command cmd="set" path= "/GroupSet/Group/juggler"/> Using a mixture of wildcards (*), names (specific) and class names (non-specific) <command cmd="set"...

  • Page 120: Message Formats

    External Control Command <command cmd="get" path="health"/> Reply <replies success="true" path="health" numberofreplies="3" commandDuration="123us"> <health value="~RxLane:1-LaneDown~RxLane:2-LaneDown~RxLane:3- LaneDown~RxLane:4-LaneDown~" fullpath="GroupSet/Group/JugglerName1/Bus:1/health"/> <health value="~RxLane:1-LaneDown~RxLane:2-LaneDown~RxLane:3- LaneDown~RxLane:4-LaneDown~" fullpath="GroupSet/Group/JugglerName2/Bus:1/health"/> <health value="~RxLane:1-LaneDown~RxLane:2-LaneDown~RxLane:3- LaneDown~RxLane:4-LaneDown~" fullpath="GroupSet/Group/JugglerName3/Bus:1/health"/> </replies> Message Formats Message formats: core and extended Messages may be sent in either plain text or XML format – see below for the plain text summary – and Compere will respond in the same format as the incoming message.
  • Page 121 External Control <command cmd="actions" type="Import MPCDI" file="C:\Users\[UserName]\Downloads\mpcdi-file- name.mpcdi"/> and in plain text: actions type="Import MPCDI" file="C:\Users\[UserName]\Downloads\mpcdi-file-name.mpcdi" Response format All valid messages are acknowledged immediately with ‘success=true/false’. The XML response is a well-formed XML document which may be parsed by any established third-party library. Note: the Compere version example below includes a date string and a build hash which can be used for build tracking/reporting.
  • Page 122 External Control Get info for a specific Juggler <command cmd="get" path="JugglerName" /> Get all versions from all Jugglers in a system <command cmd="get" path="fwversion" /> <command cmd="get" path="swversion" /> <command cmd="get" path="compereversion" /> Get versions for a specific Juggler Name <command cmd="get"...
  • Page 123 External Control path="externalipaddress" Example: MPCDI import <command cmd="actions" type="Import MPCDI" file="C:\\path\\to\\system.mpcdi" /> Plain text actions type="Import MPCDI" file="C:\\path\\to\\system.mpcdi" Further examples Get all temperatures for all Jugglers in a system <command cmd="get" path="temperaturePL" /> <command cmd="get" path="temperatureCPU" /> Get CPU temperature for a specific Juggler Name <command cmd="get"...

  • Page 124: System Status

    External Control System Status Contains status elements: Timestamp of Compere · Task manager · Current project · Default project · Comms mode (client/server/off) · Peer data · Command <command cmd="status" /> Reply <status success="true" time="Thu Jan 21 15:32:21 2021"> <taskSummary total="0"...

  • Page 125: Bus Status

    External Control <juggleruptime value="0d:01h:52m" fullpath="GroupSet/Group/JugglerName/juggleruptime"/> </replies> Bus Status Get bus status Command <command cmd="get" path="/GroupSet/GroupJugglerName/Bus:1/health"/> Reply <replies success="true" path="/GroupSet/Group/JugglerName/Bus:1/health" numberofreplies="1" commandDuration="123us"> <health value="~RxLane:1-LaneDown~RxLane:1-CtrlBad~RxLane:2- LaneDown~RxLane:3-LaneDown~RxLane:3-CtrlBad~RxLane:4- LaneDown~RxLane:4-CtrlBad~RxLane:5-LaneDown~RxLane:6- LaneDown~RxLane:7-LaneDown~RxLane:8-LaneDown~" fullpath="GroupSet/Group/JugglerName/Bus:1/health"/> </replies> Bus Reset Flash the bus Command <command cmd="set" path="/GroupSet/Group/JugglerName/Bus:1/reset" value="1"/> Reply <set success="true"/> Genlock Get genlock status Command...
  • Page 126 External Control Reply <replies success="true" path="/GroupSet/Group/JugglerName/VideoChannel:2/outputgenlocked" numberofreplies="1" commandDuration="123us"> <outputgenlocked value="0" fullpath="GroupSet/Group/JugglerName/VideoChannel:2/outputgenlocked"/> </replies> Get current genlock ratio and available options Command <command cmd="get" path="/GroupSet/Group/JugglerName/HdmiTx:3/genlockratio"/> Reply <replies success="true" path="/GroupSet/Group/JugglerName/HdmiTx:3/genlockratio" numberofreplies="1" commandDuration="234us"> <genlockratio typeName="MemberArray" value="1:1" enabled="1" fullpath="GroupSet/Group/JugglerName/HdmiTx:3/genlockratio"> <memberarrayitem UUID="04e120c5000000000400000000000178" value="1:1" enabled="1"/> <memberarrayitem UUID="04e120c5000000000400000000000179" value="1:2" enabled="1"/>...

  • Page 127: Hotplug Detect

    External Control <memberarrayitem UUID="04e120c5000000000400000000000168" value="Lock to Rx:3" enabled="1"/> <memberarrayitem UUID="04e120c5000000000400000000000169" value="Lock to Rx:4" enabled="1"/> <memberarrayitem UUID="04e120c5000000000400000000000170" value="Lock to Tx:1" enabled="1"/> <memberarrayitem UUID="04e120c5000000000400000000000171" value="Lock to Tx:2" enabled="1"/> <memberarrayitem UUID="04e120c5000000000400000000000172" value="Lock to Tx:3" enabled="1"/> <memberarrayitem UUID="04e120c5000000000400000000000173" value="Lock to Tx:4" enabled="1"/> <memberarrayitem UUID="04e120c5000000000400000000000174" value="Lock to GPIO:1"...

  • Page 128: Resolution

    External Control Reply <replies success="true" path="/GroupSet/Group/JugglerName/DpRx:2/edidlist" numberofreplies="1" commandDuration="567us"> <edidlist typeName="MemberArray" value="HD60-Internal" enabled="1" fullpath="GroupSet/Group/JugglerName/DpRx:2/edidlist"> <memberarrayitem UUID="04e120c5000000000400000000000081" value="HD60- Internal" enabled="1"/> <memberarrayitem UUID="04e120c5000000000400000000000082" value="2xHD120.bin" enabled="1"/> <memberarrayitem UUID="04e120c5000000000400000000000083" value="2xHD60.bin" enabled="1"/> <memberarrayitem UUID="04e120c5000000000400000000000084" value="4k30.bin" enabled="1"/> <memberarrayitem UUID="04e120c5000000000400000000000085" value="4K60.BIN" enabled="1"/> <memberarrayitem UUID="04e120c5000000000400000000000086" value="720p60.bin" enabled="1"/> <memberarrayitem UUID="04e120c5000000000400000000000087" value="HD120- 10.bin"...

  • Page 129: Mpcdi

    External Control fullpath="GroupSet/Group/JugglerName/DpRx:2/VideoTiming/activelines"/> </replies> Get all input info Command <command cmd="get" path="/GroupSet/Group/JugglerName/DpRx:2/VideoTiming"/> Reply <replies success="true" path="/GroupSet/Group/JugglerName/DpRx:2/VideoTiming" numberofreplies="1" commandDuration="789us"> <videotiming UUID="04e120c5000000000000000000000010" fullpath="GroupSet/Group/JugglerName/DpRx:2/VideoTiming" value=""> <name value="VideoTiming"/> <enabled value="1"/> <state value="0"/> <activepixels value="4096"/> <activelines value="2160"/> <totalpixels value="4256"/> <totallines value="2222"/> <hsyncwidth value="32"/> <vsyncwidth value="10"/> <hactivestart value="112"/>...

  • Page 130: Project Controls

    External Control <command cmd="status"/> Reply <status success="true"> <taskSummary total="7" failed="0" pending="1" complete="6" percentComplete="85.714286" MPCDI-Processing="85.714286%"/> <projectStatus ProjectPath="C:\Users\[UserName] \AppData\Local\compere\Projects\primary.prj" DefaultProject="C: \Users\[UserName]\AppData\Local\compere\Projects/myproject.prj"/> <networkInfo commsMode="server" peerData="64-4b-f0-12-75-fd "/> </status> Project Controls Note: Saving and Loading is to the server and the path must use the correct slashes for the server OS. Open a project Command <command...

  • Page 131: Presets And Clones

    External Control Presets and Clones Use a Preset or Clone resource (Recalling a Preset imports values to matching UUIDs. Loading a Clone imports saved copies of objects with new UUIDs.) Command (Presets) <command cmd="recallpreset" file="C:\[Compere Root Path]\Presets\[file].pre"/> or (implied file location) <command cmd="recallpreset"...

  • Page 132: Logs And Diagnostics

    Logs and Diagnostics Logs and Diagnostics Compere generates a log file (CompereLog.txt) which can be very useful for system debugging and troubleshooting. On a Windows machine this can be found by default in: C:\Users\[USERNAME] \AppData\Local\Compere\logs. Ø Default file locations can be edited. See File Locations in Preferences Panel These files inflate, so when they get to a certain size they are archived with a sequential file suffix: CompereLog_nn.txt.
  • Page 133 Logs and Diagnostics Gather Project Data Lists logs per Juggler in the Project Group. Click ‘Open’ to create a zip file in this location of all logs and the local Compere Preference.pref file. Reporting diagnostic information Send the following information to us to help us understand what you are seeing: Save server Project File locally (XML) ·...

  • Page 134: Command Line Arguments

    Command Line Arguments Command Line Arguments Occasionally it can be useful to run Compere with a command line switch, to force it to run in a particular way. For example, different Windows shortcuts can be created to do this, by adding the switches into the shortcut target: C:\7thSense\compere\compere.exe networkserver...

  • Page 135: Troubleshooting A Juggler System

    Troubleshooting a Juggler System Troubleshooting a Juggler System Bus faults Faults in the bus will be indicated by the Rx bus pins in a Juggler in the Nodes panel being red when they should be green (not set to Off, but cabled). The majority of faults in the bus system will be caused by connector contamination.

  • Page 136: Juggler Physical Specifications

    Juggler Physical Specifications Juggler Physical Specifications Environmental Characteristics Operating Non-operating Temperature +15 to +30 °C -10 to +50 °C Humidity (non-condensing) 10 to 90% 5 to 95% Altitude Specification Rating/Description Notes Width including mounting ears: Rackmount Dimensions (H × W × D) (1U) 44.3 ×...
  • Page 137 Juggler Physical Specifications Side panel exhaust vents, mm [in] Rear panel exhaust vents, mm [in] M512-3 Juggler : User Guide © 2021 7thSense...

  • Page 138: Rack Mounting Jugglers

    Rack Mounting Jugglers Rack Mounting Jugglers Juggler units must be installed in a rack with load-bearing support along the sides, under the rear, or on a shelf. The rear and side exhaust vents must be kept clear. The front panel should be secured using an M6 rack mount bolt in each of the top and bottom mounting holes on each side of the unit’s front panel.

  • Page 139: Juggler Care And Maintenance

    Juggler Care and Maintenance Juggler Care and Maintenance Environment Juggler is intended for use in a commercial (not domestic) environment and should be operated in a clean, dust free area (e.g. a server room). It is intended for operation in benign environments (not subject to corrosive or explosive atmospheres, moisture or flammable gases).
  • Page 140 Juggler Care and Maintenance Cleaning External casing and the front panel should be carefully wiped with a soft cloth and antistatic solution. Air filter A user-serviceable air filter is located behind each of two vents on the unit’s front panel. It is important to remove and clean or replace the filters periodically to avoid overheating.
  • Page 141 Juggler Care and Maintenance Internal maintenance Other than the mains fuses, Juggler contains no user-serviceable parts. Warning: Do not operate the Juggler with any covers removed as the air flow through the unit will be compromised and may lead to overheating. The lid of the Juggler forms an integral part of the cooling circuit.

  • Page 142: Warranty, Support And Service

    Warranty, Support and Service Warranty, Support and Service Standard warranty is 24 months, return-to-distributor. Please contact 7thSense Design if you require an extended warranty. Please ask for instructions and request authorisation before returning a Juggler unit to your distributor. Server Internal Maintenance Internal maintenance must only be undertaken by suitable qualified service personnel.

  • Page 143: Regulatory Compliance

    Regulatory Compliance Regulatory Compliance Juggler Pixel Processor complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. Note: The equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC Rules.

  • Page 144: Document Information

    Document Information Document Information Date Document Software Revision Details Author/Editor edition version December 2020 Compere 1.0-1 New release Andie Davidson February 2021 Compere 1.0-2 Compere version updates Andie Davidson April 2021 Compere 1.0-2 Updates to clones and presets; Andie Davidson external control The Adopted Trademarks HDMI, HDMI High-Definition Multimedia Interface, and the HDMI Logo are trademarks or registered trademarks of HDMI Licensing Administrator, Inc.

  • Page 145: Index

    Index projects projects, project files recall preset render settings (layout panels) Compere 3D active to passive node save layout 3D passive to active node server-client roles add, select, edit, delete, remove objects shortcuts canvas status bar canvas arrangement system config table canvas assembly panel task progress canvas object...
  • Page 146 Index Juggler compliance and conformity connections in Compere connections physical technical support 132, 142 cooling data bus electrical fuses fibre-optic patch cables warranty front panel controls front panel display genlock genlocking GPIO ports input/output input/output connections interconnections interface options NDI feed network connections operating environment optical connectors, cleaning...
  • Page 148 E: info@7thsense.one W: 7thsense.one 7thSense Design Ltd 7thSense LLC, Michigan 7thSense LLC, Orlando 2 The Courtyard, Shoreham Road 332 E Lincoln Ave 4207 Vineland Rd Upper Beeding Suite 100 Suite M1 Steyning Royal Oak, MI 48067 Orlando, FL 32811 West Sussex BN44 3TN T: +44 (0) 1903 812299 T: +1 248 599 2717...

Table of Contents