DepthMaps are killing me.
I have create a small 3 picture tour. One set has depthmaps uploaded the other does not.
I would really like to hear everyones thought on this.
-----------------------------------------------------
I used the Depth Anything V2 Base
max resolution of 512 I wonder if this is the problem.
----------------------------------------------------------
Below are my options for the depthmaps:
Depth-map model options
- Depth Anything V2 Small — Commercial use allowed; Apache 2.0 license. A practical lightweight option when you need quicker processing.
- Depth Anything V2 Base — Non-commercial only under CC BY-NC 4.0; likely offers stronger results than Small but should not be used in paid client projects.
- Depth Anything V2 Large — Non-commercial only under CC BY-NC 4.0; the larger model option, but not suitable for commercial delivery.
- MiDaS 3.0 Large — Commercial use allowed under the MIT license.
- MiDaS 3.1 Large — Commercial use allowed under the MIT license; a solid choice for professional image batches.
- ZoeDepth ZoeD_N — Commercial use allowed under MIT; trained with the NYU Depth V2 dataset, which generally makes it a sensible option for indoor scenes.
- ZoeDepth ZoeD_K — Commercial use allowed under MIT; trained with the KITTI dataset, making it relevant to outdoor/street-like imagery.
- ZoeDepth ZoeD_NK — Commercial use allowed under MIT; trained on both NYU and KITTI and described by the developer as the most versatile ZoeDepth option.
- Depth Pro — Available as another model-weight option; its download is nearly 2 GB, and the add-on currently runs it on CPU only rather than GPU.
Other depth options
- Depth-map styles — The product advertises 17 styles, so you can create alternate visual interpretations of each estimated depth map rather than being limited to one grayscale result.
- Batch sources — Process a directory of still images or video, then save the generated maps locally without relying on an external API.
- GPU acceleration — Optional GPU support is available through CUDA for NVIDIA GPUs or MPS for Mac GPUs; if no compatible GPU is detected, it falls back to CPU.
- CPU-only workflow — You can explicitly disable GPU use, and Depth Pro is presently CPU-only regardless.