Hello,I am working on a LifeCAM studio for tracking purposes in an indoor enviroment,- I am facing problems in the calibration step- Camera resolution is 1280p @30 fps- I am trying to work on the corrected image after the perspective calibration applied- I am getting sluggish image results when working on the corrected image- I am NOT GETTING sluggish image results when working on the UNCORRECTED image as you can see above:- non calibrated image (uncorrected image)- calibrated image (corrected image)- tracking (thresholding) As a trial to solve this sluggish video problem, I was thinking of throwing the calibration block from the loop to the initialization. Then, I found an option to do that in VBAI (learn calibration at each iteration). So I did some benchmarks (corrected image applied) and here are the results: seems that there is no big difference, but when I do the benchmark (corrected image is not applied) I am getting high FPS ~25 fps Here are the VI:And here is the VI when I am trying to get the calibration blocks out of the loop Questions:1- Why am I getting low FPS sluggish image results when working on the corrected image (LabVIEW or VBAI) and how can I solve it ?2- How can I solve the probe execution problem ? H/W specs:- CORE 2 DUO 3.00GHz- 4GB RAM- INTEL Q45 CHIPSET Thank you in advance,Regards

I assume your image correction is in the same loop as your image acquisition. Correction is a very slow process, so it takes a while before it can loop and grab the next image. Normally you don't apply correction to a live image. It is usually applied to a single image before you do your analysis. Bruce

Machine Vision

Low FPS after applying perspective calibration to acquire a corrected image in LabVIEW

Solved!

Author

Thank you all for your help, really appreciated !

Tracking the vehicle will be based on the calibrated uncorrected image then, I was just troubleshooting the task if I can do it on the calibrated corrected image, it seems that it can be achieved with higher FPS but with a bit more complications in the code which it won't be needed in my case