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

realsense2 getDepthWidth() is not consistent with data output #5

Open
randaz81 opened this issue Jun 11, 2020 · 1 comment
Open

realsense2 getDepthWidth() is not consistent with data output #5

randaz81 opened this issue Jun 11, 2020 · 1 comment

Comments

@randaz81
Copy link
Member

I want to discuss this strange behavior of the yarp realsense2 driver (in the tests, I used a D435 camera)

Introduction: resolution 320x240 is not available for the depth camera, but it is ok for the rgb camera. The minimum resolution for the depth camera is 422x240.

Issue:
If I set depth resolution to 422x240 and the rgb resolution 320x240, then I have the two following possibilities:

  1. if depth and rgb outputs are not aligned (option needAlignment= false), then the depth output port broadcasts an image with a width of 422 (that's ok). Additionally, the method realsense2Driver::getDepthWidth() returns a width of 422 (that's ok too).

  2. if depth and rgb outputs are aligned (option needAlignment= true), then the depth output port broadcasts an image with a width of 320 (that's ok, since the alignment crops the depth image to the width of the rgb image). But the method realsense2Driver::getDepthWidth() returns a width of 422.

I think this behavior is either wrong or, if it is intentional, it seems to me that it is not documented, and it generates confusion. What do you think? @xEnVrE @lnobile @Nicogene

@Nicogene Nicogene self-assigned this Jun 12, 2020
@Nicogene
Copy link
Member

Hi @randaz81 ,

The resolution of the depth and rgb are taken from the internal structures without interrogating the hardware.

I don't remember if I didn't do it because it wasn't possible or if I just did a mistake.
In the latter case I think it is a bug that can easily addressed

@Nicogene Nicogene removed their assignment Jun 12, 2020
@drdanz drdanz transferred this issue from robotology/yarp Jan 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants