Downloads
Not sure which developer tool to use? Learn more ▸
NatNet SDK
NatNet's client/server architecture allows client applications to run on the same network or computer as the tracking software (Motive). The SDK integrates seamlessly with standard languages (C/C++/C#/Python), tools (Microsoft Visual Studio), and protocols (UDP/Unicast/Multicast). Using the NatNet SDK, developers can quickly integrate OptiTrack motion tracking data into new and existing applications, including custom plugins to third-party applications and engines for real-time streaming. Learn more
NatNet SDK 4.0.0
This version of the NatNet SDK adds some improvements and fixes to the previous release. It is intended to work smoothly with all versions of Motive.
Note: The 4.0 update includes bit-stream syntax changes to allow up to 32 force plates to be streamed at once. This requires corresponding updates for each program that uses the 'direct depacketization' approach for parsing streamed data.
- Details & Requirements
-
- Released Date: August 3, 2021
- File Format: ZIP (Windows), TAR (Linux)
- Some features require Motive 3.0.0 Beta 1+
- Changelogs
-
- NatNet SDK 4.0.0 August 3, 2021
-
- Features
-
- Unicast Data Subscription - Users can now adjust Unicast streaming clients to configure the tracking data they receive. For example, each client can now subscribe to specific rigid bodies and receive only the subscribed tracking data over unicast; making the streaming packets lighter and faster for each client. This cuts down the latency for large VR installations and smaller systems alike. (Supported in Motive 2.2+.)
- Rigid Body Forward Prediction - Predict rigid body positions/orientations into the future by a configurable amount of time.
- Bitstream Version Configuration - The bitstream version may now be configured to work with multiple clients running different versions of NatNet.
- Camera Positions - Added camera position information data to the NatNet data descriptions.
- Reduced the total number of samples included to help make NatNet easier to understand; improved each of the remaining samples.
- Increased the maximum number of force plates supported in the data stream to 32.
- Updated the main NatNet solution file to use VisualStudio 2019 (v142).
- Added the ability for NatNet to get/set the frame rate of Motive.
- Added support for remotely getting, and setting, properties (such as colors) that have vector types.
- Added informative error messages when Motive attempts to connect to a client with incorrect settings, and improved connection reliability.
- Hardcoded the auto-connection port to 1513 to allow for exceptions to ports with firewalls or anti-virus for applications that wish to auto-connect.
- Reduced network traffic in large systems by lengthening keep-alive message interval to 10 seconds.
- WinForms Application
- Modified the WinFormsTestApp to show the same force plate value as Motive on each frame when there are more force plate frames than tracking frames.
- Updated the name of this project to just "WinFormsSample".
- Fixed an issue with the enable/disable asset button.
- SampleClient and Sample3DClient and SampleClientML
- Updated the color scheme of the SampleClient3D to better match Motive.
- Hid several labeled marker tags in the SampleClient that are no longer relevant.
- Updated the SampleClinetML to include camera devices.
- Added the ability to give command-line arguments to the SampleClientML example.
- Python and Packet Clients
- Added New Types - Added force plates, DAQ devices, and cameras to the PythonClient and PacketClient.
- Added Objects for Data Types - Rewrote the PythonClient to follow a more object-oriented coding model.
- Updated the PythonClient to better conform to PEP8 coding standards.
- Added the PythonClient to the default VisualStudio project file
- Updated the user commands for the PythonClient and PacketClient to be more useful.
- Add the ability to specify the bitstream syntax version for the PythonClient and PacketClient.
- Fixed a variety of other issues in the PythonClient related to data reliability, thread safety, and coding standards.
- Fixed an issue where the PythonClient would disconnect from Unicast connections.
- Fixed an issue with the PacketClient where it was not reading the correct number of bytes of skeleton data.
- Fixes
-
- Fixed an issue where a remote record trigger would not work when the eSync is put into a ready state.
- Fixed negative streaming ID values in some instances.
- Fixed some small issues to allow the PacketClient to work with Unicast.
- Fixed a lost "unknown message" handler callback when switching between unicast/multicast.
- NatNet SDK 3.1 September 11, 2018
-
- Updated the sample projects for the Apache Software License. This gives greater open source freedom with the NatNet redistributable.
- Included additional timing metrics and recording to the WinForms application.
- Updated the python depacketizer sample to match the correct rigid body descriptions.
- Updated the SampleClient and SampleClient3D projects, so that they may be used exclusively with unlabeled markers.
- Updated the explanation of labeled markers in the PacketClient.cpp to be more descriptive.
- Improved clarity of the version and compilation information for sample applications.
- Added a broadcast option to the multicast data channel.
- Fixed a crash when attempting to stream over 99 rigid bodies at one time.
- Fixed a crash with the WinForms test app by removing the ability to edit text in the IP address combo box.
- Fixed an issue where the labeled marker list did not report the flags when a labeled marker was occluded.
- Fixed a bug with automatically determining the IP address on start.
- Fixed a bug in the WinForms test app that caused it to report incorrect rigid body data in some cases.
- Fixed a bug in the WinForms test app where it would not refresh when switching between multicast and unicast.
- Renamed "Labeled Markers" to just "Markers" in the WinForms application.
- NatNet SDK 3.0.1 November 7, 2017
-
- Cleaned up the SampleClient by removing OtherMarkers sample and refactoring some other code.
- Updated the PDF user guide.
- Updated the PacketClient to show correct marker id decoding and marker params usage.
- Updated samples projects to Visual Studio 2015.
- Fix for unavailable transmission latency when connecting to Motive via Unicast.
- Fix for Packet Client showing all markers as unidentified and fix logic in OtherMarker list.
- Fix for streaming skeletons as rigid bodies setting crashing the SampleClient3D when enabled.
- Fix for issue with getting data descriptions from a take with markersets.
- NatNet SDK 3.0.0 September 8, 2017
-
- Features & Enhancements
-
- Added support for streaming of analog data such as NIDAQ data from Motive.
- NatNet now provides more accurate and detailed methods for determining the latency during different processes in Motive.
- Added the ability to remotely configure Motive software settings from NatNet clients.
- Added an active marker ID property to marker data type to support new active markers over NatNet. Also, included active marker ID information in the rigid body marker descriptions.
- Reorganized the member methods of the NatNetClient class. Previous methods are still supported for this release; refer to NatNetClient.h for details.
- Updated the sample applications, including the WinFormSamples app, to demonstrate the newly added features.
- Added RebroadcastMotiveData sample for streaming using serial port communication.
- Now includes pre-built sample applications for both 32-bit and 64-bit applications in the samples/bin directory.
- Added the ability to automatically discover Multicast/Unicast client. As a result, the ConnectionType Enum has been deprecated.
- Added an auto-detection feature for finding IP addresses of the available NatNet tracking server, improving the usability of several client applications.
- Added SampleClientML sample for demonstrating a basic use of the managed library.
- Compatibility Notes
-
- Important: Static linking is no longer supported. Projects that utilized NatNetStaticLib.lib will need to be updated to link dynamically instead.
- SDK security update: Starting from 3.0, the NatNet library will strictly work with Motive only. Other server applications, including Arena and Tracking Tools, are no longer compatible.
- Deprecated Connection Type Enum for clients. Clients now just need to invoke NatNetClient::Connect.
- Removed fLatency metrics from the frame of mocap data.
- Removed marker positions and corresponding property values from sRigidBodyData. They can now be obtained from sRigidBodyDescription.
- NatNet SDK 2.10.0 June 27, 2016
-
- Features & Enhancements
-
- Updated the User Guide to include new information and correct formatting / grammatical errors.
- Added NatNet Unity3D sample code for skeleton re-targeting using Mecanim.
- Added NatNet Python depacketization client into NatNet SDK Samples directory.
- Added reference to open source NatNet based Maya plug in.
- Added 'keep alive' streaming command to resolve issues with UDP unicast clients going to sleep.
- Fixes
-
- Fixed issue where WinFormsTestApp crashed on exit.
- Fixed crash in WinFormsTestApp when streaming more than 44 rigid bodies.
- Fixed issue where WinFormsTestApp became non-responsive after selecting multiple items.
- NatNet SDK 2.9.0 October 19, 2015
-
- Features & Enhancements
-
- Added: Motive 1.9 streaming support.
- Added: Stream ID of unlabeled markers over NatNet. Please refer to updated Winforms sample to show new unlabeled marker data access.
- Added: Add Force Plate information to data descriptions and FrameOfMocapData structure. ( Bitstream syntax change)
- Added: (NatNet Managed Library (NatNetML) only) Update Winforms sample to illustrate data polling as an alternative to data callback.
- Fixes
-
- Fixed: (NatNet Managed Library (NatNetML) only) Update NatNetML with marker parameter data (e.g. occluded flag)
- NatNet SDK 2.8.0 September 2, 2015
-
- Features & Enhancements
-
- Added: Motive 1.8 streaming support
- Added: New MATLAB wrapper sample.
- Added: Add playback range and looping commands ("SetPlaybackStartFrame,frameNumber", "SetPlaybackStopFrame,frameNumber", "SetPlaybackLooping,0or1") to NatNet command list, and updated NatNet SDK Winforms and PacketClient samples to illustrate usage.
- Added: DecodeID() helper routine, which illustrates usage in Winforms and SampleClient apps for decoding legacy marker ID
- Added: Updated Unity3D streaming sample to stream rigid bodies and skeletons.
- Added: Add Z-up quaternion to Euler decoding example to WinForms sample when streaming Z-up from Motive.
- Added: Add support and examples for explicitly disconnecting Unicast clients.
- Added: Add support for Z-up streaming, and update SampleClient 3D to illustrate usage.
- Changed: (NatNetML only) Change GetLastFrameOfData() routine in managed client to lock the frame and return a copy of the data (polling clients only). Update WinForms sample app to illustrate usage.
- Changed: (NatNetML only) Provide copy constructors to simplify .NET client data deep copy operations, and update Winforms sample with data copy operation.
- Changed: (NatNetML only) Fix graphing for correct frame alignment for Motive.
- Changed: (NatNetML only) Add timing testing operations and reporting.
- Fixes
-
- Fixed: Fix for PointCloud solved bit indicator.
- Fixed: Debug x64 WinformsSample was not compiling out of the box.
- Fixed: RigidBody tracked flag in managed clients is now transmitted correctly.
- NatNet SDK 2.7 October 21, 2014
-
- Features & Enhancements
-
- Motive 1.7 Streaming support
- New timing sample for validating mocap streaming frame timing.
- New Broadcast Trigger sample illustrating how to use remote record trigger/listen using XML formatted UDP broadcast packets instead of NatNet commands.
- NatNetML - added SMPTE Timecode and Timecode Subframe members. See WinForms sample for usage.
- Fixes
-
- Fix for FrameID periodically displays dropped/duplicate packets during live mode.
- Fix for PacketClient incorrectly decoding rigid Body IsTracked parameter.
- Fix for crash in GetDataDescriptions() when streaming a Rigid Body with a single character name.
- Sample Clint incorrectly reports skeleton marker data
- Update SampleClient3D to clarify quaterion decomposition, add new visuals.
- Maximum markers per rigid body changed from 10 to 20 to match new RigidBody tracking capabilities in Motive.
- Frame timestamp now keyed off hardware frame id. fTimestamp resolution increased from float to double *.
* DirectDepackatization clients should update their code (see timestamp in PacketClient.cpp for an example).
- NatNet SDK 2.6 May 8, 2014
-
- Features & Enhancements
-
- Added Motive 1.6 streaming support.
- New RigidBody tracking state parameter added to the NatNet stream.
- IsRecording flag on FrameOfMocapData was added, indicating frame was recorded in Motive.
- ModelsChanged flag on FrameOfMocapData indicating actively tracked model list has changed.
- Additional flags on LabelMarkerList indicating marker occlusion and marker position calculation method.
- Additional FrameOfMocapData timestamp added to the stream.
- NatCap remote capture sample for illustrating send/receive of Motive remote control commands via UDP direct broadcast.
- UDP Repeater / Unity3D
- Increased the unlabeled/other marker count cap to 1000 markers per frame.
- Fixes
-
- SampleClient latency value was incorrectly calculated.
- NatNet SDK 2.5 October 2, 2013
-
- Features & Enhancements
-
- Added Motive 1.5 streaming support.
- A new Matlab sample demonstrates how to read from the NatNet stream through MatLab scripts.
- Additional function signature overloads to better support MatLab.
- Added new Motive remote control commands Start/Stop Recording, Start/Stop Playback, LiveMode, EditMode, SetRecordTakeName, SetLiveTakeName. Refer to WinForms sample for usage examples.
- Added Motive record broadcast message parser sample.
- Samples were updated to illustrate accessing point cloud model solved marker locations.
- Added timing information to WinForms sample.
- New QuaternionToEuler() helper routines are now included.
- Winforms Sample updated with a new layout and sample Command/Requests for use with Motive.
- Fixes
-
- SimplerServer compile issue.
- SampleClient when more than two skeletons are streaming.
Camera SDK
Free SDK includes full camera control, access to 2D object data, camera synchronization, and 6DoF vector tracking. Sample apps are packaged as part of the SDK installer. Learn more
Camera SDK 3.1.0 Beta 1
This is the latest version that is compatible with Motive 3.1.0 Beta 1.
- Details
-
- Release Date: October 3, 2023
- File Format: EXE
- API binary compatible with Motive 3.1.0 Beta 1
- Changelogs
-
- Camera SDK 3.0.1 Beta 1 October 3, 2023
-
- Brought the Camera SDK back for compatibility with Motive 3.1.
- Created a new installer for the Camera SDK.
- Added an example to show how to configure camera properties such as the frame rate.
- Added an example to show how to connect to an eSync and display timecode data.
- Replaced internal mutexes with recursive mutexes to have better reliability.
- Camera SDK 2.3.6 September 25, 2023
-
- Released to maintain API binary compatibility with Motive 2.3.6 Final
- Slim 3U cameras with a serial numbers 26279 or higher must be run with the Camera SDK 2.3.6+.
- Flex 3 cameras with a serial number 25869 or higher must be run with the Camera SDK 2.3.6+.
- Camera SDK 2.3.5 June 29, 2023
-
- Released to maintain API binary compatibility with Motive 2.3.5 Final
- Fixed issues with object and precision mode for newer Flex 3 and Slim 3U cameras.
- Camera SDK 2.3.4 March 28, 2023
-
- Released to maintain API binary compatibility with Motive 2.3.4 Final
- Added support for PrimeX 41 and PrimeX 22 cameras over serial number M99450+
- Camera SDK 2.3.3 March 9, 2023
-
- Released to maintain API binary compatibility with Motive 2.3.3 Final
- Slim 3U cameras with a serial number 446597 to 446999, and 477234 or higher must be run with Motive 2.3.3+.
- Flex 3 cameras with a serial number 512030 or higher must be run with Motive 2.3.3+.
- Camera SDK 2.3.2 November 22, 2022
-
- Released to maintain API binary compatibility with Motive 2.3.2 Final
- Camera SDK 2.3.1 February 17, 2022
-
- Released to maintain API binary compatibility with Motive 2.3.1 Final
- Updated the Camera SDK EULA.
- Camera SDK 2.3.0 July 1, 2021
-
- Released to maintain API binary compatibility with Motive 2.3.0 Final
- Camera SDK 2.2.0 November 8, 2019
-
- Released to maintain API binary compatibility with Motive 2.2.0 Final
- Added additional details to the color video sample for libav integration.
- Camera SDK 2.1.2 August 21, 2019
-
- Released to maintain API binary compatibility with Motive 2.1.2
- Camera SDK 2.1.1 January 23, 2019
-
- Released to maintain API binary compatibility with Motive 2.1.1
- Camera SDK 2.1 November 9, 2018
-
- Released to maintain API binary compatibility with Motive 2.1.
- Camera SDK 2.1 Beta 2August 30, 2018
-
- Released to maintain API binary compatibility with Motive 2.1 Beta 2.
- Camera SDK 2.1 Beta 1July 27, 2018
-
- Released to maintain API binary compatibility with Motive 2.1 Beta 1.
- Camera SDK 2.0.2 April 25, 2018
-
- Released to maintain API binary compatibility with Motive 2.0.2.
- Included a sample application for the new Color Camera.
- Added the FrameRateCalculation sample to the Camera SDK.
- Camera SDK 2.0.1 January 5, 2018
-
- Released to maintain API binary compatibility with Motive 2.0.1.
- Camera SDK 2.0 November 13, 2017
-
- Released to maintain API binary compatibility with Motive 2.0.0.
- Camera SDK 2.0 Beta 3October 4, 2017
-
- Released to maintain API binary compatibility with Motive 2.0.0 Beta 3.
- Camera SDK 2.0 Beta 2September 8, 2017
-
- Released to maintain API binary compatibility with Motive 2.0.0 Beta 2.
- Camera SDK 2.0 Beta 1July 25, 2017
-
- Released to maintain API binary compatibility with Motive 2.0.0 Beta.
- Include sample application for the new Color Camera.
- Added the FrameRateCalculation sample to the Camera SDK.
- Camera SDK 1.10.3May 8, 2017
-
- Released to maintain binary compatibility with Motive 1.10.3.
- Fix for CameraSDK not shutting down properly.
- Camera SDK 1.10.2January 30, 2017
-
- Released to maintain binary compatibility with Motive 1.10.2.
- CameraSDK now has libraries for Visual Studio 2015.
- Camera SDK 1.10.1August 26, 2016
-
- Released to maintain binary compatibility with Motive 1.10.1.
- Camera SDK 1.10June 27, 2016
-
- Released to maintain binary compatibility with Motive 1.10.0.
- Camera SDK 1.10 BetaMay 3, 2016
-
- Released to maintain binary compatibility with Motive 1.10.0 Beta 1.
- Camera SDK 1.9December 14, 2015
-
- Released to maintain binary compatibility with Motive 1.9.0.
- Camera SDK 1.9 Beta 2December 1, 2015
-
- Released to maintain binary compatibility with Motive 1.9.0 Beta 2.
- Camera SDK 1.9 Beta 1Octoeber 26, 2015
-
- Released to maintain binary compatibility with Motive 1.9.0 Beta 1.
- Camera SDK 1.8August 5, 2015
-
- Released to maintain binary compatibility with Motive 1.8.0.
- Camera SDK 1.8 Beta 2June 29, 2015
-
- Released to maintain binary compatibility with Motive 1.8.0 Beta 2.
- Camera SDK 1.8 Beta 1April 30, 2015
-
- Released to maintain binary compatibility with Motive 1.8.0 Beta 1.
- Camera SDK 1.7.5March 25, 2015
-
- Released to maintain binary compatibility with Motive 1.7.5.
- Camera SDK 1.7.4March 17, 2015
-
- Add support for eSync 2.
- Camera SDK 1.7.3March 2, 2015
-
- Released to maintain API binary compatibility with Motive 1.7.3
- Camera SDK 1.7.2December 5, 2014
-
- Released to maintain API binary compatibility with Motive 1.7.2
- Camera SDK 1.7.1November 26, 2014
-
- Released to maintain API binary compatibility with Motive 1.7.1
- Camera SDK 1.7November 17, 2014
-
- Released to maintain API binary compatibility with Motive 1.7.0
- Camera SDK 1.7 Beta 2November 4, 2014
-
- Released to maintain API binary compatibility with Motive 1.7.0 Beta 2
- Camera SDK 1.7 Beta 1October 17, 2014
-
- Adds support for the new Slim 13E camera.
- Released to maintain API binary compatibility with Motive 1.7.0 Beta 1
- Camera SDK 1.6 Beta 2June 19, 2014
-
- Released to maintain API binary compatibility with Motive 1.6.0 Beta 2
- Camera SDK 1.6 Beta 1May 6, 2014
-
- Added support for the new Prime 13/13W camera series
- Released to maintain API binary compatibility with Motive 1.6.0 Beta 1
- Camera SDK 1.5.1April 18, 2014
-
- Released to maintain API binary compatibility with Motive 1.5.1
- Camera SDK 1.5October 15, 2013
-
- Released to maintain API binary compatibility with Motive 1.5
- Camera SDK 1.5 Beta 2 September 26, 2013
-
- Released to maintain API binary compatibility with Motive 1.5 Beta 2
- Camera SDK 1.5 Beta 1 August 26, 2013
-
- Fixed an issue with cModuleSync2 when removing cameras
- Improved reliability and speed of Ethernet camera discovery
- Camera SDK 1.2.2 June 25, 2013
-
- Fix to correct LLDP/PoE+ detection on Cisco switches
- Camera SDK 1.2.1 May 21, 2013
-
- Released to maintain API binary compatibility with Motive 1.0.1
- Camera SDK 1.2 April 24, 2013
-
- Added support for OptiTrack Prime 17W cameras
- Updated sample projects & VisualTest application
- Camera SDK 1.2 Beta March 19, 2013
-
- Added support for the OptiTrack Prime 41 camera
- Added support for hardware timestamping when using Ethernet devices
- Added access to uncompressed JPEG image data from cameras
- Camera SDK 1.1.6 March 11, 2013
-
- Fixed Flex 13 IR LEDs not working when used with an OptiHub connected to some USB 3.0 ports
- Camera SDK 1.1.5 March 5, 2013
-
- Fixed some V120:SLIM cameras operating at incorrect frame rates
- Camera SDK 1.1.4 January 2, 2013
-
- Improved OptiHub operation for 120hz
- Fixed S250e PoE power issues with Cisco switches at slow frame rates
- Fixed External Sync not working correctly for V100:R2 cameras
- Fixed Exposure sync out pulse not aligned with shutter for V100:R2 cameras
- Camera SDK 1.1.3 June 15, 2012
-
- No changes from 1.1.3 Beta 2
- Camera SDK 1.1.3 Beta 2 May 22, 2012
-
- Implemented OptiHub Sync out exposure timing for Flex 13 cameras
- Changed Flex 13 cameras to not free run when sync signal missing in external sync mode
- Fixed Flex 13 cameras sometimes running at 100hz instead of 120hz
- Camera SDK 1.1.3 Beta 1 May 4, 2012
-
- Added support for Flex 13 devices
- Fixed compatibility S250e issue in previous 1.8.0 release
- Fixed possible loss of sync for S250e cameras at less than 100 FPS
- Camera SDK 1.1.2 Beta February 15, 2012
-
- Added support for eSync devices
- Added ability to use Camera SDK and Tracking Tools API from the same process
- Added dynamically linked run-time Camera SDK libs
- Added Time Code support via eSync
- Added access to marker shape via object segment list
- Added undistorted 2D to distorted 2D point model
- Changed to new installer platform
- Improved 8-bit rasterization performance
- Improved MJPEG performance significantly
- Improved S250e Hardware Object Mode
- Previous Releases
-
-
Camera SDK 2.3.6
- Details & Requirements
-
- Release Date: September 25, 2023
- File Format: EXE
- API binary compatible with Motive 2.3.6
-
Camera SDK 2.3.5
- Details & Requirements
-
- Release Date: June 29, 2023
- File Format: EXE
- API binary compatible with Motive 2.3.5
-
Camera SDK 2.3.4
- Details & Requirements
-
- Release Date: March 28, 2023
- File Format: EXE
- API binary compatible with Motive 2.3.4
-
Camera SDK 2.3.3
- Details & Requirements
-
- Release Date: March 9, 2023
- File Format: EXE
- API binary compatible with Motive 2.3.3
-
Camera SDK 2.3.2
- Details & Requirements
-
- Release Date: November 22, 2022
- File Format: EXE
- API binary compatible with Motive 2.3.2
-
Camera SDK 2.3.1
- Details & Requirements
-
- Release Date: February 17, 2022
- File Format: EXE
- API binary compatible with Motive 2.3.1
-
Camera SDK 2.3.0
- Details & Requirements
-
- Release Date: July 1, 2021
- File Format: EXE
- API binary compatible with Motive 2.3.0
-
Camera SDK 2.2.0
- Details & Requirements
-
- Release Date: November 8, 2019
- File Format: EXE
- API binary compatible with Motive 2.2.0
-
Camera SDK 2.1.2
- Details & Requirements
-
- Release Date: August 21, 2019
- File Format: EXE
- API binary compatible with Motive 2.1.2
-
Camera SDK 2.1.1
- Details & Requirements
-
- Release Date: January 23, 2019
- File Format: EXE
- API binary compatible with Motive 2.1.1
-
Camera SDK 2.1.0
- Details & Requirements
-
- Release Date: November 9, 2018
- File Format: EXE
- API binary compatible with Motive 2.1
-
Camera SDK 2.0.2
- Details & Requirements
-
- Release Date: April 25, 2018
- File Format: EXE
- API binary compatible with Motive 2.0.2
-
Camera SDK 2.0.1
- Details & Requirements
-
- Release Date: January 5, 2018
- File Format: EXE
- API binary compatible with Motive 2.0.1
-
Camera SDK 2.0
- Details & Requirements
-
- Release Date: November 13, 2017
- File Format: EXE
- API binary compatible with Motive 2.0
-
Camera SDK 1.10.3
- Details & Requirements
-
- Release Date: May 8, 2017
- File Format: EXE
- API binary compatible with Motive 1.10.3
-
Camera SDK 1.10.2
- Details & Requirements
-
- Release Date: January 30, 2017
- File Format: EXE
- API binary compatible with Motive 1.10.2
-
Camera SDK 1.10.1
- Details & Requirements
-
- Release Date: August 26, 2016
- File Format: EXE
- API binary compatible with Motive 1.10.1
-
Camera SDK 1.10
- Details & Requirements
-
- Release Date: June 27, 2016
- File Format: EXE
- API binary compatible with Motive 1.10
-
Camera SDK 1.9
- Details & Requirements
-
- Release Date: December 14, 2015
- File Format: EXE
- API binary compatible with Motive 1.9
-
Camera SDK 1.8
- Details & Requirements
-
- Release Date: August 5, 2015
- File Format: EXE
- API binary compatible with Motive 1.8
-
Camera SDK 1.7.5
- Details & Requirements
-
- Release Date: March 24, 2015
- File Format: EXE
- Released to maintain API binary compatibility with Motive 1.7.5
-
Camera SDK 1.7.4
- Details & Requirements
-
- Release Date: March 17, 2015
- File Size: 115 MB
- File Format: EXE
- Released to maintain API binary compatibility with Motive 1.7.4
-
Camera SDK 1.7.3
- Details & Requirements
-
- Release Date: March 2, 2015
- File Size: 103 MB
- File Format: EXE
- Released to maintain API binary compatibility with Motive 1.7.3
-
Camera SDK 1.7.2
- Details & Requirements
-
- Release Date: December 5, 2014
- File Size: 103 MB
- File Format: EXE
- Released to maintain API binary compatibility with Motive 1.7.2
-
Camera SDK 1.7.1
- Details & Requirements
-
- Release Date: November 26, 2014
- File Size: 103 MB
- File Format: EXE
- Released to maintain API binary compatibility with Motive 1.7.1
-
Camera SDK 1.7
- Details & Requirements
-
- Release Date: November 17, 2014
- File Size: 103 MB
- File Format: EXE
- API binary compatible with Motive 1.7
-
Camera SDK 1.5
- Details & Requirements
-
- Released Date: October 15, 2013
- File Size: 95.9 MB
- File Format: EXE
- API binary compatible with Motive 1.5
-
Camera SDK 1.2.2
- Details & Requirements
-
- Released Date: June 25, 2013
- File Size: 77.3 MB
- File Format: EXE
- API binary compatible with Motive 1.0.2
-
Camera SDK 1.2.1
- Details & Requirements
-
- Released Date: May 21, 2013
- File Size: 77.3 MB
- File Format: EXE
- API binary compatible with Motive 1.0.1
-
Camera SDK 1.2
- Details & Requirements
-
- Release Date: Released Date: April 24, 2013
- File Size: 77.3 MB
- File Format: EXE
-
Camera SDK 1.1.6
- Details & Requirements
-
- Release Date: March 11, 2013
- File Size: 43.6 MB
- File Format: EXE
-
Camera SDK 1.1.5
- Details & Requirements
-
- Release Date: March 5, 2013
- File Size: 43.6 MB
- File Format: EXE
-
Camera SDK 1.1.4
- Details & Requirements
-
- Release Date: January 2, 2013
- File Size: 43.6 MB
- File Format: EXE
-
Camera SDK 1.1.3
- Details & Requirements
-
- Release Date: June 15, 2012
- File Size: 41.6 MB
- File Format: EXE
-
Camera SDK 2.3.6
Active Batch Programmer
Utility for programming OptiTrack Active hardware including Active Tags, Active Pucks, Active HMD clips, etc.This is an advanced tool for reconfiguring Active hardware after initial factory configuration.
Active Batch Programmer 1.6.0
This is the latest version that is compatible with OptiTrack Active technology.
- Details
-
- Release Date: May 16, 2023
- File Format: EXE
- Works with: Windows 64 bit.
- Changelogs
-
- Active Batch Programmer 1.6.0 May 16, 2023
-
- New Features
-
- New Installer - Created an installer for the Active Batch Programmer.
- Radio Intensity Property - Added the ability to set the radio Signal Intensity.
- Added sliders for Signal Intensity and LED Brightness.
- Added a way to clear the log.
- Added the ability to program CinePucks with newer versisons of firmware.
- Added third party license files to the ZIP file.
- Hard coded log output to (C:\ProgramData\Optitrack\Active_Batch_Programmer_Logs\).
- Fixes
-
- LED Brightness Full Range - Fixed an issue where the full range of the LED brightness was not allowed. You may now set brightness values from 0 to 255.
- Fixed an issue where the IMU Uplink ID would increment when programming non-IMU tags.
- Fixed an issue where programming a tag twice in the same session didn't work.
- Fixed an issue where choosing "Auto Brightness" would turn off the LEDs.
- Fixed an issue where the toggle for setting the LED brightness was not respected.
- Fixed an issue where the Label Group values were shown in the log for 1.x firmware tags even though they do not support that feature.
- Fixed an issue where the word "Brightness" was partially clipped.
- Removed an error message about PanID values which are no longer used.
- Removed the firmware version from the heading.
- Removed the extra two LED on/off options leaving the ability to enable up to 8 markers.
- Active Batch Programmer 1.5.0 July 27, 2022
-
- Initial public release of programming utility for OptiTrack Active technology.
- Previous Releases
-
-
Active Batch Programmer 1.5.0
- Details & Requirements
-
- Release Date: July 27, 2022
- File Format: Zip, EXE
- Works with: Windows 64 bit.
-
Active Batch Programmer 1.5.0