The RED Komodo does not ship with a native BNC genlock port. That single omission reshapes the entire synchronization workflow for any LED volume deployment.
The fix is not a firmware toggle. It is a three-part discipline: an external hardware interface for tri-level sync, a matched shutter angle to LED refresh rate pair, and a processor that acts as the master clock. Each piece has measurable tolerances. Exceed any one and the wall tears.
The Komodo does not have a "Sync 4" menu. It has a 9-pin EXT port, an optional Expander Module, and a shutter angle dial — those are the sync interfaces.
The Reality of Komodo Synchronization in Virtual Production
LED volumes run on a fixed refresh rate — typically 23.976, 24, 29.97, 30, 59.94, or 60 Hz, depending on the panel and processor. The camera sensor exposes frames at a rate dictated by its recording format. When the two clocks drift out of phase, the sensor samples the wall at inconsistent points in the panel's refresh cycle. The result: visible scan lines, partial-frame brightness shifts, and banding that contaminates the plate.
This is not a color science issue. It is a clock alignment problem. The Komodo compounds it because the camera body itself offers no tri-level sync or black burst input. Most cinema cameras in this price bracket ship with at least one BNC sync port. The Komodo ships with none.
The practical effect is straightforward: any LED volume operator using a Komodo must source sync externally. That means an Expander Module, a third-party sync interface, or a workaround through the EXT port. Without one of these in the signal path, the camera free-runs on its internal timecode and drifts relative to the wall within seconds.
Three variables determine whether the sync holds:
1. Source clock authority — which device in the chain is the master.
2. Phase relationship — whether the camera sensor read-out starts on a known point in the wall's refresh cycle.
3. Tolerance bandwidth — how much drift the system absorbs before artifacts appear.
The Komodo can satisfy all three, but only when the chain is built deliberately. Frame-accurate precision in this domain carries the same penalty structure as other high-stakes timing workflows — a discipline that the desks at grumarket understand intimately when evaluating commodities and futures contracts against fixed delivery tolerances. The physics differ entirely. The tolerance math does not.
Hardware Requirements: Bridging the Genlock Gap
The Komodo's body has no genlock BNC. To inject tri-level sync or black burst, crews must add one of three hardware layers.
Option 1: RED Komodo Expander Module. This is the manufacturer-recommended path. The Expander adds a full-size SDI cluster, control ports, audio breakouts, and a sync input path that routes tri-level and timecode through the camera's internal sync block. When the Expander is mounted, the Komodo can lock to an external reference. The Expander is not optional in a serious virtual production rig — it is the baseline.
Option 2: Third-party sync interfaces. Devices such as the Ambient Lockit, Timecode Systems:pulse, or Denecke SB-T accept tri-level or black burst and convert it into a signal the Komodo can ingest through the EXT port. These add latency, typically in the 1–3 frame range, which must be absorbed into the wall's phase delay. Cheaper adapters add more. The tolerance here is narrow — a one-frame mismatch with a 24 Hz wall is 41.7 ms of skew, more than enough to break a composite.
Option 3: Direct EXT port injection. The Komodo's 9-pin EXT port carries GPIO and sync signals. Tapping into this port for tri-level sync is possible but undocumented at the firmware level for most builds. This is a fallback, not a primary workflow.
The Expander Module is the default choice for a reason. It is the only path where RED's firmware officially recognizes the sync source and phase-locks the sensor accordingly. Third-party converters work in many cases but introduce latency that must be measured and compensated, not assumed.
Mastering Shutter Phase and LED Refresh Rate Alignment
Genlock alone does not eliminate scan lines. The Komodo's shutter angle and the LED wall's refresh rate must match within the sensor's exposure window. The standard motion picture shutter angle of 180° is the default starting point, but it is not a universal fix.
Consider a 60 Hz wall running at 29.97 fps with a 180° shutter. The exposure window is roughly 16.67 ms. The wall refreshes every 16.67 ms. These numbers align, but only if the camera sensor read-out starts at the top of the wall's refresh cycle. If it starts mid-cycle, the sensor samples across two refresh windows, and banding appears.
The mitigation is procedural:
- Set the LED processor as the master clock.
- Feed its tri-level or genlock output to the Komodo Expander.
- Configure the Komodo to slave to that reference.
- Adjust the wall's output delay in the processor (typically a frame or sub-frame delay) until the camera sensor read-out coincides with the start of the wall's refresh.
Most LED processors — Brompton, Megapixel, ROE Visual — expose this delay in milliseconds or frames. The Komodo operator has no native control over the wall side; the DIT or virtual production supervisor adjusts the processor to match the camera, not the reverse.
Refresh rate pairing matters. A 23.976 fps Komodo on a 60 Hz wall works, but the non-integer ratio creates a visible beat frequency if phase is not perfectly aligned. A 24 fps Komodo on a 48 Hz wall pairs cleanly. The pairing matrix below summarizes the most common production combinations:
| Komodo FPS | Wall Refresh | Sync Source | Phase Tolerance |
|---|---|---|---|
| 23.976 | 48 Hz | Expander + tri-level | Clean 2:1 ratio, low beat frequency |
| 24.000 | 48 Hz | Expander + tri-level | Integer ratio, preferred for cinema |
| 29.97 | 60 Hz | Expander + tri-level | Standard broadcast pairing |
| 30.00 | 60 Hz | Expander + tri-level | Integer ratio |
| 59.94 | 60 Hz | Expander + tri-level | Near-1:1, tightest tolerance window |
| 60.00 | 60 Hz | Expander + tri-level | 1:1, demands sub-millisecond alignment |
Choose the closest integer multiple whenever the wall supports it. Non-integer pairings can be made to work, but they leave less margin for tolerance drift during a long shoot day.
Configuring the EXT Port for External Sync Signals
The Komodo's 9-pin EXT port is not a genlock port. RED markets it as a GPIO and 3D Sync interface — distinct functions. Treating it as a substitute for a BNC genlock input is a common mistake that produces stable-looking but phase-incorrect results.
The port does carry sync signals. Specifically:
- GPIO inputs and outputs for trigger and tally.
- 3D Sync for stereoscopic camera pairing, where one Komodo acts as master and another as slave.
- Timecode input and output on designated pins.
Routing tri-level sync through the EXT port is documented for 3D setups, not for LED wall phase alignment. Using 3D Sync as a workaround for genlock will lock two cameras together, but it will not phase-lock either camera to the wall. That distinction is the source of most "the wall still tears" troubleshooting tickets.
The correct workflow:
1. Use the Expander Module for wall sync.
2. Reserve the EXT port for 3D stereo or GPIO triggers.
3. Do not cross the two.
Pinout documentation for the EXT port is available from RED support, but the practical takeaway is structural: the EXT port is a control interface, not a primary sync interface. Crews that wire tri-level through it are working against the camera's design and will see artifacts that look like sync failures but are actually phase failures.
Sync the camera to the wall through the Expander. Use the EXT port for triggers and stereo pairing. Cross those two roles and the wall will not hold phase.
Firmware Best Practices for Stable Timecode and Sync
The Komodo's sync behavior has changed across firmware versions. Early builds had documented drift in timecode holdover when the reference signal was intermittent. Current firmware versions released through 2024 for the DSMC3/Komodo ecosystem address most of these issues, but only when the camera is updated to the latest stable release.
Three firmware rules apply:
- Run the latest stable firmware on both the Komodo body and the Expander Module. Mismatched firmware versions between the two introduce sync negotiation errors that read as random banding on the wall.
- Enable "Free Run" timecode mode only when the camera is locked to an external reference. In free run with no reference, the camera drifts relative to the wall within minutes. The drift is sub-frame at first — invisible on the monitor, fatal in comp.
- Verify timecode stability with a downstream waveform or scope. Timecode counters in the monitor output can read stable while the underlying clock drifts by sub-frame amounts. A scope trace of the genlock input reveals what the on-screen counter hides.
RED's release notes for recent firmware versions explicitly call out timecode stability improvements. This is not marketing language. It is a measurable change. Operators running older firmware on a multi-camera LED volume regularly see drift that disappears after a firmware update — and reappears if the firmware is rolled back.
The Bottom Line
The RED Komodo can be synchronized to an LED volume. It cannot be synchronized from the camera body alone. The chain that works:
- Komodo running current stable firmware.
- Expander Module mounted and on matching firmware.
- LED processor designated as master clock.
- Tri-level or genlock fed from processor to Expander.
- Shutter angle set to 180° or matched to the wall's refresh cycle.
- Wall output delay tuned by the VP supervisor until banding disappears.
There is no "Sync 4" toggle inside the Komodo. There is a discipline that spans the camera, the Expander, and the wall processor. Run that discipline correctly and the wall holds. Skip any one step and the artifacts return.
For crews troubleshooting persistent scan lines on a Komodo-based volume: the answer is rarely in the camera menu. It is in the Expander Module seating, the firmware version match, the shutter-to-refresh phase alignment, and the processor's clock authority — in that order. Fix the chain, not the camera.
