The Orchestrator is the application that enables communication and coordination between all PLAY on-site applications, to allow controlled playback from a single point of access.
Key responsibilities
-
Receives and caches all information from the PV4 Portal instance for dissemination over the local network.
-
Receives and/or processes data from third-party providers (stats APIs, telemetry systems).
-
Translates incoming control information from PV4 Controllers and external controllers for dissemination to Renderer Applications over the network.
-
Logs cue playback and errors.
-
Stores configurations and authentication for your show.
Key information
-
The Orchestrator can be run on any Windows machine on your local network being used for PV4 PLAY. Only a single machine on the network should run the Orchestrator application, to prevent information conflicts.
-
The Orchestrator must have an internet connection to receive new information from the PV4 Portal instance. Show data is cached locally for offline operation, or in the event of internet dropouts or complete loss.
-
The Orchestrator is the main point of communication for all on-site applications. It must be running, configured, and have a show loaded for any communication to occur between on-site applications.
-
The Orchestrator is the application that all external applications must send control messages to. This includes Stream Decks, QLab, or any application that transmits OSC.
User interface
The Orchestrator UI is also the first place to look when troubleshooting the wider system — see Orchestrator User Interface for a full walkthrough. At a glance, it shows:
-
Show Load Status
-
Discovered modules on your local network
-
Connectivity Errors
-
Cue playback info
-
Received control commands
Configuration
See Orchestrator Configuration for the full configuration reference.