Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
In Motive, the Application Settings can be accessed under the View tab or by clicking icon on the main toolbar. Default Application Settings can be recovered by Reset Application Settings under the Edit Tools tab from the main Toolbar.
Live-Pipeline settings contain camera filter settings and solver settings for obtaining 3D data in Motive. Please note that these settings are optimized by default and should provide high-quality tracking for most applications. The settings that might need to be adjusted based on the application are visible by default (i.e. not advanced).
The most commonly changed settings are...
Coarse/Fine IK Iterations - This helps Skeletons converge to a good pose quickly when Skeletons start in a difficult to track pose.
Minimum Rays to Start/Continue - This helps reduce false markers from semi-reflective objects when there is a lot of camera overlap. It also allows you to not track when seen by only one camera (Minimum Rays to Continue = 2).
Boot Skeleton Label Percentage - A lower value will allow Skeletons to boot more quickly when entering the volume. A higher value will prevent untracked Skeletons from attempting to track using other markers in the volume.
Solver settings for recorded captures:
Please note that these settings are applied only to the Live 3D data. For captures that are already recorded, you can optimize them from the properties of the corresponding TAK file.
The solver settings control how each marker trajectory gets reconstructed into the 3D space and how Rigid Bodies and Skeletons track. The solver is designed to work for most applications without needing to modify any settings. However, in some instances changing some settings will lead to better tracking results. The settings that may need to be changed are visible by default. There are also a large number of advanced settings that we don’t recommend changing, but the tooltips are available if needed. The settings that users may need to change are listed below with descriptions.
These are general tracking settings for the solver not related to creating 3D markers or booting assets. Do not change these settings in Live mode as incorrect settings can negatively affect the tracking, this is mostly useful when optimizing 3D data for recorded captures with actors in difficult positions to track.
What it does: This property sets the number of Coarse IK iterations, which are fast but not accurate inverse kinematic solve to place the Skeleton on the associated markers.
When to change: Do not change this property in Live mode. In recorded captures, this property may need to be changed, under the TAK properties, if the recording(s) starts with actors who are not in standing-up positions. Sometimes in these recordings, the Skeletons may not solve on the first couple frames, and in these cases, increasing this setting will allow the Skeleton to converge on the first frame.
What it does: This property sets the number of Fine IK iterations, which are slow but accurate inverse kinematic solve to place the final pose of the Skeleton on the associated markers. Increasing this setting may result in higher CPU usage.
When to change: Do not change this property in Live mode. In recorded captures, this property may need to be changed, under the TAK properties, if the recording(s) starts with actors who are not in standing-up positions or the ones that are difficult to solve. Sometimes in these recordings, the Skeletons may not solve on the first couple frames, and in these cases, increasing this setting will allow the Skeleton to converge on the first frame.
The Trajectorizer settings control how the 2D marker data is converted into 3D points in the calibrated volume. The trajectorizer performs reconstruction of 2D data into 3D data, and these settings control how markers are created in the 3D scene over time.
What it does: This setting controls the maximum distance between a marker trajectory and its predicted position.
When to change: This setting may need to be increased when tracking extra fast assets. The default setting should track most applications. Attempt to track with default settings first, and if there are any gaps in the marker trajectories, you can incrementally increase the distance until stable tracking is achieved.
What it does: This setting controls the maximum distance between a ray and the marker origin.
What it does: This sets the minimum number of tracked rays that need to converge on one location to create a new marker in 3D. This is also the minimum number of calibrated cameras that see the same target marker within the 3D threshold value for them to initially get trajectorized into a 3D point.
When to change: For large volumes with high camera counts, increasing this value may provide more accurate and robust tracking. The default value of 3 works well with most medium and small-sized volumes. For volumes that only have two cameras, the trajectorizer will use a value of 2 even when it's not explicitly set.
What it does: This sets the minimum number of rays that need to converge on one location in order to continue tracking a marker that already initialized near that location. A value of 1 will use asset definitions to continue tracking markers even when a 3D marker could not have been created from the camera data without the additional asset information.
When to change: This is set to 1 by default. It means that Motive will continue the 3D data trajectory as long as at least one ray is obtained and the asset definition matches. When single ray tracking is not desired or for volumes with a large number of cameras, change this value to 2 to utilize camera overlaps in the volume.
What it does: This setting is used for tracking active markers only, and it sets the number of frames of motion capture data used to uniquely identify the ID value of an active marker.
When to change: When using a large number of active tags or active pucks, this setting may need to be increased. It's recommended to use the active batch programmer when configuring multiple active components, and when each batch of active devices has been programmed, the programmer will provide a minimum active pattern depth value that should be used in Motive.
What it does: The total number of rays that must contribute to an active marker before it is considered active and given an ID value.
When to change: Change this setting to increase the confidence in the accuracy of active marker ID values (not changed very often).
What it does: The number of frames of data that the solver will attempt to fill if a marker goes missing for some reason. This value must be at least 1 if you are using active markers.
When to change: If you would like more or fewer frames to be filled when there are small gaps.
The Booter settings control when the assets start tracking, or boot, on the trajectorized 3D markers in the scene. In other words, these settings determine when Rigid Bodies and/or Skeletons track on a set of markers.
What it does: This controls the maximum distance between a pair of Marker Constraints to be considered as an edge in the label graph.
When to change: The default settings should work for most applications. This value may need to be increased to track large assets with markers that are far apart.
What it does: This sets the percentage of Skeleton markers that need to be trajectorized in order to track the corresponding Skeleton(s). If needed, this setting can also be configured per each asset from the corresponding asset properties using the Properties pane.
When to change: The default settings should work for most applications. Set this value to about 75% to help keep Skeletons from booting on other markers in the volume if there are similar Skeleton definitions or lots of loose markers in the scene. If you would like Skeletons to boot faster when entering the volume, then you can set this value lower.
Controls the deceleration of the asset joint angles in the absence of other evidence. For example, a setting of 60% will reduce the velocity by 99% in 8 frames; whereas 80% will take 21 frames to do the same velocity reduction.
The residual is the distance between a Marker Constraint and its assigned trajectory. If the residual exceeds this threshold, then that assignment will be broken. A larger value helps catch rapid acceleration of limbs, for example.
Ignores reconstructed 3D points outside of the reconstruction bounds.
This will be the general shape of the reconstruction bounds. Can choose from the following:
Cuboid
Cylinder
Spherical
Ellipsoid
The rest of the settings found under this tab can be modified in relation to center, width, radius, and height.
Two marker trajectories discovered within this distance are merged into a single trajectory.
A marker trajectory is predicted on a new frame and then projected in all the cameras. to be assigned to a marker detection in a particular camera, the distance (in pixels) must not exceed this threshold.
The maximum number of pixels between a camera detection and the projection of its marker.
The new marker trajectory is generated at the intersection of two rays through detections in different cameras. Each detection must be the only candidate within this many pixels of the projection of the other ray.
Marker trajectories are predicted on the next frame to have moved with this percentage of their velocity on the previous frame.
When a Skeleton marker trajectory is not seen, its predicted position reverts towards its assigned Marker Constraints by this percentage.
When a Rigid Body marker trajectory is not seen, its predicted position reverts towards its assigned Marker Constraints by this percentage.
The penalty for leaving Marker Constraints unassigned (per label graph edge).
The maximum average distance between the marker trajectory and the Marker Constraints before the asset is rebooted.
This value controls how willing an asset is to boot onto markers. A higher value will make assets boot faster when entering the volume. A lower value will stop assets from booting onto other markers when they leave the volume.
This is a less accurate but fast IK solve meant to get the skeleton roughly near to the final pose while booting.
This is a more accurate but slow IK solve meant to get the skeleton to the final pose while booting. (High values will slow down complex takes.)
The maximum number of assets to boot per frame.
This section of the application settings is used for configuring the 2D filter properties for all of the cameras.
The minimum pixel size of a 2D object, a collection of pixels grouped together, for it to be included in the Point Cloud reconstruction. All pixels must first meet the brightness threshold defined in the Cameras pane in order to be grouped as a 2D object. This can be used to filter out small reflections that are flickering in the view. The default value for the minimum pixel size is 4, which means that there must be 4 or more pixels in a group for a ray to be generated.
This setting sets the threshold of the circularity filter. Valid range is between 0 and 1; with 1 being a perfectly round reflection and 0 being flat. Using this 2D object filter, the software can identify marker reflections using the shape, specifically the roundness, of the group of thresholded pixels. Higher circularity setting will filter out all other reflections that are not circular. It is recommended to optimize this setting so that extraneous reflections are efficiently filtered out while not filtering out the marker reflections.
When using lower resolution cameras to capture smaller markers at a long distance, the marker reflection may appear to be more pixelated and non-circular. In this case, you may need to lower the circularity filter value for the reflection to be considered as a 2D object from the camera view. Also, this setting may need to be lowered when tracking non-spherical markers in order to avoid filtering the reflections.
Changes the padding around masks by pixels.
Delay this group from sync pulse by this amount.
Controls how the synchronizer operates. Options include:
Force Timely Delivery
Favor Timely Delivery
Force Complete Delivery
Choose the filter type. Options include:
Size and Roundness
None
Minimum Pixel Threshold
The minimum allowable size of the 2D object (pixels over threshold).
The maximum allowable size of the 2D object (pixels over threshold).
The size of the guard region beyond the object margin for neighbor detection.
The pixel intensity of the grayscale floor (pixel intensity).
The minimum space (in pixels) between objects before they begin to overlap.
The number of pixels a 2D object is allowed to lean.
The maximum allowable aspect tolerance to process a 2D object (width:height).
The allowable aspect tolerance for very small objects.
The rate at which the aspect tolerance relaxes as object size increases.
The Application Settings panel can be opened under the View tab or by clicking icon on the main toolbar in Motive. Most of the settings that are related to the overall software and the system can be accessed and configured in this panel. This includes camera system setting, data pipeline settings, streaming settings, and hotkeys and shortcuts.
Changes to the Application Settings can be resetted by Reset Settings under the Edit Tools tab from the main Toolbar.
Advanced Settings
The Application Settings contains advanced settings that are hidden by default. Access these settings by going to the menu on the top-right corner of the pane and clicking Show Advanced and all of the settings, including the advanced settings, will be listed under the pane.
The list of advanced settings can also be customized to show only the settings that are needed specifically for your capture application. To do so, go the pane menu and click Edit Advanced, and uncheck the settings that you wish to be listed in the pane by default. One all desired settings are unchecked, click Done Editing to apply the customized configurations.
The Assets tab in the application settings panel is where you can configure the creation properties for Rigid Body and Skeleton assets. In other words, all of the settings configured in this tab will be assigned to the Rigid Body and Skeleton that are newly created in Motive.
A list of the default Rigid Body creation properties is listed under the Rigid Bodies tab. These properties are applied to only Rigid Bodies that are newly created after the properties have been modified. For descriptions of the Rigid Body properties, please read through the Properties: Rigid Body page.
Note that this is the default creation properties. Asset specific Rigid Body properties are modified directly from the Properties pane.
You can change the naming convention of Rigid Bodies when they are first created. For instance, if it is set to RigidBody, the first Rigid Body will be named RigidBody when first created. Any subsequent Rigid Bodies will be named RigidBody 001, RigidBody 002, and so on.
User definable ID. When streaming tracking data, this ID can be used as a reference to specific Rigid Body assets.
The minimum number of markers that must be labeled in order for the respective asset to be booted.
The minimum number of markers that must be labeled in order for the respective asset to be tracked.
Applies double exponential smoothing to translation and rotation. Disabled at 0.
Compensate for system latency by predicting movement into the future.
For this feature to work best, smoothing needs to be applied as well.
Toggle 'On' to enable. Displays asset's name over the corresponding skeleton in the 3D viewport.
Select the default color a Rigid Body will have upon creation. Select 'Rainbow' to cycle through a different color each time a new Rigid Body is created.
When enabled this shows a visual trail behind a Rigid Body's pivot point. You can change the History Length, which will determine how long the trail persists before retracting.
Shows a Rigid Body's visual overlay. This is by default Enabled. If disabled, the Rigid Body will only appear as individual markers with the Rigid Body's color and pivot marker.
When enabled for Rigid Bodies, this will display the Rigid Body's pivot point.
Shows the transparent sphere that represents where an asset first searches for markers, i.e. the Marker Constraints.
When enabled and a valid geometric model is loaded, the model will draw instead of the Rigid Body.
Allows the asset to deform more or less to accommodate markers that don't fix the model. High values will allow assets to fit onto markers that don't match the model as well.
A list of the default Skeleton display properties for newly created Skeletons is listed under the Skeletons tab. These properties are applied to only Skeleton assets that are newly created after the properties have been modified. For descriptions of the Skeleton properties, please read through the Properties: Skeleton page.
Note that this is the default creation properties. Asset-specific Skeleton properties are modified directly from the Properties pane.
Creates the Skeleton with arms straight even when arm markers are not straight.
Creates the Skeleton with straight knee joints even when leg markers are not straight.
Creates the Skeleton with feet planted on the ground level.
Creates the Skeleton with heads upright irrespective of head marker locations.
Force the solver so that the height of the created Skeleton aligns with the top head marker.
Height offset applied to hands to account for markers placed above the write and knuckle joints.
Same as the Rigid Body visuals above:
Label
Creation Color
Bones
Marker Constraints
Changes the color of the skeleton visual to red when there are no markers contributing to a joint.
Display Coordinate axes of each joint.
Displays the lines between labeled skeleton markers and corresponding expected marker locations.
Displays lines between skeleton markers and their joint locations.
In Motive, the Application Settings can be accessed under the View tab or by clicking icon on the main toolbar. Default Application Settings can be recovered by Reset Application Settings under the Edit Tools tab from the main Toolbar.
2D tab under the view settings lists out display settings for the Camera View in Motive.
Sets the background color of the Camera View.
Enables markers selected from the 3D Perspective View to be also highlighted with yellow crosshairs in the 2D camera view, based on calculated position. Crosshairs that are not directly over the marker tend to indicate occlusion or poor camera calibration.
When enabled, Camera View shows which markers have been filtered out by the camera's circularity and size filter. This is enabled by default and is useful for inspecting why certain cameras are not tracking a specific markers in the view.
3D tab under the view settings lists out display settings for the Perspective View in Motive.
Sets the background color of the Perspective View.
Turns a gradient “fog” effect on in the Perspective View.
Selects the color of the ground plane grid in the Perspective View.
Selects the size of the ground plane grid in the Perspective View. Specifically, it sets the number of grids along the positive and negative direction in both the X and Z axis. Each grid represents 20cm x 20cm in size within a calibrated volume.
When enabled, Motive will display the floor plane in the Perspective View. This is disabled by default to only show the floor grid.
Sets the color of selections in the 3D view port.
Displays the coordinate axis in the 3D view port.
Determines where timecode gets displayed in Motive. Timecode can be displayed either on the Perspective View or the Control Deck or hidden entirely. Timecode will be available only when the timecode signal is inputted through the eSync.
Show or hide marker count report located at the bottom-right corner of the Perspective View.
Overlays the OptiTrack logo over top of the Perspective View.
Overlays refresh rate of the display on the Perspective View.
Determines whether marker sizes in the 3D Perspective View are represented by the calculated size or overwritten with a set diameter.
When the Marker Size setting above is set to Custom, the diameter of the 3D markers will all be fixed to the inputted diameter.
Sets the color for passive markers in the 3D viewport. Retro-reflective markers or continuously illuminating IR LEDs will be recognized as passive markers in Motive.
Sets the color for active markers in the 3D viewport.
Sets the color for measurement markers that are sampled using the Measurement Probe.
When this is set to true. 3D positions and estimated diameter of selected markers will be displayed on the 3D viewport.
Displays a history trail of marker positions over time.
When both the marker history and this setting is enabled, marker history trail will be shown for only selected markers in the viewport.
Number of past frames for showing the marker history.
Sets the color of tracking cameras in the 3D Perspective View. Cameras that are set to Object mode or Precision mode will be considered as tracking cameras in Motive.
Sets the color of reference cameras in the 3D Perspective View. Cameras that are capturing reference MJPEG grayscale videos or color videos, for Prime Colors, will be considered as reference cameras.
Sets the color for Tracked Rays in the 3D Perspective View.
Sets the color for unlabeled rays in the 3D Perspective View.
Sets the color for untracked rays in the 3D Perspective View.
Sets the color used for visualizing the capture volume.
Minimum number of cameras required for their FOV to overlap when visualizing the capture volume.
Sets the color for labeled markers. Markers that are labeled using either Rigid Body or Skeleton solve will be colored according to their asset properties.
Shows rays stemming from camera to markers that have not been labeled.
Displays all tracked rays.
Colors used for plot guidelines in the Graph View pane.
Background color used for the plots.
When enabled, y-axis of each plot will autoscale to fit all the data in the view. It will also zoom automatically for best visualization. For fixed y-plot ranges, this setting can be disabled. See Graph View pane for more information.
Preferred graph layout used for Live mode.
Preferred graph layout used for Edit mode.
The scope of domain range, in frames, used for plotting graphs.
In Motive, the Application Settings can be accessed under the View tab or by clicking icon on the main toolbar. Default Application Settings can be recovered by Reset Application Settings under the Edit Tools tab from the main Toolbar.
If you have an audio input device, you can record synchronized audio along with motion capture data in Motive. Recorded audio files can be played back from a captured Take or be exported into a WAV audio files. This page details how to record and playback audio in Motive. Before using an audio input device (microphone) in Motive, first make sure that the device is properly connected and configured in Windows.
In Motive, audio recording and playback settings can be accessed from Application Settings.
In Motive, open the Audio Settings, and check the box next to Enable Capture.
Select the audio input device that you want to use.
Press the Test button to confirm that the input device is properly working.
Make sure the device format of the recording device matches the device format that will be used in the playback devices (speakers and headsets).
Capture the Take.
Enable the Audio device before loading the TAK file with audio recordings. Enabling after is currently not supported, as the audio engine gets initialized on TAK load
Open a Take that includes audio recordings.
To playback recorded audio from a Take, check the box next to Enable Playback.
Select the audio output device that you will be using.
Make sure the configurations in Device Format closely match the Take Format. This is elaborated further in the section below.
Play the Take.
In order to playback audio recordings in Motive, audio format of recorded sounds MUST match closely with the audio format used in the output device. Specifically, communication channels and frequency of the audio must match. Otherwise, recorded sound will not be played back.
The recorded audio format is determined by the format of a recording device that was used when capturing Takes. However, audio formats in the input and output devices may not always agree. In this case, you will need to adjust the input device properties to match them. Device's audio format can be configured under the Sound settings in Windows. In Sound settings (accessed from Control Panel), select the recording device, click on Properties, and the default format can be changed under the Advanced Tab, as shown in the image below.
Recorded audio files can be exported into WAV format. To export, right-click on a Take from the Data pane and select Export Audio option in the context menu.
If you want to use an external audio input system to record synchronized audio, you will need to connect the motion capture system into a Genlock signal or a Timecode device. This will allow you to precisely synchronize the recorded audio along with the capture data.
For more information on synchronizing external devices, read through the Synchronization page.
In Motive, the Application Settings can be accessed under the View tab or by clicking icon on the main toolbar. Default Application Settings can be recovered by Reset Application Settings under the Edit Tools tab from the main Toolbar.
The Mouse tab under the application settings is where you can check and customize the mouse actions to navigate and control in Motive.
The following table shows the most basic mouse actions:
You can also pick a preset mouse action profiles to use. The presets can be accessed from the below drop-down menu. You can choose from the provided presets, or save out your current configuration into a new profile to use it later.
The Keyboard tab under the application settings allows you to assign specific hotkey actions to make Motive easier to use. List of default key actions can be found in the following page also: Motive Hotkeys
Configured hotkeys can be saved into preset profiles to be used on a different computer or to be imported later when needed. Hotkey presets can be imported or loaded from the drop-down menu:
In Motive, the Application Settings can be accessed under the View tab or by clicking icon on the main toolbar. Default Application Settings can be recovered by Reset Application Settings under the Edit Tools tab from the main Toolbar.
Sets the separator (_) and string format specifiers (%03d) for the suffix added after existing file names.
Enable/Disable auto-archiving of Takes when trimming Takes.
When enabled, all of the session folders loaded in the Data pane will be persisted when exiting and launching Motive again next time.
_[Advanced]_Sets the default device profile, XML format, to load onto Motive. The device profile determines and configures the settings for peripheral devices such as force plates, NI-DAQ, or navigation controllers.
[Advanced] Enter IP address of glove. Leave blank to use Local Host IP.
Enable or disable the LED panel in front of cameras that displays assigned camera numbers.
Sets how Camera IDs are assigned for each camera in a setup. Available options are By Location and By Serial Number. When assigning by location, camera IDs will be given following the positional order in clockwise direction, starting from the -X and -Z quadrant in respect to the origin.
Controls the color of the RGB Status Indicator Ring LEDs (Prime Series cameras only). Options include distinct indications for Live, Recording, Playback, Selection and Scene camera statuses, and you can choose the color for the corresponding camera status.
(Default: Blue) Sets the indicator ring color for cameras in Live mode.
(Default: Green) Sets the indicator ring color for cameras when recording a capture.
(Default: Black) Sets the indicator ring color for cameras when Motive is in playback mode.
(Default: Yellow) Sets the indicator ring color for cameras that are selected in Motive.
(Default: Orange) Sets the indicator ring color for cameras that are set as the reference camera in Motive.
(Default: Enabled) Controls whether the hibernation light turns on for the cameras when Motive is closed.
Configures the Aim Assist button. Sets whether the button will switch the camera to MJPEG mode and back to the default camera group record mode. Valid options are: True (default) and False.
(Default: Grayscale Only) Sets whether the camera button will display the aiming crosshairs on the the camera. Options: None, Grayscale Only, All Modes.
Enables or disables LED illumination on the Aim Assist button behind Prime Series cameras.
Sets the default device profile, XML format, to load onto Motive. The device profile determines and configures the settings for peripheral devices such as force plates, NI-DAQ, or navigation controllers.
Enter IP address of glove. Leave blank to use Local Host IP.
Shows which log file is loaded into Motive and displayed in the log pane. There is also a folder icon in order to change or add a log file.
Enable or disable continuous calibration for bumped cameras. When enabled, Motive will continuously monitor the calibration and update it as necessary. When this is set to true, calibration updates more invasively to accommodate for camera position/orientation changes. In general, if camera is significantly moved or displaced, it's suggested to calibrate the system again. For more information, refer to the Continuous Calibration page.
Restrict camera translation during continuous calibration.
Automatically loads the previous, or last saved, calibration setting when starting Motive.
The time duration, in seconds, that the camera system will auto-detect the existing extraneous reflections in order to apply masks during Calibration process.
Number of samples suggested for calibration. Depending on this setting, the sample count feedback will be colored differently during the Calibration process.
During the calibration wanding process, informative visuals are drawn over the camera view to show successfully collected wand samples and also to mark any extraneous reflections that appear. This is enabled by default. Disabling this will hide those calibration visuals.
When enabled, you can edit the camera calibration position with the 3D Gizmo tool.
Max distance cameras are translated by the position correction tool in mm.
Enables detection of PoE+ switches by High Power cameras (Prime 17W, PrimeX 22, Prime 41, and PrimeX41). LLDP allows the cameras to communicate directly with the switch and determine power availability to increase output to the IR LED rings. When using Ethernet switches that are not PoE+ Enabled or switches that are not LLDP enabled, cameras will not go into the high power mode even with this setting enabled.
In Motive, the Application Settings can be accessed under the View tab or by clicking icon on the main toolbar. Default Application Settings can be recovered by Reset Application Settings under the Edit Tools tab from the main Toolbar.
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.
This section 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.
(Default: False) Enables/disables broadcasting, or live-streaming, of the frame data. This must be set to true in order to start the streaming.
(Default: loopback) Sets the network address which the captured frame data is streamed to. When set to local loopback (127.0.0.1) address, the data is streamed locally within the computer. When set to a specific network IP address under the dropdown menu, the data is streamed over the network and other computers that are on the same network can receive the data.
(Default: Multicast) Selects the mode of broadcast for NatNet. Valid options are: Multicast, Unicast.
(Default: True) Enables, or disables, streaming of labeled Marker data. These markers are point cloud solved markers.
(Default: True) Enables/disables streaming of all of the unlabeled Marker data in the frame.
(Default: True) Enables/disables streaming of the Marker Set markers, which are named collections of all of the labeled markers and their positions (X, Y, Z). In other words, this includes markers that are associated with any of the assets (Marker Set, 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 a_Take_. In this data, Skeleton and Rigid Body markers are point cloud solved and model-filled on occluded frames.
(Default: True) Enables/disables streaming of Rigid Body data, which includes the name of Rigid Body assets as well as positions and orientations of their pivot points.
(Default: Skeletons) Enables/disables streaming of Skeleton tracking data from active Skeleton assets. This includes the total number of bones and their positions and orientations in respect to global, or local, coordinate system.
When enabled, this streams active peripheral devices (ie. force plates, Delsys Trigno EMG devices, etc.)
(Default: Global) When set to Global, the tracking data will be represented according to the global coordinate system. When this is set to Local, the streamed tracking data (position and rotation) of each skeletal bone will be relative to its parent bones.
(Default: Motive) Sets the bone naming convention of the streamed data. Available conventions include Motive, FBX, and BVH. The naming convention must match the format used in the streaming destination.
(Default: Y Axis) Selects the upward axis of the right-hand coordinate system in the streamed data. When streaming onto an external platform with a Z-up right-handed coordinate system (e.g. biomechanics applications) change this to Z Up.
(Default: False) Allows using the remote trigger for recording using XML commands. See more: Remote Triggering
(Default: False) When set to true, Skeleton assets are streamed as a series of Rigid Bodies that represent respective Skeleton segments.
(Default: True) When set to true, associated asset name is added as a subject prefix to each marker label in the streamed data.
Enables streaming to Visual3D. Normal streaming configurations may be not compatible with Visual3D, and this feature must be enabled for streaming tracking data to Visual3D.
Applies scaling to all of the streamed position data.
(Default: 1510) Specifies the port to be used for negotiating the connection between the NatNet server and client.
(Default: 1511) Specifies the port to be used for streaming data from the NatNet server to the client(s).
Specifies the multicast broadcast address. (Default: 239.255.42.99). Note: When streaming to clients based on NatNet 2.0 or below, the default multicast address should be changed to 224.0.0.1 and the data port should be changed to 1001.
Warning: This mode is for testing purposes only and it can overflood the network with the streamed data.
When enabled, Motive streams out the mocap data via broadcasting instead of sending to Unicast or Multicast IP addresses. This should be used only when the use of Multicast or Unicast is not applicable. This will basically spam the network that Motive is streaming to with streamed mocap data which may interfere with other data on the network, so a dedicated NatNet streaming network may need to be set up between the server and the client(s).To use the broadcast set the streaming option to Multicast and have this setting enabled on the server. Once it starts streaming, set the NatNet client to connect as Multicast, and then set the multicast address to 255.255.255.255. Once Motive starts broadcasting the data, the client will receive broadcast packets from the server.
Warning: Do not modify unless instructed.
(Default: 1000000)
This controls the socket size while streaming via Unicast. This property can be used to make extremely large data rates work properly.
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.
(Default: False) When enabled, Motive streams Rigid Body data via the VRPN protocol.
[Advanced] (Default: 3883) Specifies the broadcast port for VRPN streaming. (Default: 3883).
| Function | Default Control |
|---|---|
Rotate view
Right + Drag
Pan view
Middle (wheel) click + drag
Zoom in/out
Mouse Wheel
Select in View
Left mouse click
Toggle Selection in View
CTRL + left mouse click
