PRG Stage Command Driver
このコンテンツはまだ日本語訳がありません。
The PRG Stage Command Driver enables Disguise to receive real-time motion-control data from the PRG Stage Command System (SCS), PRG’s flagship automation platform used to control winches, hoists, tracks, revolves, lifts, and other multi-axis scenic elements.
Unlike the simpler PRG Screen Automation protocol, the Stage Command System provides structured, high-resolution positional data and operational status for multiple axes of movement.
This driver should be used whenever your production relies on PRG automation hardware controlled through SCS and needs Disguise content to synchronise with the actual physical motion on stage.
Typical use cases include:
- Flying screens or LED walls operated by PRG SCS
- Automated scenic pieces (portals, set pieces, moving architecture)
- Deck automation such as tracks, elevators, and revolves
- Multi-axis movement requiring accurate positional feedback
- Synchronising media playback with live stage motion
- Reacting to PRG machinery state changes as the machinery reaches specific positions or states
The PRG Stage Command Driver listens for structured SCS network messages and exposes them in Disguise as automation axes that can drive tracking, camera calibration offsets, or timeline logic.
Driver Properties
Section titled “Driver Properties”
The UDP port that the PRG SCS system outputs its automation data to.
This must match the port configured by the PRG automation team.
IP Filter
Section titled “IP Filter”The specific SCS controller IP address that data will be accepted from (optional).
Useful in large network environments or multi-controller setups.
Multicast Address
Section titled “Multicast Address”The multicast group the SCS system is publishing positional data to (optional).
Required only if your PRG SCS configuration uses multicast distribution.
Additional Notes
Section titled “Additional Notes”- SCS may expose multiple axes, each corresponding to a physical device or motion group.
- Axes can be mapped in Disguise to drive screen positions or content tracking.
- For simple PRG UDP feeds not originating from SCS, use the standard PRG Driver, not this one.
Developer Documentation