2020-07-29 13:28:31 -0600 | received badge | ● Popular Question (source) |
2014-08-30 13:00:57 -0600 | commented answer | Stereo Calibration (HTC Evo 3D) @curtis newton the links are not about opencv but they're useful nonetheless. The toolboxes in the links can calibrate cameras using multiple chessboard in a single image but in opencv you can use several pictures of a chessboard in different position. The tips provided in the links are still valid... |
2014-08-28 11:59:53 -0600 | commented answer | Stereo Calibration (HTC Evo 3D) I said Htc because the first question is about calibrating Htc evo's cameras... I don't know any golden rule to obtain a good calibration with normal (no autofocus) webcams. See this answer for some common mistakes about camera calibration. |
2014-08-27 06:02:14 -0600 | commented answer | Stereo Calibration (HTC Evo 3D) sry @curtis newton, are you referring to bad rectification using webcams? How is your problem related to the Htc smartphone? Do you use the sample rectification program provided with opencv sources to perform disparity maps? |
2014-08-18 12:26:03 -0600 | commented question | bad rectification and high rms returned by stereoCalibration @markotruba i know you had already read this answer but i fully agree with this as i explain here i tried to bypass the takePhoto() call but the problems persist. PS. using my photo app reduce rms error but i don't get any improvements in the rectified images (and so in the disparity maps) |
2014-06-03 09:54:53 -0600 | received badge | ● Critic (source) |
2014-06-03 09:54:13 -0600 | answered a question | Stereo Calibration (HTC Evo 3D) i have the same problem and i tryed to use my personal camera app without calling the pictureCallback. I essentialy use the previewCallback and i save the arriving frame using Highgui.imwrite to store the jpeg picture. Using my camera app gave me no result and the rectified images are the same of njaa's ones. So the changing of the intrinsic parameters (if it is is the real problem) occurs continously during the preview and not only after the photo has been taken... |
2014-05-23 08:38:07 -0600 | commented question | bad rectification and high rms returned by stereoCalibration UPDATE: if i resize all the calibration images before processing them, i can reduce the rms error a lot but the rectified images gain no improvements. I have completely black rectified pair! |
2014-05-23 05:09:09 -0600 | asked a question | bad rectification and high rms returned by stereoCalibration Hi, i have some problems while computing rectification of stereo pairs: stereoCalibration returns an high rms error and i obtain bad rectification pairs. I tried both my rectification program and the stereo_calib.cpp provided with opencv. They both returns similiar rms errors. Plus, i ran my program with the sample stereo pairs in opencv/sample/cpp and i got correctly rectified images. So i believe the problem is in the way i take stereo picture, is it possible? I use the stereo camera of an Htc Evo 3D (a 3D smartphone) taking pictures of a chessboard pattern. I tried to change the number and the set of pictures used as input but the littlest stereoCalibration rms i got was around 1.5 and the rectified images are totally wrong. |
2014-05-15 05:58:34 -0600 | received badge | ● Supporter (source) |
2014-03-23 10:57:17 -0600 | commented question | Error in every OpenCV sample for android Hi, i don't know the answer to your problem but i had the same error. I changed the "Project Build Target" (under properties, Android) of the OpecCV library project to the latest set of APIs and cleaned all the projects... Hope it can help... |
2014-03-20 05:10:24 -0600 | received badge | ● Editor (source) |
2014-03-18 14:54:31 -0600 | asked a question | opencv for android samples error Hi, I followed the documentation to set up the environment to develop Android application. I have an error in the opencv library and I can not execute the samples provided with the library. I can compile the samples only if I select android api 4.4.2 in the project build target under android in the opencv project's properties. Using the api 3.0 or 2.2 doesn't work... EDIT: Maybe it will be better if i add some more infos... I'm working with: Linux Debian (Wheezy? Well... the stable one...)
I'd like to know whether i selected as Project Build Target for the OpenCV Library project (I chose Android 4.4.2) is correct or not to compile my app on an older version of android too. |