Markerless Mocap Camera Selection

A source-bounded, camera-agnostic guide to selecting and qualifying cameras for a flexible markerless motion-capture lab.

Provisional Shop Recommendation

For a shop system intended to observe fast whole-body motion and eventually use six to eight cameras, the current evidence supports a two-camera pilot, not an immediate full-rig purchase. The provisional first candidate is the color Teledyne FLIR Blackfly S BFS-U3-16S2C-CS; the Basler ace 2 a2A1920-160ucBAS is the matched alternate. Both are global-shutter industrial cameras with hardware-trigger support and replaceable lenses. The FLIR candidate trades resolution for a higher vendor-specified maximum rate (226 frames per second at 1440 by 1080); the Basler candidate supplies 1920 by 1200 at 160 frames per second.

The distributed eight-camera reference-rig evaluation hypothesis remains the Allied Vision Alvium G5-203 (Alvium G5-203c), with the LUCID Triton2 TRT016S-CC as an Ethernet/PTP challenger. These distributed candidates operate over 5GigE and 2.5GigE Vision with IEEE 1588 PTP synchronization, addressing the cabling and host-controller bottlenecks of high-rate USB topologies across large capture volumes.

The Stereolabs ZED X One GS remains an evaluation candidate for spaces where synchronized GMSL2 cabling is valuable. It is not the default fast-motion choice: its full-resolution mode is 60 frames per second, its 120-frame-per-second mode is binned to 960 by 600, its vendor dual-camera hardware synchronization claim is 15 microseconds, and the complete topology adds capture-card, NVIDIA, fixed-lens, and proprietary-SDK constraints.

This recommendation is deliberately provisional. Camera specifications alone cannot establish pose, joint-angle, or C3D accuracy. A successful two-camera USB pilot does not establish an eight-camera distributed topology, and an attractive camera-body specification does not qualify the complete lab. Buy two cameras for the pilot, measure the whole acquisition chain, and evaluate the distributed Ethernet candidates separately for the full room. In operational terms: buy two cameras for the pilot and make the larger purchase conditional on the recorded qualification evidence.

WarningNo Procurement Approval & Price Scoping

No listed camera is approved for a full deployment. Observed vendor list prices (such as FLIR US list USD 371.00 and Stereolabs store USD 399/424) cover camera body only and do not represent total system cost. Complete system costs remain unavailable until formal quotes include lenses, GPIO/trigger hardware, host controllers, multi-gigabit PoE switches, Cat6A cabling, mounting, lighting, storage, spares, taxes, and shipping. The machine-readable registry defaults procurement to deny.

Governed Evidence

The canonical dataset is the camera evidence registry. Its schema is affinedrift/mocap-camera-evidence-registry/v1, and scripts/verify_mocap_camera_registry.py rejects missing sources, stale reviews, unknown links, cross-camera claims, incomplete purchasing attributes, and any claim that silently turns an engineering inference into an approved fact.

Evidence classes have intentionally different authority:

Evidence Class	What It Can Establish	What It Cannot Establish
vendor_spec	A vendor’s dated statement about its product or SDK	Sustained rig performance or independent accuracy
peer_reviewed_observed	What a cited study observed under its own protocol	Transfer to another camera, task, pose model, or lab
engineering_inference	A transparent design screen or pilot decision	A qualified threshold or procurement approval
unavailable	That the necessary value is not currently authoritative	A value to be silently estimated or substituted

AffineDrift owns this public evidence and explanation only. Tools owns camera, time, frame, calibration, and interchange contracts. UpstreamDrift owns capture orchestration, calibration execution, reconstruction, validation, and operator workflows. This page does not implement or duplicate either runtime.

Candidate Matrix

Candidate	Shutter	Vendor-Specified Video Mode	Synchronization	Optics	Data Path	Camera Body List Price	Current Role
Teledyne FLIR BFS-U3-16S2C-CS	Global	1440 by 1080 at up to 226 frames per second	Hardware or software trigger; action command	CS mount; documented removable C adapter	USB 3.1 Gen 1	USD 371.00 (camera body only; US list)	Preferred fast-motion pilot candidate
Basler a2A1920-160ucBAS	Global	1920 by 1200 at up to 160 frames per second	Hardware trigger; programmable API	C mount	USB 3.0	Quote required (unavailable)	Higher-resolution fast-motion alternate
Stereolabs ZED X One GS	Global	1920 by 1200 at up to 60 fps; 960 by 600 at up to 120 fps	External synchronization; vendor claim within 15 microseconds	Fixed narrow, wide, or fisheye variant	GMSL2 plus capture hardware	USD 399 base / USD 424 wide (camera body only)	Long-cable topology evaluation
Allied Vision Alvium G5-203c	Global	1620 by 1220 at up to 231 frames per second	Hardware trigger; IEEE 1588 PTP; Action Commands	C mount	5GigE (PoE)	Quote required (unavailable)	Distributed reference-rig evaluation hypothesis
LUCID Triton2 TRT016S-CC	Global	1440 by 1080 at up to 226 frames per second	Hardware trigger; IEEE 1588 PTP; Action Commands	C mount	2.5GigE (PoE)	Quote required (unavailable)	Distributed Ethernet/PTP challenger

Primary product evidence is available from:

• FLIR Blackfly S product page and US pricing page
• FLIR technical reference
• Basler product page
• ZED X One product page and Stereolabs Store listing
• Stereolabs Dual-Camera Sync Guide and ZED Box Connectivity Guide
• Allied Vision Alvium G5-203c product page and Technical Documentation
• LUCID Triton2 TRT016S-CC product page and Technical Downloads

These pages were accessed on 2026-08-26 and 2026-08-27. Product pages can change; the registry therefore carries review dates and does not treat a URL as an immutable specification.

Teledyne FLIR Fast-Motion Pilot Candidate

The FLIR candidate leads the two-camera pilot because temporal sampling is the first screen for rapid motion. The vendor lists a global shutter, 226 frames per second at full 1440-by-1080 Bayer output, a CS-mount lens interface, and hardware trigger support. The separate I/O documentation describes the physical input and its propagation specification. None of these statements proves exposure alignment between two assembled cameras, reliable eight-camera streaming, or pose accuracy.

The Spinnaker SDK is a vendor component under a restrictive EULA, not the licensing authority for the open core. A camera adapter must remain optional and satisfy the public Tools camera protocol. Synthetic and prerecorded drivers must continue to work when Spinnaker is absent.

Basler Higher-Resolution Alternate

The Basler candidate offers 2.3 megapixels at 160 frames per second, global shutter, C-mount optics, a hardware-trigger input, and GenICam-facing pylon APIs. Its additional pixels may improve keypoint localization when the person occupies a smaller portion of the image; that possible benefit is an inference to test, not a result. The lower maximum frame rate may be immaterial for some body segments and insufficient for others.

The pylon SDK is also governed by a vendor license. It belongs behind an optional adapter. A commercial release must review the exact pylon license shipped with the chosen SDK version rather than relying on this summary.

Stereolabs Long-Cable Evaluation

The ZED X One GS offers a synchronized, locking GMSL2 topology and fixed lens variants. Stereolabs technical documentation states that dual ZED X One hardware synchronization is accurate to 15 microseconds, and multi-device ZED Box documentation states approximately 15 microseconds. This makes the system interesting where USB cable length and connector reliability dominate. It does not remove the need to measure exposure timing, transport drops, or model latency on the assembled system.

The comparison must preserve mode context. 120 frames per second applies to the 960-by-600 binned mode, while full 1920-by-1200 output is limited to 60 frames per second. A pair is required for ZED SDK stereo or depth features. The SDK and capture topology depend on supported NVIDIA hardware, and their licenses and redistribution terms remain separate review gates.

