-
Notifications
You must be signed in to change notification settings - Fork 19
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
Wrong Detection? How to properly calibrate? #9
Comments
One more input after further checking: it seems like the orientation of the device (e.g. a smartphone in this case) has an impact on the calibration. When I capture frames, and calibrate in portrait with a single marker, tracking is working okay - however in landscape mode the axis are looking wrong. |
Hello I'm glad this application has help you. In addition to the 15-20 frames, did you capture at least 10 markers in each frame? I have never encountered this kind of calibration error, maybe because I have never tested the application on android 11. On my side, I will update the application so that it supports android 11. Thank you. |
Hi, Thanks for your quick feedback! Yes, I did capture at least 10 markers in each frame. Some further information: in my project I am using the OpenCV-Contrib V.4.5.3 from QuickBird Studio. Another thing I noticed is that the One final comment: in my app I eventually grouped the calibration & tracking into a single app to still be able to use shared preferences. Thanks! |
Hi @RivoLink! Thank you very much for sharing this project. I'm also trying to implement it on Android 11 and we are facing the following error: "Error: Can't load camera parameters." Perhaps this is about @jmariller is mentioning: "...in my app I eventually grouped the calibration & tracking into a single app to still be able to use shared preferences." Thank you in advance! :) |
I got it! Thank you! |
Hi @RivoLink
First of all thanks a lot for providing this application, it helped me a lot to start building a prototype based on ArUco - I needed to adapt your implementation slightly so that it works under Android 11 (e.g. cannot use mode world readable for preferences), but it eventually ran.
Now I am facing another challenge: the calibration seems to be working, as it effectively stores values in preferences which seem okay, however when I run the detection part of the application, the axis look all messed up - worse, when I am filming the full board the application hangs. Any idea what I am doing wrong, how do you properly calibrate the board? I assume 15-20 frames shall be captured from different viewpoints, right?
Many thanks in advance for your help!
The text was updated successfully, but these errors were encountered: