-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Realsense D455 duplicated depth arrays #10669
Comments
Hi @tmxftw I see you are using two separate pipelines with their own unique configurations, like the Python code in #1735 (comment) When you say that the arrays are duplicated, do you mean that the second camera's depth array has the same values as the first camera's depth array? Or is it that in the second array, the frame numbers are repeating (1, 1, 1, 2, 2, 2, 3, 3, 3, etc) If the problem is that the frame numbers are repeating then a RealSense team member advises at #5107 (comment) to use poll_for_frames() instead of wait_for_frames() to avoid duplicate frames. Using poll_for_frames() in applications that handle more than one camera is also Intel's recommendation, as advised at #2422 (comment) |
|
I am still trying to implement poll_for_frames(), however, I have several questions regarding how to use it:
|
I tried to implement poll_for_frames() like so, by changing wait_for_frames() with poll_for_frames() and keeping said frames.
However, the issues with duplicate depths is still occuring |
https://dev.intelrealsense.com/docs/multiple-depth-cameras-configuration https://dev.intelrealsense.com/docs/external-synchronization-of-intel-realsense-depth-cameras |
Hi @tmxftw Do you require further assistance with this case, please? Thanks! |
Case closed due to no further comments received. |
Issue Description
I am trying to use two D455 cameras to get the rgb and depth data as numpy arrays. The cameras are attached onto a moving rover and it will capture depth and rgb data as it moves, hence the cameras should be getting different depth data. The individual arrays will be saved on the pi as the code runs, and downloaded to a desktop for further processing. However, after checking the acquired data, the depth arrays are duplicated and repeated, causing the data to be useless for further processing. On the other hand, the rgb images are captured properly.
The trend of duplicates seems to be more common for the second camera of self.pipeline_1.
The main issue i am trying to tackle is to reduce the duplication of depth arrays.
A secondary issue will be to increase the frame rate of captured data, which is currently less than 1.
This is the code which I used to check for duplicates in the depth arrays:
This is the camera class I created to record the numpy arrays:
The text was updated successfully, but these errors were encountered: