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

Why the depth data is 424*512*4? #23

Open
huangshaoguang opened this issue Jul 12, 2019 · 2 comments
Open

Why the depth data is 424*512*4? #23

huangshaoguang opened this issue Jul 12, 2019 · 2 comments

Comments

@huangshaoguang
Copy link

Hello! Thank you for sharing. Why the depth data is 4245124? What does the depth data of every dim mean?

@pedrombmachado
Copy link

Well because you will get R, G, B and Depth channels.

@JesseSilverberg
Copy link

I am also having issues with the depth data returned by getDepthData(). The fourth channel value is always 69, no matter how far away the object is.

This repo is said to be python bindngs to libfreenect2, but when I go into libfreenect2 and run ./bin/Protonect, the depth image looks nothing like the depth image from this library. In libfreenect2, every distance is given a homogeneous gray value, that changes uniformly with distance. This depth image gives varying pixel colors for a single object, meaning a flat wall looks green and purple.

The depth image also doesn't cover the same field of view as the color image, and I am wondering how to match up depths of pixels in the color image.

I am running this with python 2.7.6 on ubuntu 14.04.

depth

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

3 participants