Allied Vision Distributed Reference-Rig Hypothesis

The Allied Vision Alvium G5-203 (Alvium G5-203c) is the reference-rig hypothesis for an eight-camera distributed capture lab. It pairs a Sony IMX422 global-shutter sensor (1620 by 1220 at up to 231 frames per second) with a 5GBASE-T (5GigE) interface, Power-over-Ethernet (PoE), and hardware IEEE 1588 PTP (Precision Time Protocol) synchronization.

Ethernet transport decouples camera placement from host PC proximity, enabling shielded Cat6A cable runs up to 100 meters without active USB repeaters. PTP synchronization allows microsecond-level clock distribution over the Ethernet switch fabric. However, eight cameras streaming at 5 Gbit/s require dedicated multi-gigabit switch backplanes, multi-port host NICs, and high-performance packet capture drivers to prevent packet drops and buffer overflows.

The Vimba X SDK provides GenICam and GenTL producer support. As with all candidates, the open Tools core must access the camera through an optional adapter, maintaining full independence from proprietary Vimba runtime binaries.

LUCID Triton2 Distributed Ethernet Challenger

The LUCID Triton2 TRT016S-CC provides an Ethernet/PTP challenger for the distributed reference rig. Featuring a Sony IMX296 global-shutter sensor (1440 by 1080 at up to 226 frames per second), it utilizes a 2.5GBASE-T (2.5GigE) interface with PoE and IEEE 1588 PTP support.

The 2.5GigE data path reduces per-camera bandwidth demand compared to 5GigE while maintaining full 226 fps capture, easing switch throughput and host CPU load in an eight-camera configuration. The Arena SDK provides GenICam/GenTL compliance under a proprietary vendor license.

Topology Comparison

Parameter	Two-Camera USB Pilot	Distributed Ethernet Reference Rig	Long-Cable GMSL2 Rig
Representative Models	FLIR BFS-U3-16S2C-CS, Basler a2A1920-160ucBAS	Allied Vision Alvium G5-203c, LUCID Triton2 TRT016S-CC	Stereolabs ZED X One GS
Physical Transport	USB 3.0 / USB 3.1 Gen 1	5GBASE-T / 2.5GBASE-T Ethernet (PoE)	GMSL2 with FAKRA connectors
Max Distance	3–5 meters (passive)	Up to 100 meters (Cat6A)	Up to 15 meters
Synchronization	Direct opto-isolated GPIO trigger lines	IEEE 1588 PTP / Action Commands / GPIO	Hardware sync pin / ZED Link (15 µs claim)
Power Distribution	USB bus power (host controller dependent)	Power-over-Ethernet (802.3af/at switch)	Power over Coax / capture card
Host Interface	Dedicated PCIe USB host controllers	Multi-port 10GbE/5GbE NIC & PoE switch	Deserializer capture card (PCIe / Jetson)
Driver Interface	GenICam / Vendor SDK (Spinnaker, pylon)	GenICam / GenTL (Vimba X, Arena)	Stereolabs SDK / V4L2 kernel driver
Lab Role	Initial fast-motion screening (2 cameras)	Full-room distributed rig (8 cameras)	Fixed-lens long-cable evaluation

Scoped Pricing vs Total System Cost

Observed vendor list prices establish camera-body baseline figures but do not represent total system cost:

• Teledyne FLIR BFS-U3-16S2C-CS: US model table lists the camera body at USD 371.00.
• Stereolabs ZED X One GS: Stereolabs store lists the base camera body at USD 399.00 and wide configured listing at USD 424.00.
• Basler, Allied Vision, LUCID: Official regional list prices were not established in this audit and remain marked unavailable.

A complete mocap lab requires extensive infrastructure beyond the camera body:

1. Optics: High-resolution C/CS-mount lenses with manual focus/aperture locks (USD 150–400 per camera).
2. Synchronization & I/O: Shielded trigger breakout cables, opto-isolated distribution amplifiers, or PTP grandmaster hardware.
3. Cabling: High-flex locking USB cables, Cat6A shielded Ethernet cables, or FAKRA GMSL2 cables.
4. Host & Ingest: Multi-channel PCIe host controllers, multi-Gigabit PoE switches, dedicated NVMe scratch arrays.
5. Mounting & Structure: Rigid wall/truss mounts, vibration dampeners, protective enclosures.
6. Illumination: High-CRI flicker-free LED lighting panels.
7. Spares & Logistics: Cold spares, shipping, regional import tariffs, and taxes.

Complete system cost comparisons remain unavailable until comprehensive, dated bills of materials are quoted for each candidate topology.

Selection Calculations

Temporal Sampling

For a point moving at image speed \(v_{px}\) pixels per second and a camera rate \(f_s\), the nominal inter-frame displacement is

\[ \Delta p = \frac{v_{px}}{f_s}. \tag{1}\]

This equation does not choose a universal frame rate. Measure \(v_{px}\) for the intended body, club, implement, or tool region, then set a task-specific maximum displacement. A body-pose model may tolerate a displacement that is unacceptable for a fast implement. The registry’s 120-frame-per-second pilot screen is therefore provisional.

Motion Blur

If exposure time is \(t_e\), the approximate image-space motion blur is

\[ b_{px} = v_{px} t_e. \tag{2}\]

For a declared blur budget \(b_{max}\), the exposure contract is

\[ t_e \leq \frac{b_{max}}{v_{px}}. \tag{3}\]

A high frame rate does not automatically create a short exposure. Lighting, aperture, gain, sensor response, and flicker determine whether the required exposure is usable. The pilot must record exposure, gain, illumination, and observed blur for every camera.

Raw Payload Screen

An uncompressed payload screen for width \(W\), height \(H\), frame rate \(f_s\), and delivered bit depth \(q\) is

\[ R_{raw} = W H f_s q. \tag{4}\]

At eight delivered bits per pixel, one FLIR stream at the vendor maximum is approximately 2.81 gigabits per second before protocol overhead. One Basler stream is approximately 2.95 gigabits per second. One Allied Vision Alvium G5-203c stream is approximately 3.65 gigabits per second. One LUCID Triton2 stream is approximately 2.81 gigabits per second. Eight such streams would represent 22.5 to 29.2 gigabits per second in aggregate. These are arithmetic screens, not measured network payloads. They demonstrate why distributed Ethernet architectures with dedicated switch infrastructure are required for full eight-camera rigs.

The acquisition contract must measure successful payload, dropped and duplicate frames, buffer occupancy, host-controller/NIC assignment, CPU load, storage write rate, and graceful recovery. A nominal interface bandwidth label is not a per-camera end-to-end guarantee.

Triangulation Geometry

For two calibrated rays separated by angle \(\theta\), depth sensitivity becomes poor as the rays approach parallel. A useful first-order relationship is

\[ \sigma_z \propto \frac{\sigma_{px} z^2}{f B}, \tag{5}\]

where \(\sigma_{px}\) is keypoint uncertainty, \(z\) is working distance, \(f\) is focal length in pixel units, and \(B\) is baseline. This proportionality explains why baseline and resolution matter, but it is not a complete uncertainty model. Wider baselines can also increase occlusion and viewpoint-dependent pose failures. Camera placement must be learned and qualified from observations, residuals, covariance, visibility, ray angles, and task coverage rather than a fixed room diagram.

What the Research Establishes

Nakano and colleagues evaluated five synchronized cameras at 1920 by 1080 and 120 hertz and reported task- and keypoint-dependent markerless error. The paper supports synchronized multi-view capture and explicit error analysis; it does not qualify any industrial camera listed here.

OpenCap demonstrated useful movement analysis from synchronized 720-by-1280 smartphone videos at 60 hertz. It is an important accessible baseline, not evidence that 60 hertz is sufficient for every shop task or that its accuracy transfers to a different camera, detector, skeleton, or calibration pipeline.

Song and colleagues compared markerless and marker-based estimates across eight movements and reported larger differences for some hip quantities, particularly during rapid movement. This reinforces a central rule: qualification is task-, joint-, model-, and protocol-specific.

Two-Camera Pilot Protocol

1. Obtain complete quotes for two FLIR cameras and two comparable Basler cameras. Include matched lenses, locking data cables, isolated trigger distribution, mounts, tripods or structure, lights, host controllers, storage, taxes, shipping, and one spare strategy.
2. Review the exact SDK versions and EULAs. The MIT core must operate without either vendor SDK.
3. Select lenses from the measured capture-volume dimensions. Record field of view, working distance, focus, aperture, and distortion; do not select only by nominal focal length.
4. Bench two matched cameras at the intended resolution, bit depth, frame rate, exposure, and cable length. Measure exposure skew, drift, frame loss, duplicates, jitter, and recovery.
5. Calibrate a real two-camera geometry, retain every observation and solver version, and report residuals, covariance, ray-angle coverage, and movement invalidation.
6. Run the intended pose backend on representative clothing, lighting, occlusion, body sizes, and motions. Keep detector confidence separate from geometric uncertainty.
7. Compare triangulated points and derived joint quantities against a declared reference. Report all unavailable and failed keypoints; never interpolate them silently.
8. Repeat at the worst intended capture-volume locations. Only then decide whether FLIR’s rate or Basler’s resolution is materially better.
9. Add cameras in stages. Re-run synchronization, bandwidth, calibration, visibility, thermal, storage, and pose tests before scaling to an eight-camera distributed topology.

Required Qualification Evidence

The full-rig decision remains blocked until the following evidence exists:

• a dated bill of materials and exact license review;
• a camera capability record from the real driver rather than a product-name switch;
• sustained stream results at every supported camera count and mixed-capability case;
• common-trigger and PTP exposure timing, drift, drop, duplicate, and recovery measurements;
• intrinsic and extrinsic calibration observations, residuals, covariance, and validity state;
• task-volume visibility and ray-angle maps with occlusion and lighting challenges;
• reference comparisons for the actual pose model, skeleton, filtering, and biomechanical outputs;
• C3D export and independent-reader round trips with units, rates, residuals, events, and explicit loss reporting;
• privacy, consent, retention, security, SBOM, and redistribution approval; and
• an exact-version commissioning report that states what the rig cannot measure.

Extension Contract

A new camera does not require a core code change when it satisfies the shared provider protocol. Its adapter must report capabilities such as stream modes, shutter, trigger, clocks, controls, pixel formats, lens metadata, and cancellation. Unsupported functions return typed unsupported outcomes. The lab manifest selects providers and records immutable device identities and settings; the reconstruction code consumes canonical observations and never switches behavior by vendor name.

To add a camera to this public registry, add its dated primary sources, exactly one claim for every purchasing attribute, limitations, review dates, and an explicit adapter state. If price, sync, license, or topology is unknown, record unavailable. The verifier will reject an apparently complete camera assembled from missing or cross-model claims.

Current Limitations

• No candidate has been connected to this workstation under the canonical Tools protocol.
• No physical timing, blur, lighting, field-of-view, pose, triangulation, or C3D test has run.
• Complete system costs remain unavailable until comparable complete regional quotes exist.
• Vendor SDK summaries are not legal opinions.
• The cited studies bound only their own cameras, participants, models, tasks, and protocols.
• This document does not approve human-subject recording, public release, or biomechanical use.

The correct next hardware action is therefore small and reversible: quote the two fast-motion candidates, buy one matched pair after license and host-topology review, and make the pilot earn the larger purchase.