Skip to main content

Workflow overview

Understanding the Move API workflow is essential for building effective motion capture applications. This guide explains the fundamental process from video input to motion capture data output.

The basic workflow​

The Move API workflow consists of four main steps:

Video Upload → Take Creation → Job Creation → Processing → Outputs

1. Video upload​

Upload your video file(s) to the Move API. The API supports various video formats and can handle both single-camera and multi-camera setups.

2. Take creation​

When you submit a video for processing, the API creates a "job" - a processing task that will analyze your video and extract motion capture data.

3. Job creation​

When you submit a video for processing, the API creates a "job" - a processing task that will analyze your video and extract motion capture data.

4. Processing​

The job runs in the background, using AI, biomechanics and physics models to:

  • Detect and track human subjects and skeletal keypoints
  • Infer kinematic data
  • Infer dynamics data
  • Generate 3D motion capture data outputs

5. Output download​

Once processing is complete, the job produces outputs in several format - the final motion capture data that contains the 3D skeletal animation.

Workflow types​

Single-camera workflow​

For single-camera motion capture:

  1. Upload a single video file
  2. Select a single-camera model
  3. Process and download the take

Multi-camera workflow​

For multi-camera motion capture:

  1. Upload multiple video files from different camera angles
  2. Provide camera calibration data
  3. Select a multi-camera model
  4. Process and download the take

Key concepts​

Files​

A file represents a input video file. Each file has:

  • Type: The video format (MP4, MOV, AVI)
  • URL: PresignedURL to upload the file to or download it from

Takes​

A take in Move API represents a distinct recording session or motion capture sequence. It is created from one or more uploaded video files and serves as the core data entity for processing and analysis. Takes are used as inputs to jobs, which generate motion capture outputs from the recorded footage. Each take has:

  • Sources: A group of video file and file type associated with the take.

Jobs​

A job represents a processing task. Each job has:

  • Status: Running, Completed, Failed
  • Model: The Move AI model used for processing
  • Input: Video files and parameters
  • Output: The resulting take

Processing time​

Processing time varies based on:

  • Video length: Longer videos take more time
  • Video Resolution: Higher the resolution more time
  • Model complexity: s2 and m2 models are more accurate but slower
  • Number of cameras: Multi-camera setups require more processing

Next steps​