Papers › VIBE: Video Inference for Human Body Pose and Shape Estimation

VIBE: Video Inference for Human Body Pose and Shape Estimation

11 Dec 2019CVPR 2020 6arXiv:1912.05656archive 2025-07-28

Muhammed Kocabas, Nikos Athanasiou, Michael J. Black

Human motion is fundamental to understanding behavior. Despite progress on single-image 3D pose and shape estimation, existing video-based state-of-the-art methods fail to produce accurate and natural motion sequences due to a lack of ground-truth 3D motion data for training. To address this problem, we propose Video Inference for Body Pose and Shape Estimation (VIBE), which makes use of an existing large-scale motion capture dataset (AMASS) together with unpaired, in-the-wild, 2D keypoint annotations. Our key novelty is an adversarial learning framework that leverages AMASS to discriminate between real human motions and those produced by our temporal pose and shape regression networks. We define a temporal network architecture and show that adversarial training, at the sequence level, produces kinematically plausible motion sequences without in-the-wild ground-truth 3D labels. We perform extensive experimentation to analyze the importance of motion and demonstrate the effectiveness of VIBE on challenging 3D pose estimation datasets, achieving state-of-the-art performance. Code and pretrained models are available at https://github.com/mkocabas/VIBE.

PaperPDFConference PDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

The archive's official repository (mkocabas/VIBE) was not harvested; the 1 sample below comes from 1 community repository.

Syntology 1 code sample harvested from 1 repository linked to this paper: 0 ran · 1 unverified.

By repository: community (archive-listed): 1 sample from 1 repository, 0 ran (0 with no instrument failure; 0 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

mkocabas/VIBE officialmentioned in papermentioned on GitHubpytorchNOASSERTIONSyntology: not harvested report
ahmedosman/STAR mentioned on GitHubtfNOASSERTIONSyntology: not harvested report
darkAlert/vibe-rt mentioned on GitHubpytorchNOASSERTIONSyntology: not harvested report
oli4jansen/VIBE_old mentioned on GitHubpytorchNOASSERTIONSyntology: not harvested report
sudarsanGyrus/3D_Pose_VIBE mentioned on GitHubpytorchSyntology: 1 sample, 0 ran · 1 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

1 sample harvested: 0 ran · 1 unverified. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1unverified

Licence: 1 of the 1 sample is pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from sudarsanGyrus/3D_Pose_VIBE. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

sudarsanGyrus/3D_Pose_VIBE community (archive-listed) 1 sample, 0 ran · 1 unverified
Rodrigues lib/utils/fbx_output.py unverified no licence file found · pointer only · d745ffdd0bddc8b2 · report

Tasks

3D Human Pose Estimation3D Pose Estimation3D Shape ReconstructionMonocular 3D Human Pose EstimationPose Estimation

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
3D Human Pose Estimation 3DPW VIBE Acceleration Error 23.4 #46 of 119 Archive leaderboard report
3D Human Pose Estimation 3DPW VIBE MPJPE 82.9 #46 of 119 Archive leaderboard report
3D Human Pose Estimation 3DPW VIBE MPVPE 99.1 #46 of 119 Archive leaderboard report
3D Human Pose Estimation 3DPW VIBE Number of parameters (M) 72.43 #46 of 119 Archive leaderboard report
3D Human Pose Estimation 3DPW VIBE PA-MPJPE 51.9 #46 of 119 Archive leaderboard report
3D Human Pose Estimation Human3.6M VIBE Average MPJPE (mm) 65.6 #87 of 88 Archive leaderboard report
3D Human Pose Estimation Human3.6M VIBE Multi-View or Monocular Monocular #87 of 88 Archive leaderboard report
3D Human Pose Estimation Human3.6M VIBE PA-MPJPE 41.4 #87 of 88 Archive leaderboard report
3D Human Pose Estimation Human3.6M VIBE Using 2D ground-truth joints No #87 of 88 Archive leaderboard report
3D Human Pose Estimation MPI-INF-3DHP VIBE MPJPE 96.6 #58 of 108 Archive leaderboard report
3D Human Pose Estimation MPI-INF-3DHP VIBE PA-MPJPE 64.6 #58 of 108 Archive leaderboard report
3D Human Pose Estimation MPI-INF-3DHP VIBE PCK 89.3 #58 of 108 Archive leaderboard report
Monocular 3D Human Pose Estimation Human3.6M VIBE Average MPJPE (mm) 65.6 #35 of 52 Archive leaderboard report
Monocular 3D Human Pose Estimation Human3.6M VIBE Frames Needed 16 #35 of 52 Archive leaderboard report
Monocular 3D Human Pose Estimation Human3.6M VIBE Need Ground Truth 2D Pose No #35 of 52 Archive leaderboard report
Monocular 3D Human Pose Estimation Human3.6M VIBE Use Video Sequence Yes #35 of 52 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Methods

1x1 ConvolutionAverage PoolingBatch NormalizationBottleneck Residual BlockConvolutionGRUGlobal Average PoolingKaiming InitializationMax PoolingReLUResidual BlockResidual Connection

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections