-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Alignment mode broken for Orbbec Femto Bolt recording #46
Comments
Hey! It's a known issue to us that the Internally, all the flag does is set:
We currently don't have a Femto Bolt device, so I cannot check if the issue has been fixed if we updated our OrbbecSDK version (currently v1.10.5). Previously, enabling In any case, I would recommend not using the
Currently, this isn't possible through our Orbbec wrapper, but for recordings, you can modify the calibration.json file with your custom calibration. See: https://github.com/SpectacularAI/docs/blob/main/pdf/calibration_manual.pdf |
Thanks for the reply! |
Thanks for pointing that out! Looks like that may be the correct way to enable |
Hello, Just wondering if there are any updates on this issue? I am running into a similar issue where setting Additional Info |
Hi all,
I use your Orbbec wrapper to record data with a Femto Bolt camera. Guided by your recording example here: recording script, I am trying to set
config.alignedDepth = true;
. When I do that, however,obPipeline->getCameraParam();
return only zeroes after thespectacularAI::orbbecPlugin::Pipeline vioPipeline(*obPipeline, config, mappingCallback);
initialization. After that, a crash follows. The error can be reproduced directly with the script mentioned above.I checked that the depth stream resolution (512x512) supports depth alignment with the OrbbecSdk. Moreover, the ROS1 Wrapper for OrbbecSDK produces correctly aligned images with the same settings. This is why I consider this a SAI issue.
The SDK version is 1.34
PS. Can I set my custom camera intrinsics calibration with your SDK? I find the factory one to be non-satisfactory.
The text was updated successfully, but these errors were encountered: