#4242nd of 70 in Open modelsFor image, video and design, 3d

vipe

Estimates camera pose, intrinsics and dense depth from raw video

Stars
2.2k
License
custom license
Last commit
Nov 2026
Last release
Jun 2026
Language
Python
Stars, last 29 weeks+355
21 Apr 2026: 1,845 stars28 Apr 2026: 1,863 stars5 May 2026: 1,875 stars12 May 2026: 1,890 stars19 May 2026: 1,897 stars26 May 2026: 1,913 stars2 Jun 2026: 1,930 stars9 Jun 2026: 1,957 stars16 Jun 2026: 1,973 stars23 Jun 2026: 1,979 stars30 Jun 2026: 1,987 stars7 Jul 2026: 1,997 stars14 Jul 2026: 2,014 stars21 Jul 2026: 2,034 stars28 Jul 2026: 2,041 stars4 Aug 2026: 2,050 stars11 Aug 2026: 2,057 stars18 Aug 2026: 2,065 stars25 Aug 2026: 2,081 stars1 Sept 2026: 2,091 stars8 Sept 2026: 2,099 stars15 Sept 2026: 2,107 stars22 Sept 2026: 2,115 stars29 Sept 2026: 2,128 stars6 Oct 2026: 2,134 stars13 Oct 2026: 2,137 stars20 Oct 2026: 2,139 stars27 Oct 2026: 2,151 stars3 Nov 2026: 2,157 stars10 Nov 2026: 2,200 stars

1,845 on 21 Apr 20262,200 on 10 Nov 2026

From GitHub's daily star counts.

Checked on GitHub.

Overview

ViPE is a Python pipeline from NVIDIA that estimates camera intrinsics, camera motion and near-metric dense depth from unconstrained video, including wide-angle and 360-degree panorama footage. It installs from PyPI (nvidia-vipe) and runs through a `vipe infer` CLI. Newer pipelines handle long videos with bounded memory (`pose_only_long`) and streaming metric reconstruction with loop closure and point cloud export (`metrictrail`).

Who it is for: Researchers annotating video with camera poses and depth for 3D or robotics data

Strengths

  • Handles pinhole, wide-angle and 360-degree panorama video in one tool
  • `pose_only_long` keeps GPU and CPU memory roughly constant regardless of video length
  • Outputs pose, intrinsics and depth per video; MetricTrail adds PLY point cloud export
  • Release 1.2.0 reports a 2.7x speed-up from CUDA fused kernels and caching

Weaknesses

  • Mixed licensing: Apache 2.0 source, but Unik3D is BY-NC-SA 4.0 and MetricTrail weights are noncommercial
  • MetricTrail needs custom CUDA kernel builds, a pinned xformers and CUDA 12.8 toolchain
  • MetricTrail weights are obtained separately; the Hugging Face release is described as planned
  • Loop closure needs external SALAD candidates exported from a separate environment

What it needs

  • GPU required
  • Needs CUDA 12.8, conda, uv, xformers 0.0.33.post1, PyPose (optional, loop closure), SALAD (optional, loop closure)
  • Models: MoGe v2 (moge2-l), Depth-Anything 3, DINO-DPVO, DINOv3 ViT-S/16, Unik3D

Quick answers

Is vipe open source?

Its code is public on GitHub under its own license terms; read them before you use it at work.

Does vipe need a GPU?

Yes, it needs a GPU.

Also in Open models

See all 70
Also in Open models
RankProjectScore
1ruviewWiFi CSI sensing on ESP32 for presence, breathing, heart rate and pose104k starsMIT94 out of 100
2layaSingle-pass multilingual classifier for typed choice, score and yes/no decisions Live demo ↗ (opens in a new tab)35.4k stars+3,167 (+9.8%) in 30 daysApache-2.088 out of 100
3rf-detrReal-time transformer models for object detection, segmentation and keypoints Live demo ↗ (opens in a new tab)10k starsApache-2.079 out of 100
#4timesfmPretrained time-series foundation model for zero-shot forecasting from Google Research35.4k stars+1,231 (+3.6%) in 30 daysApache-2.078 out of 100
#5yolov5PyTorch YOLOv5 object detection, segmentation and classification models with training code58.3k starsAGPL-3.076 out of 100