DocumentationMotionCommons · Developer preview

Capture and recorded imports

Developer preview

Preserve original recordings and attach them to the correct patient session.

Docs/Use MotionCommons
Ask Claude

Capture and recorded imports

Page Markdown

The complete guide, ready to copy or save as a Markdown file.

Download .md ↓

Record, verify and seal

Integrity verification establishes accepted bytes. It does not establish clinical quality, camera calibration, synchronization or biomechanical validity.

  1. Choose an authorized patient session and create a capture trial.
  2. Upload the original video through the private resumable transport. Interrupted uploads can resume.
  3. Run exact-byte integrity verification before accepting the asset.
  4. Seal the single-view or multiview capture set and replay the original video.

Review an OptiGait package

The standalone OptiGait review page has been removed. Stored packages remain private study evidence, and the synthetic session dashboard stays available as a generated preview.

The adapter preserves recorded evidence. Importing a package does not run inference or APP EXACT replay. Use generated synthetic fixtures for automated testing.

sh
uv run python tools/dev.py --optigait

Inspect metadata locally

This explicit local mode uses the local development stack and fixed inspection worker. Install ffprobe first. The run ledger records input provenance, attempts and accepted metadata reports.

Native metadata inspection is distinct from full media-quality validation, OpenSim processing, video-to-3D inference and general cloud jobs.

sh
uv run python tools/dev.py --local --inspect

Accessibility

Make every MotionCommons page comfortable for you. Settings apply on this browser.

Text size

Your training, at your pace.

Reading & movement
Audio support

Spoken audio is unavailable in this browser. All instructions remain available as text.

Read this page speaks up to 1,800 characters of visible page text. Embedded dashboards have their own Read dashboard button.