-
Notifications
You must be signed in to change notification settings - Fork 447
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
drop in frames in real time mode (retrieveDepth()) #20
Comments
Hi, |
I'm sorry, I didn't know how to put it in words so I used the word frames dropped. But actually I had separate counters everytime zed.grab() was a success (count1) and when it wasn't (count2). So lets say when count1 was 2000, count 2 was around 70 Million. Maybe this will help. When I used a video to get depth with retrieveMeasure(), 20-21 frames were processed per second. Whereas, only 4.6 were processed in live mode. . I used standard clock to find out the time for processing. Is there a way to better this performance ? Could it be an OS problem ? Configuration: Thanks! |
Oh ok, I see. The status of |
Yes, you are right. I get it now. Can you recommend the best possible way to get the depth map(retrieveImage()) at minimum 30fps while using ZED camera in live mode? I even have a more powerful system. |
Hey,
so I am calling the retriveMeasure() after the zed Grab() function to get the depth from the camera in the real time mode. But so many frames are being dropped without being processed. For example around 70 million frames were dropped when only 2000 frames were processed. I tried with svo_real_time_mode = true/false both. But got similar results. Is there a way I can fix this problem ?
The text was updated successfully, but these errors were encountered: