Hi,
I'm using V120 with Motive 3.4 for a tracking project. Due to field-of-view and space constraints, I can only use one camera, which means I cannot get 3D coordinates through multi-camera triangulation.
However, I found that 2D marker coordinates from the single camera would still work for my tracking and motion analysis needs.
Question: Can Motive export 2D marker coordinates (pixel/image coordinates) from a single camera? I currently can only export 3D coordinates, and couldn't find 2D export options in the manual.
Any help appreciated!
Thanks!
Can Motive 3.4 Export 2D Marker Coordinates from Single Camera?
-
SunngCHEN1999
- Posts: 3
- Joined: Mon Nov 03, 2025 12:17 am
Re: Can Motive 3.4 Export 2D Marker Coordinates from Single Camera?
Actually, you don't need Motive for that. I am facing similar issue with 4-camera setup and really small space with lot of occlusion.
You can use CameraSDK to access camera feed directly. https://docs.optitrack.com/developer-tools/camera-sdk
There is plenty of examples with code that gathers 2D data / images. You can control camera mode / config.
The only thing I found out is that intrinsic parameters returned by this API is a stub:
Core::DistortionModel model;
camera->GetDistortionModel(model);
It does not match camera parameters generated by Motive calibration process, at least for my Flex13 cameras.
So currently I gather 2D data using this API, but for calibration I use data from "C:\Users\User\Documents\OptiTrack\Calibrations\" mcal file. It is simple XML file with all data available.
You can use CameraSDK to access camera feed directly. https://docs.optitrack.com/developer-tools/camera-sdk
There is plenty of examples with code that gathers 2D data / images. You can control camera mode / config.
The only thing I found out is that intrinsic parameters returned by this API is a stub:
Core::DistortionModel model;
camera->GetDistortionModel(model);
It does not match camera parameters generated by Motive calibration process, at least for my Flex13 cameras.
So currently I gather 2D data using this API, but for calibration I use data from "C:\Users\User\Documents\OptiTrack\Calibrations\" mcal file. It is simple XML file with all data available.