Skip to content

Stype Driver

The Stype Driver allows Disguise to receive real-time camera-tracking data from Stype systems, including Stype RedSpy, StypeLand and other encoders using the Stype protocol. Stype provides precise camera position, rotation, lens metadata and timing information for virtual production, augmented reality and camera-tracked workflows.

We recommend using the default driver settings unless your Stype system or network setup requires custom configuration.

Use the Stype Driver when your workflow requires:

  • Real-time camera tracking for xR, AR or virtual production
  • Accurate lens metadata including zoom, focus and distortion parameters
  • Synchronising CG environments with live-action camera movement
  • Virtual set extensions that follow the tracked camera
  • Motion capture or encoded crane tracking (e.g., Stype’s encoded heads and jibs)
  • Latency and timing analysis using the packet timing graph option

Stype data is commonly used in LED volumes, green-screen stages, broadcast AR, and any workflow where a tracked camera must drive rendered content inside Disguise.


When enabled, Disguise logs the timing of all incoming Stype packets and visualises them as a graph.

This is useful for diagnosing network jitter, dropped packets or inconsistent tracking frequency.

Port

The UDP port on which the driver receives data. Set this to match the port configured on the sending device or controller.

IP filter (optional)

Restricts incoming data to a specific source IP address. Useful when several sources are present on the network, or to isolate a single sender. Leave blank to accept data from any IP.

Multicast address (optional)

The multicast group address used by your system. Only required when the sender is configured for multicast — enter the exact multicast address used by the emitter. Leave empty for unicast or broadcast configurations.


Developer Documentation