Back To Page References
In Motive, the Data Streaming pane can be accessed under the View tab or by clicking icon on the main toolbar.
For explanations on the streaming workflow, read through the Data Streaming page.
The OptiTrack Streaming Engine allows you to stream tracking data via Motive's free streaming plugins or any custom built NatNet interfaces. To begin streaming, select "Broadcast Frame Data." Select which types of data (e.g. markers, rigid bodies, or skeletons) will be streamed, noting that some third party applications will only accept one type of data. Before you begin streaming, ensure that the network type and interface are consistent with the network you will be streaming over and the settings in the client application.
OptiTrack Streaming Engine: Streams marker, rigid body, or skeletal data via OptiTrack’s NatNet streaming engine.
Broadcast Frame Data: Default: Unchecked. Allows broadcasting the frame data. This box must be checked in order to start the streaming.
Local Interface: Sets the network address which the captured data is streamed to. When set to local loopback (127.0.0.1) address, the data is streamed within the computer. You can also choose the IP address specific networks.
Stream Subject Prefix: When set to true, each marker label includes a subject prefix, which is the name of associated asset.
Stream Visual3D Compatible: Enables streaming to Visual3D. Normal streaming is not compatible with Visual3D, and this feature must be enabled in order to stream tracking data to Visual3D.
Stream Labeled Markers: Enables/disables, streaming of labeled Marker data in that are either point cloud solved or model filled.
Stream Unlabeled Markers: Enables/disables streaming of all of the unlabeled Marker data in the frame.
Stream Marker Set Markers: Enables/disables streaming of named collections of identified markers and their positions (X, Y, Z). In other words, this includes markers that are associated with any of the assets (MarkerSet, Rigid Body, Skeleton). The streamed list also contains a special marker set named all which is a list of labeled markers in all of the assets in aTake.
Stream Rigid Bodies: Controls the streaming of rigid body name, position, and orientation data over NatNet.
Stream Skeletons: Sets whether skeletons are streamed, if present.
Local Rigid Bodies: When this is set to true, the streamed tracking data (position and rotation) of each skeletal bone will be relative to its parent bones. When set to false, the tracking data will be represented according to the global coordinate system.
Skeleton as Rigid Body: Enables the streaming of skeleton segments as a series of rigid bodies.
Scale: Sets the scaling for streamed skeletal data.
Bone Naming Convention: Determines the bone naming convention for the streamed data among Motive, FBX, and BVH. It must match with the convention used in the streaming destination.
Up Axis: Selects the upward axis in the streamed data. (Default: Y Axis).
Remote Trigger: Allows using the remote trigger for the streaming. (Default: False).
Type: Selects the mode of broadcast for NatNet. Valid options are: Multicast, Unicast. (Default: Multicast).
Command Port: Specifies the port to be used for negotiating the connection between the NatNet server and client. (Default: 1510).
Data Port: Specifies the port to be used for streaming data from the NatNet server to the client(s). (Default: 1511).
Multicast interface: Specifies the multicast broadcast address. (Default: 188.8.131.52).
Note: When streaming to clients based on NatNet 2.0 or below, the default multicast address should be changed to 184.108.40.206 and the data port should be changed to 1001.
For information on streaming data via the VRPN Streaming Engine, please visit the VRPN knowledge base. Note that only 6 DOF rigid body data can be streamed via VRPN.
VRPN Streaming Engine: Streams rigid body data via the VRPN protocol.
VRPN Broadcast Port: Specifies the broadcast port for VRPN streaming. (Default: 3883).
For information on streaming data via the Trackd Streaming Engine, please consult the Trackd documentation or contact Mechdyne. Note that only 6 DOF rigid body data can be streamed via Trackd.
TrackD Streaming Engine: Streams rigid body data via the Trackd protocol.
Back to Top