Motion Capture System Product

Overview

A motion-capture (mocap) system is an optical instrument that tracks the 3D position and orientation of a human actor in real-time, converting body motion into digital skeletal data for animation engines. It is the industry standard for character animation in film, games, and virtual production. Real-time mocap feeds live skeletal pose to character models being rendered on set or in a virtual-production engine, enabling directors to see performances in-engine immediately.

The system works by placing retroreflective markers on an actor's body, illuminating them with infrared light, and using synchronous cameras to triangulate their 3D positions at high speed. Multiple cameras (8–16) provide redundancy and spatial resolution; the more cameras covering a volume, the better the tracking quality and the fewer lost-frame problems.

Optical tracking principle

Each IR Camera contains a 1–2 megapixel infrared sensor paired with an IR Ring Light LED array at 850 nm wavelength. The Camera Lens is a wide-angle (50°) C-mount lens providing field of view coverage of ±2 m at typical 3 m distance. The sensor is global-shutter (not rolling), capturing all pixels simultaneously to freeze motion.

When illuminated by the ring light, retroreflective markers (typically 3M 7610 or equivalent Retroreflective Marker) appear as bright white spots in the camera's infrared image. The marker is a hemispherical ball coated with retro-reflective material—light bounces straight back toward its source (the ring light surrounds the lens, so light returns directly to the sensor). This retroreflection is the key: regular white paint would scatter light; retro-reflective material concentrates it.

The Camera Bracket allows pan/tilt adjustments so each camera covers a portion of the motion-capture-system-tracking-volume. Overlapping camera coverage allows the software to triangulate each marker's position from multiple viewpoints.

Synchronization

All cameras must capture frames at the exact same time; otherwise, if a marker moves between frames, different cameras see it in different locations, breaking triangulation. The Sync Hub solves this by distributing a genlock (timing reference) signal to all cameras via BNC connectors. The Genlock Generator is typically 50 or 60 Hz (matching the power line frequency) or a custom frequency like 24 Hz (matching film frame rate). All cameras trigger their sensors on this clock pulse, ensuring pixel-perfect synchronization. Modern systems may use 1588 PTP (Precision Time Protocol) over Ethernet instead of hardware genlock.

The IR Camera transmits raw image data (2 MB per frame × 200 fps × 8 cameras ≈ 3 GB/s) to the Sync Hub via GigE or Thunderbolt. The hub buffers frames and forwards them to the Compute Server.

Real-time tracking and solving

The Software Engine performs two tasks: centroid detection and skeleton solving.

Centroid detection finds the center of each bright spot (marker) in each camera image. A simple thresholding algorithm isolates pixels above a brightness threshold, then computes the centroid. With marker occlusion and camera noise, this is more complex in practice; commercial software uses sub-pixel fitting and outlier rejection.

Triangulation uses the 3D camera positions (determined during calibration) and the 2D image coordinates to compute 3D marker positions. This is multi-view geometry: if marker M is seen at pixel (u1, v1) in camera 1 and (u2, v2) in camera 2, there is a unique 3D point in space consistent with both observations.

Skeleton solving fits a Compute Server template skeleton (e.g., 48 joints) to the cloud of 3D marker positions. This is a constraint-satisfaction problem: joints should be at fixed distances (bone lengths), joints should not penetrate skin, and motion should be smooth. The solver outputs quaternion rotations at each joint, forming the final skeletal output.

All of this runs on a Compute Server with a GPU Accelerator (RTX 6000 or dual RTX 4090) providing parallel processing. Frame rates of 100–200 Hz are standard; latency is 5–10 ms end-to-end (sensor to output).

Marker suit and placement

The Marker Suit is a form-fitting garment (typically nylon or spandex) with sewn pockets or loops to hold Retroreflective Marker spheres. Standard rigging places markers at anatomically-correct joint positions: shoulders, elbows, wrists, hips, knees, ankles, plus spine, neck, and head. More detailed capture (facial animation) requires additional facial markers.

The Head Cap holds multiple markers on the head; some systems use Marker Stickers (adhesive retroreflective circles) for temporary placement on actor skin for finer detail capture (hand fingers, face points).

Calibration

Before tracking begins, the system must know the 3D positions and orientations of all cameras. This is done via the Calibration Wand—a carbon-fiber rod with exactly-spaced markers (e.g., 100 mm and 400 mm from the tip). The operator moves the wand slowly through the entire motion-capture-system-tracking-volume while all cameras record its position. The software solves for each camera's position and lens distortion parameters.

The Calibration Wand is also used to define the world origin (where 0,0,0 is) and to establish the XY plane (floor level).

Data output and integration

The Software Engine outputs skeletal pose in real-time over Ethernet via UDP or TCP. Standard formats include BVH (Biovision Hierarchy), C3D, or proprietary formats. Animation engines (Maya, MotionBuilder, Unreal Engine, game engines) connect to this data stream and drive virtual character rigs in real-time. Latency is critical: for live AR applications or virtual production on-set, 5–10 ms latency is acceptable; higher latency causes unsettling jitter.

Recording and archival

The Storage SSD records raw camera frames and solved skeleton data for archival and post-processing. With 8 cameras at 2 MP and 200 fps, data rates reach 30–50 TB per hour—requiring fast NVMe storage and large drive arrays. Post-production cleanup, marker merging, and skeleton refinement are performed offline in software like MotionBuilder.

Operational considerations

• Occlusion (marker hidden behind prop or actor) is the main failure mode. More cameras reduce occlusion probability.
• Reflections from shiny props or floors can create false markers. Matte surfaces are preferred.
• Outdoor use is problematic due to sunlight IR noise; systems are designed for indoor, controlled lighting.
• Cost is substantial: $150k–$500k for a full 16-camera professional system installed.
• Operator skill is critical; correct marker placement and calibration require training.