Screenforce is the ultimate way to control your virtual production stage! Remotely run software, change Nvidia sync, execute python scripts, chain and more, all with an easy to use interface and secure execution.

Chain actions together to create multi-stage functionality, build groups of nodes for simple execution, and control everything remotely with OSC.

Overview

Screenforce is a controller-and-receiver system for operating Windows render nodes on a virtual production stage or broadcast environment. It lets an operator discover machines, arrange them into wall or stage groups, and launch repeatable actions across one node or a group of nodes.

What Screenforce does

• Discovers Windows render nodes on the production network.
• Organizes nodes into nested groups, such as Stage A > Main Wall and Stage A > Ceiling.
• Allows actions to be performed the controller, a single receiver, or a group:
  • Run/Stop software programs
  • Run/Stop Python scripts
  • Change Nvidia Sync status (House Sync/Framelock/Off)
  • Kill programs matching a specific name
• Allows multiple actions can be chained together with an optional delay
• Accepts OSC triggers from a show-control or automation system.
• Displays output from software and allows console commands to be run on remote notes

Screenforce is not a render-status dashboard, frame-sync validator, media server, file-deployment tool, remote desktop system, or safety interlock. It does not currently report GPU load, render frame rate, Unreal Engine cluster state, thermals, genlock lock status, or application health. Verify those through the appropriate production tools.

System layout

Install the receiver on every machine that Screenforce will control, and install the controller on the operator workstation.

The installer will give you the option to automatically start each on boot as admin. You can instead opt to start Screenforce manually, but Nvidia sync actions won’t work unless Screenforce has admin privileges.

The controller also contains a Local node. Actions assigned to it run on the controller workstation and do not pass through a receiver.S

Network configuration