Rode Wireless GO II: Why Timecode Drifts on Long Takes and How the Sync Jack Fixes It

Drift shows up at the tail of the take

Inside the Wireless GO II transmitter, a free-running crystal oscillator governs the sample clock for the internal 48 kHz recording. Consumer-grade oscillators are normally specified in parts per million, a scale that looks harmless until the take runs long. A 20 ppm error over 15 minutes works out to roughly 18 milliseconds, close to half a frame at 25 fps and slightly more than that at 24 fps.

The camera beside it has its own clock. A Blackmagic Pocket Cinema Camera 6K, a mirrorless body, or any other separate recorder runs from its own oscillator, and that oscillator can sit on the other side of its tolerance range. The error between the two files is the relative difference between both devices, so two small tolerances can add up across one uninterrupted clip.

At the start, the files appear locked because the editor has aligned a clap, a slate hit, or the transient of a spoken word. The first few seconds prove only that one point on the audio track matches one point on the picture track. By the end of a long interview, the accumulated clock difference can put the lips ahead of the syllable or behind it.

Short clips disguise the issue because the error stays below a frame. A 20 minute interview exposes it. The opening alignment still looks perfect, yet the last answer carries the result of every second in which the two clocks were running separately.

What the transmitter jack can be made to carry

The transmitter port is a locking 3.5 mm TRS connector. In its standard configuration it accepts a lavalier or an external microphone and passes analogue audio into the unit. When the transmitter is connected over USB-C to the Rode Central desktop application, that port can be reassigned in the transmitter settings.

One assignable function lets the jack carry an external clock reference or a line-level signal that can serve as a shared alignment marker across the devices on set. The point is to give post-production the same event in more than one file, captured by the same rig at the same instant.

A hardware timecode generator such as a Tentacle Sync E can feed a matching signal into the camera and a corresponding reference to the audio chain. With that arrangement, both files carry a common timing reference. A dedicated field recorder such as a Sound Devices MixPre can embed SMPTE timecode in its recorded file; the Wireless GO II recorded file lacks embedded SMPTE timecode. Its sync jack supports a jam reference point, a shared audible or electrical event that post software can resolve to the same instant on both tracks.

Rode Central version 2.0 and later exposes the jack assignment under the transmitter settings. Once written, the setting is stored in the unit firmware, so it survives closing the app and powering the transmitter down. Firmware 2.0.4 was the release that stabilised this behaviour on both transmitters in a dual-channel setup.

A 24 fps take, counted through

Use a 24 fps shoot with a single 22 minute take. If the camera oscillator runs 15 ppm fast and the transmitter oscillator runs 18 ppm slow, the relative drift is 33 ppm. Over 22 minutes, or 1320 seconds, that produces 1320 times 0.000033 seconds of separation, about 43.6 milliseconds.

At 24 fps, one frame lasts 41.7 milliseconds. By the end of that take, the separation has passed a full frame. An editor who synced to the first word will see the audio arrive about a frame late against the picture near the end, and the error continues to grow in a straight line on longer takes.

A jam reference near the head and a second reference near the tail give DaVinci Resolve two known-common points. From those points, Resolve can stretch or compress the audio clip by the needed rate correction, expressed as a measured percentage. The second mark replaces frame nudging with a calculation tied to the actual drift in that file.

Proxy cuts hide the slip until full-resolution playback

During an offline edit in DaVinci Resolve, proxy playback can keep the problem out of sight. Reduced resolution, compressed proxy media, and the latency of scrubbing make sub-frame slip hard to judge. Even a one-frame error can pass unnoticed when the editor is concentrating on story structure, cut points, or interview selects.

The drift often becomes obvious after the timeline is relinked to full-resolution Blackmagic RAW files and played back at the proper frame rate on a calibrated monitor. At that point, a hard consonant near the end of a long answer may land away from the lip closure. Resolve displays the audio waveform against the clip, so the mismatch can be seen as well as heard.

Checking the tail of every long clip during the offline catches the issue earlier. The head of the take has already been aligned, so it naturally looks correct. The far end of the take is where the oscillator difference has had time to accumulate.

A practical check is to move to the last spoken sentence of a 20 minute interview and watch a plosive. If the waveform spike sits a frame away from the visible mouth closure, the two independent clocks have separated across the duration. That finding is more meaningful than another look at the opening clap.

A separate issue can come from an external audio interface in the chain, such as a Focusrite Scarlett feeding another recorder. Buffer latency is measured in milliseconds and behaves as a fixed offset. Correct it once at the head and it remains corrected through the clip. Oscillator drift behaves differently because it scales with clip length, so the two problems need separate diagnosis.

Two reference points bracket the take

A single jam sync at the top of the day fades as a safeguard on consumer hardware because the oscillators keep moving after the jam. Professional timecode boxes re-jam periodically for that reason.

On a Wireless GO II setup, the equivalent discipline is to capture a shared audible reference, such as a sharp clap or slate, at both the head and the tail of any take running past ten minutes. Those two points define the correction across the whole clip, whatever the final duration turns out to be.

Firmware, cables, and settings that survive power cycles

The TRS and TRRS distinction on the sync cable matters. A cable with the wrong wiring can still pass audio while failing to carry the reference signal expected by the reassigned jack. The failure can be silent on set: the recording sounds normal, and the problem appears later as drift that cannot be resolved from the file alone.

Rode specifies the pinout in the Wireless GO II documentation. The SC7 and SC8 cables in Rode’s accessory line follow that pinout. Using the documented wiring keeps the jack function matched to the signal the transmitter has been configured to receive.

Once the jack function is written through Rode Central, the transmitter retains it across power cycles. There is no on-device menu for changing it back. The reassignment lives in firmware and requires the desktop app to reverse. A crew that reformats or resets the units through Rode Central returns the jack to its default audio-input behaviour, so the setting deserves confirmation before a long-take shoot.

When the reference is missing

The awkward case is the shoot already in the card folder: only the transmitter’s internal recording survived, and the set captured no external reference at all. The file carries its own clock history, while the camera clock it drifted against was never logged; post has only manual frame-by-frame correction against the picture.

For a documentary crew planning long uninterrupted interviews, the choice is how much faith to place in the internal recorder when the sync jack is left unwired. The recording may sound clean while its timing evidence is missing from the file.