Multicameraframe Mode Motion Fixed Full -

Synchronised Triggering: All cameras in the array capture frames at the exact same microsecond, ensuring that a fast-moving object is in the same relative position across all views.

Full Resolution Processing: Unlike "sub-stream" modes that lower quality to save bandwidth, "Full" mode maintains the maximum native resolution and frame rate for every individual camera sensor.

Temporal Consistency: It eliminates the "jelly effect" or rolling shutter issues by prioritising high shutter speeds across the entire multi-camera frame. Common Use Cases

360° VR & Panoramic Stitching: Capturing high-speed action (like a sports car or a bird in flight) where the subject moves across the boundaries of different lenses. multicameraframe mode motion full

Industrial Inspection: Monitoring high-speed assembly lines where multiple angles are needed to check for defects in real-time.

Biometric Tracking: Advanced security systems that use multiple angles to reconstruct a 3D "skeleton" of a person's movement for gait analysis. Technical Requirements To run this mode effectively, your system usually requires:

High-Bandwidth Interface: Such as 10GbE (Ethernet), Camera Link, or CoaXPress to handle the massive data load. Synchronised Triggering : All cameras in the array

Hardware Clock Sync: Systems like IEEE 1588 (PTP) to keep the internal clocks of all cameras aligned.

Sufficient Storage I/O: High-speed NVMe storage capable of writing multiple "Full" streams simultaneously without buffering.

This guide explains what the mode does, when to use it, and how to configure it for optimal results. Battery life or storage is critical (it consumes

2. When to Use Motion Full Mode

| Use Case | Why Motion Full | |----------|----------------| | Sports replay (multi-angle) | Every angle shows the exact same moment in time for freeze-frames. | | VR/180° stereoscopic | Left/right eye frames must match within <1ms. | | Markerless motion capture | Skeletal tracking needs simultaneous views. | | Broadcast switching | Seamless cuts between cameras without temporal mismatch. | | Autonomous driving testbeds | Sensor fusion requires frame-accurate sync. |

Avoid Motion Full when:

• Battery life or storage is critical (it consumes 2–4× more than staggered modes).
• You only need one active camera at a time (use single-camera mode).

Performance and quality trade-offs

• Higher N frames → better SNR and detail but greater misalignment risk and latency.
• More aggressive motion compensation → fewer motion artifacts but higher hallucination risk (over-warping).
• Depth-based methods handle parallax but require depth accuracy.
• Neural methods yield superior quality but need training data and may hallucinate fine detail.

The Core Mechanics

In MCFM, all cameras share a synchronized timecode (ideally genlocked) but capture different spatial perspectives of a moving subject. The "Frame Mode" refers to keeping each camera’s focal length and sensor crop identical. "Motion" refers to either:

1. Subject moves through a static array (e.g., a fighter punching through a 5-camera arc).
2. Camera array moves past a static subject (e.g., a dolly track with 3 side-by-side cameras).
3. Both move (the hardest; requires motion-control rigs).

On Professional Cinema Cameras (RED/Sony)

1. Set project FPS to 120fps (minimum for motion full).
2. In Multi-Cam Sync menu, select “Genlock Internal”.
3. Turn off “Smart Crop” (critical – Smart Crop sacrifices “Full”).
4. Set “Depth Mode” to “Maximum Motion Vectors.”