Skip to content

Mo-Sys F4 Driver

The Mo-Sys F4 Driver is used to receive camera tracking data from Mo-Sys F4 systems.

This driver integrates directly with the Mo-Sys tracking workflow to provide real-time positional and rotational camera information for use in Disguise’s virtual production, xR, and AR environments.

Most installations work reliably using the default settings. Adjust the driver properties only when working with multi-camera setups or when your Mo-Sys system requires specific configuration.

Use the Mo-Sys F4 Driver when receiving live camera tracking data from Mo-Sys F4 systems for virtual production, xR, and broadcast environments. The driver provides a direct link between the physical camera and Disguise, ensuring accurate alignment between real-world camera movement and virtual scene elements.

This driver is especially useful when:

  • Integrating Mo-Sys F4 camera tracking for AR graphics, virtual studios, or xR workflows.
  • Synchronising real camera movement with virtual content, environments, or set extensions.
  • Working with multiple tracked cameras, each requiring unique identifiers.
  • Calibrating or validating Mo-Sys positional and rotational data within Disguise.
  • Ensuring lens and camera motion is correctly interpreted for real-time rendering.
  • Monitoring tracking performance during live production or rehearsal.

The Mo-Sys F4 Driver allows Disguise to interpret incoming tracking data with minimal configuration, making it suitable for both high-end broadcast installations and flexible real-time production setups.


This driver listens on UDP port 8051 by default.

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.

Logs the timing of incoming packets to a graph in the monitoring manager. This is useful for diagnosing latency or dropped packets.


Developer Documentation