movementaIn dev
Pear Tree Performance Coaching

Climb Analysis

Advice for users

Tips to optimize uploads and troubleshoot common analysis issues.

  • Camera position: For the most accurate pose estimation, stand with the camera about 3–4 m from the wall, in front of the climb (perpendicular to the climb plane), and pan to follow the climber. Static shots also work, but accuracy may vary as the climber gets smaller or larger in frame.
  • Video download timeout: For long or high-resolution clips, trim the clip to the climb itself before uploading, run the analysis on a desktop browser, and use a stable Wi-Fi connection.
  • Interrupted or stalled runs: Keep this tab open and the screen awake until the report appears. The analysis runs in your browser, so leaving the page or letting the screen lock stops it. Phones and tablets may suspend video decoding when the screen locks or the tab is backgrounded; use a laptop if possible.
  • Analyzer errors (non-2xx): This is usually a temporary backend hiccup. Start the analysis again in a few minutes — it often succeeds on the next attempt.
  • Network drops: Re-run the analysis on a stable connection. A dropped network mid-analysis is safe to retry.
  • Save / upstream timeouts: If a run fails right at the end, open the report before re-running; the analysis may have saved anyway.

Leave blank if the video was filmed today. Setting this when uploading older footage keeps trend graphs and analyses on the right calendar position.

Entering the details below helps optimize the analysis outcome.

Used to filter dashboard trends — separate competition performance from day-to-day training.

Each angle is analysed on its own; the reports are linked so you can switch between angles or compare them side by side.

Telling us the outcome anchors the top-out inference and keeps feedback coherent. On a rope, "reached the end with falls / rests" counts as reaching the anchor but not as a clean send; "recording cut" tells the analyzer not to treat the abrupt ending as a fall.

The report prose is written in this language. Scores, metric names and reference titles stay unchanged so reports remain comparable.

Keeps the report from overstating progress — without it a fall well below the finish can be described as "just below the final holds".

If the route is set in one color (common in gyms), tell us which — the AI will only consider on-color holds as on-route and won't suggest using off-color holds in its feedback.

If multiple people appear (spotter, belayer, another climber), this helps the AI analyse the right person. We'll also ask you mid-flow if our pose tracker spots more than one.

If auto-tracking still struggles, cropping the video before upload is the strongest fallback.

On-device pose tracking
MediaPipe Pose runs over the whole clip in your browser. Tracks the climber across multiple people via persistence + upward motion.
Robust mode (3 local pose runs)
Runs MediaPipe pose tracking 3 times with different sampling rates and reports each numeric movement, joint and load score as mean ± SD. Fully local — no extra AI tokens. Adds ~2× pose-tracking time.

We adaptively sample keyframes across the full video — denser around dynos, foot cuts, and rests — plus a high-resolution reference frame, then run AI movement analysis.

Report depth

Reports are produced in Balanced mode unless you choose otherwise — not the deepest setting. Pick a deeper mode for more detail, or a quicker one for a faster answer.

Times appear once the video length is known.

Analysis density
Frame budget scales with clip duration and motion. Defaults keep short and long clips at the same per-second granularity.
Pose tracking density
Pose tracking follows the climb's motion: a steady base rate everywhere, full rate around dynos, foot cuts and cruxes, and never more than a short gap without a pose, so annotated moments and body metrics stay covered. Short clips are tracked at full rate.

Pick a video file to enable Run analysis.

Sessions

Latest analysis pipeline: 2026.10.01

Loading sessions…