Skip to content
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

Capturing frames without frame drops #7663

Closed
a-m-p-m opened this issue Oct 27, 2020 · 3 comments
Closed

Capturing frames without frame drops #7663

a-m-p-m opened this issue Oct 27, 2020 · 3 comments

Comments

@a-m-p-m
Copy link

a-m-p-m commented Oct 27, 2020

Hello,

I hope this is an appropriate place for the following question:

Given that there is a substantial level of frame drops in RealSense Viewer at high fps (e.g., 90 fps for 848x480 frame size: #7488), did anyone had a success capturing and saving frames from the camera (e.g., D435) using there own piece of software without frame drops for 848x480 @ 90 fps setting?

Thanks.

@MartyG-RealSense
Copy link
Collaborator

MartyG-RealSense commented Oct 28, 2020

Hi @a-m-p-m If you are saving the frames to disk in real-time as they are captured then there is the possibility of bottlenecks occurring with the computer hardware, such as a storage device with slow access speeds (e.g a non-SSD hard drive).

The file format that you are saving in may have a bearing on speed of writing. Bag files are the most efficient recording format in the RealSense SDK, whilst writing frames to other formats such as ply and csv may be considerably slower.

Also, are you using the official 1 meter cable supplied with the camera please? If you use your own cable, the choice of cable can have a bearing on data transfer due to varying quality of third-party USB cables. The company Newnex can provide industrial-grade USB equipment.

https://www.newnex.com/realsense-3d-camera-connectivity.php

If you are recording for a short period (e.g up to 30 seconds) then an SDK function called Keep() may suit you. It records frames to the computer's memory instead of writing them to file. When the pipeline is closed, you can do batch-processing on the frames such as align and post-processing and then save the data to file. The technique consumes computer memory capacity though, which is why it is best suited to short recording durations.

@MartyG-RealSense
Copy link
Collaborator

Hi @a-m-p-m Do you still require assistance with this case, please? Thanks!

@MartyG-RealSense
Copy link
Collaborator

Case closed due to no futher comments received.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants