-
Notifications
You must be signed in to change notification settings - Fork 29
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
How to use captured depth images? #10
Comments
The depth image is upscaled quite a bit. I think its something in the order of 250x120 (not sure what the exact number is). I think what you are seeing is mostly the interpolation. |
Hi, I have a problem converting the captured depth image to real depth. |
Looks like the offline depth is not working properly. I'll try and fix it soon. Sorry about that. |
As a work-around, we (Spectacular AI), have released an alternative offline-focused iOS data collection app that can record both depth and high-resolution video at high FPS. Its outputs can be used for InstantNGP, Nerfstudio (step-by-step tutorial) and probably even SplaTAM (see here). |
I would also recommend looking into polycam app, they enable a developer mode that allows for getting rgb + depth + camera poses/intrinsic parameters. https://github.com/PolyCam/polyform this may simplify the need for having to use a network connection |
Any update on the fix for the offline version? |
Hey sorry I have not had the chance to look at this yet. However, if anyone is compiling from source and would like to have a go at fixing it, these are the lines that need changing: The problem is that |
I'm not familiar with processing pixels on IOS. So I save depth as binary and process it on PC with Python. |
Hello,
Thank you for the great work!!
I'm using NeRFCapture app for obtaining RGB-D images and poses.
However, when generating point cloud using these data, It is something weird.
I think it is because of depth image scale.
How to resolve it, and What is the scale of the depth map from the NeRFCapture?
Thank you 🥹
The text was updated successfully, but these errors were encountered: