Camera tracking comparison · 2026
Two of the most-deployed optical camera tracking systems for broadcast, virtual production, and LED volumes. An objective, technical comparison from the team behind RedSpy, so you can pick the right fit for your production.
Sources: stYpe internal specifications and testing; Mo-Sys StarTracker Max Brochure 2026 (mo-sys.com).
All three systems deliver broadcast-grade camera tracking. The technical differences below determine which is the right fit for your production type.
| Feature | RedSpy | StarTracker Max |
|---|---|---|
| Tracking method | Optical, marker-based (retroreflective markers) | Optical, marker-based (retroreflective stars) |
| Marker placement | Ceiling, wall, or floor | Ceiling, wall, or floor |
| Studio prep required | Marker placement, one-time mapping | Star placement, one-time star map creation |
| Typical setup time | Several hours for initial installation | Fast lock on power-on once star map exists; multi-hour initial install |
| Outdoor capable | Yes | No publicly available examples of outdoor projects |
| Indoor studio | Yes | Yes |
| LED volume | Yes | Yes |
| Digital markers for LED walls | Yes, stYpe’s patented pierced-marker technology | Yes, compatible with Brompton Ghostframe digital markers |
| Axes tracked | 6DOF + zoom, focus, iris | 6DOF + zoom, focus, iris |
| Positional accuracy* *According to comparison test in a room with markers at 6m height | Depends on the studio and marker height. Typically in range of cm according to tests | Depends on the studio and marker height. Typically in range of cm according to tests. |
| Angular accuracy* *According to comparison test in a room with markers at 6m height | Within 0.1 degrees | Depends on the studio and marker height. Figures pending from comparison test. |
| Min. delay | 0.002 s (0.1 field at 60 fps) | 0.0166 s (1 field, NTSC) |
| Tracking recovery (nominal / max) | < 0.2 s nominal / 0.5 s max | < 1 s nominal (per Mo-Sys spec) |
| Min. markers to track | 4 (8+ recommended) | 8 (20+ well-spaced recommended) |
| Max studio size | 200 x 200 m | 100 x 100 m |
| Max studio size with floor markers | 10,000 m² (floor markers) | Not specified in Mo-Sys documentation |
| Max ceiling height | 40+ m | 16+ m |
| Protocol | FreeD, StypeHF, EEVEC | Mo-Sys F4, FreeD |
| Tri-Level, BnB genlock | Yes | Yes |
| SMPTE ST 2059 (ST 2110) genlock | Yes | Not listed in Mo-Sys documentation |
| High-speed recording | Up to 250 fps output | Up to 180 fps output |
| Lens encoder ranges | Absolute, no reset on power-on | Relative, set min/max each power-on |
| PoE remote processing unit | Yes, rack-room deployment supported | No, processor unit mounts on or near camera |
| Processing unit required | Optional for mobile setups | Integrated (no separate PC needed) |
| Server-grade / ECC RAM | Yes, 24/7 operation | No |
| Web-based management UI | Yes, RedSpy Control Center | Yes, web UI via PC, phone, or tablet |
| Engine integration | Unreal, Unity, Disguise, Notch, + others | Unreal (VP Pro plugin); FreeD/F4 for others |
| Weight on camera | 311 g (sensor only; processor in rack or portable box) | 700 g total: 250 g sensor unit + 450 g processor unit (two separate units, cable-connected) |
| Re-calibration | Automatic, no daily recalibration needed | Autonomous, no daily recalibration needed |
| Drift accumulation | None | None |
| Data recording | FBX, XML, JSON | FBX via VP Pro plugin (Unreal, active license required) |
| Wireless option | Yes, 50 m indoors / 150 m outdoors | Not specified |
Both RedSpy and StarTracker Max use retroreflective markers placed in the environment, which the infrared camera detects to compute position and orientation. Both support ceiling, wall, and floor mounting. Both create a map on first setup that is then reused indefinitely.
RedSpy is engineered for both indoor and outdoor use. Its retroreflective markers work in natural daylight and the system is robust to changing light conditions. It has been proven on live sports, outdoor broadcasts in bright sun, Steadicam rigs, helicopter, drone, and cable cam setups. StarTracker Max is designed primarily for indoor environments, and Mo-Sys does not publish outdoor deployment examples.
RedSpy delivers a minimum delay of 2 ms (0.1 fields at 60 fps) versus 16.6 ms (1 field, NTSC) for StarTracker Max, per Mo-Sys’s own published spec. After a tracking loss event, RedSpy recovers in under 0.2 s nominally and 0.5 s at worst. StarTracker Max recovers in under 1 s nominally per Mo-Sys’s published specification.
Both systems are two-part: a camera-mounted sensor and a separate processing unit.
StarTracker Max’s sensor unit weighs 250 g and its processor unit weighs 450 g (700 g combined). Per Mo-Sys, the sensor mounts on a bracket or directly to the processor unit, and the processor unit is designed to mount on or very close to the camera, connected to the sensor by cable.
RedSpy’s sensor weighs 311 g and is the only part that needs to be on the camera, connecting to the processing box via ethernet. RedSpy’s processing box comes in two forms: (i) PRO, a rack-mounted, server-grade box with ECC RAM for 24/7 operation, and (ii) PORTABLE, a smaller box that can mount on a camera similarly to StarTracker Max’s processor unit.
For jibs, Steadicam, and handheld work, a lighter on-camera rig, where the processing box sits further away or in a rack room, is meaningful.
StarTracker Max‘s sensor unit is rectangular (4 x 4 x 9 cm, 250 g per Mo-Sys), with 12 LEDs and openings in the housing for ventilation.
RedSpy‘s camera and sensor unit is cylindrical (6.2 cm diameter x 9 cm height, 322 g), fully closed, with 45 LEDs and fully passive cooling. The closed housing keeps dust from accumulating inside the unit, which extends its operating lifespan compared to a vented design.
RedSpy mounts to a rig through a standard 1/4″-20 UNC thread on the bottom of the camera, listed as .315″ (8 mm) deep. A small locating pin hole next to the thread (2 mm deep) keeps the camera from rotating once mounted. Two screw types are used across stYpe’s mounting hardware, both 1/4″-20 UNC x 1/2″ (12.7 mm):
If you are considering a transition, here is what changes and what stays the same.
No. RedSpy is a marker-based optical tracking system. It uses retroreflective markers placed in the environment on ceilings, walls, or floors, which the infrared camera detects to compute camera position and orientation. Mo-Sys StarTracker Max is also marker-based, using retroreflective stars.
Yes. RedSpy is also engineered for outdoor use. Its retroreflective markers set on the floor work in natural daylight, and the system is robust to changing light conditions. It has been proven on live sports, outdoor broadcasts, and mixed daylight environments.
Both systems deliver sub-pixel optical tracking accuracy. In controlled studio conditions the precision is comparable. The real difference is in production context: RedSpy holds accuracy across lighting changes and outdoor environments, while StarTracker is optimized for a controlled indoor space with its marker grid intact.
Both systems require an initial marker placement and map creation when first deployed to a space, which takes several hours. Once in place, the same map is reused indefinitely and the systems lock in place within seconds after power-on.
Yes. RedSpy supports Canon and Fujinon internal serial encoders as well as external zoom and focus encoders for lenses without internal readout. Encoder ranges are absolute, so there is no need to reset min/max values at each power-on. Lens calibration data built for any optical tracking system can be ported over with minimal rework.
Both systems work well with LED volumes. StarTracker Max is compatible with Brompton Ghostframe digital markers on the wall. RedSpy also supports its own patented pierced markers on the LED wall.
Yes. RedSpy supports SMPTE ST 2059 genlock, making it compatible with ST 2110 IP production workflows. Mo-Sys documentation does not list ST 2059 genlock support for StarTracker Max.
RedSpy recovers from tracking loss in under 0.2 seconds nominally and 0.5 seconds at worst. For situations where markers are temporarily out of view, under set elements, through tight interiors, or in unprepared areas, the optional Watcher X add-on provides an auxiliary image-based sensor to maintain stable tracking continuity.
Book a demo with our deployment team. We will set RedSpy up in your studio or on location and show you the calibration, tracking, and engine integration end-to-end.