When Your Orbitify Multi-Camera Setup Splits Timecodes Across Different Partitions

So you set up your Orbitify rig—three cameras, maybe four, all ready to roll. You hit record, shoot for an hour, and when you pull the cards, the timecodes don't match. Not even close. One camera thinks it started at 01:00:00:00, another at 01:00:05:12, and a third might be on a completely different frame count. You check the files: they're on different partitions, maybe different drives. And now you're stuck splicing clips with no common reference. Sound familiar?

This isn't just a glitch. It's a workflow problem that happens when timecode sync breaks across partitions, often because of how Orbitify handles start times or how your cameras record flags. But it's fixable. In this article, we'll cover exactly how to prevent it, and what to do when it's already broken. No theory—just steps.

Who Actually Hits This Mess?

When timecode drift ruins your cut

You've got six camera angles from a two-day interview shoot. The director wants the A-roll synced across all bodies before the editor starts. Should be simple — except the footage from Day 1 lives on one SSD partition, Day 2 on another, and somewhere in between the timecode numbers decided to take a vacation from each other. I've sat in edit bays where the assistant is manually sliding clips frame by frame, muttering about "partition boundaries" like they're cursed geography. That's who hits this mess: anyone splitting a multi-camera project across physical drives, card slots, or folder structures that the camera workflow software treats as separate universes.

The concrete consequence? You lose half a day minimum. Not hyperbolic — I've watched a three-hour wedding edit stretch into fourteen because the Sony FX6 on partition A thought it was 14:02:03:12 while the Canon C300 Mark III on partition B insisted on 14:02:03:11. One frame off per hour of recording. That sounds minor until your multicam group has thirty clips and every single cut point bleeds by a frame. The seam blows out. Dissolves jitter. The producer asks why the handshake looks sloppy — and you can't answer "because the partition split the timecodes" without sounding like you're making excuses for bad prep.

The partition problem explained

Here's the dirty secret: partitions aren't just storage boundaries — they're timecode graveyards. Most pro cameras embed timecode as metadata, but the moment you offload to a partitioned card or split media across two internal drives during a long shoot, the camera or ingest software often resets the clock reference. Not every time, not obviously. Sometimes it's a single frame offset. Sometimes it's a whole second. The odd part is — the camera's display shows seamless timecode. Only when you import into an NLE and line up waveforms do you discover the partition introduced a fracture.

Real shoot scenario: four-camera concert capture. Cameras A and B record to the same SSD's partition 1. Cameras C and D fill partition 2 mid-show when partition 1 maxes out. Nobody stops to check if the timecode generator on Camera C stayed locked after the partition swap. It didn't. The editor pulls in the footage, groups by timecode, and gets a multicam cluster where Camera C is 14 frames ahead by the third song. That's not a sync error you fix with a slip edit — that's a rebuild of the entire timeline group. Wrong order. Huge pain.

'We thought the timecode was jam-synced on set. Turned out the partition swap broke the drift compensation. Cost us a full day of conform.'

— Senior assistant editor, unscripted television, 2024

Real shoot scenarios that trigger it

How do you actually land in this situation? Three patterns I see repeatedly. First: the hot-swap disaster. A documentary crew shooting vérité fills a 256GB card on partition one, swaps to partition two mid-interview because nobody formatted the second card slot. Timecode was jammed to the same source, but the camera's internal clock drifted during the swap — and the new partition doesn't inherit the running timecode. Second: the multi-day offload problem. Day one footage goes to partition A on the RAID. Day two lands on partition B because someone reorganized folders. Both days were shot with identical timecode settings, but the ingest software treated each partition as a separate "project" and reset the origin.

Not every film checklist earns its ink.

Not every film checklist earns its ink.

The third pattern is the one that stings most: shoot-and-ship. A producer hands you a drive with three partitions — each labeled for a different scene — and says "all synced." You open partition one: fine. Partition two: 1.5 frames off. Partition three: somehow running backward? The catch is — the timecode was jammed once at camera prep, but the partition boundaries on the drive forced the DIT to restart the camera's timecode generator between media swaps. Nobody caught it because the camera's internal clock looked continuous. That hurts. The fix involves pulling original camera files, comparing time-of-day metadata, and rebuilding the sync map manually. Not a five-minute job.

Most teams skip this: they assume a jam sync at the start of the day protects every partition. It doesn't. Partitions fragment the continuity that timecode needs to stay linear. If your workflow splits media across folder structures, card slots, or drive volumes mid-shoot, you're gambling that every partition inherits the same clock pulse. One frame off per hour. Over a twelve-hour shoot that's twelve frames. Enough to make a talking head look like they're mouthing the words wrong. Fix it before the editor sees it — or budget for the overtime.

What You Need to Settle Before Starting

Camera timecode checklist — the non-negotiables

Before you touch a single file partition, every camera body in your rig must agree on how it measures time. That sounds trivial until you find one body set to Rec Run while the other is on Free Run — the offsets drift before you've rolled a single take. Every camera needs: the same frame rate (23.976 ≠ 24, and yes, that mismatch will destroy your multi-cam group), the same timecode mode (Free Run jammed from a master or Tentacle), and the same user bit settings if you're embedding reel IDs. I have watched a four-camera sitcom shoot spend forty-five minutes re-syncing in post because one operator had inadvertently left their camera on Drop Frame while the others ran Non-Drop — the timeline looked fine for two minutes, then the gap opened like a slow leak. The catch is: camera menus bury these settings differently. Sony Venice calls it 'Timecode Preset'; RED uses 'Timecode Mode'; Canon C-series hides it under 'Display Setup'. Print the menu path for each model and tape it to the monitor stand. You'll thank yourself when the DP yells 'speeds' and nobody is scrambling.

Orbitify firmware and app version — why it matters

Orbitify pushes updates roughly every six weeks. The version you installed in March may not support the partition-aware sync logic that shipped in July. Check two things before you start: the camera node firmware (found under System > About on each Orbitify unit) and the mobile/desktop app build number. A mismatch between node and app versions often produces silent failures — the app shows green checkmarks, but the timecode metadata written to QuickTime files is a few frames off. That hurts. I've debugged a project where the director's monitor displayed perfect sync while the recorded proxies had a ten-frame offset; the culprit was a node stuck on v2.4 while the controller ran v2.6. The fix? Downgrade the controller or flash the nodes — either way, don't assume backward compatibility. Orbitify's changelog is explicit about 'container integrity fixes' in recent builds. Read it. One more thing: the app's 'Auto-Sync Partitions' toggle appears only in v2.8+. If you see it grayed out, you're on an older release. Don't proceed until that toggle is active and tested.

Storage and partition layout prep

This is where most teams skip the boring step and pay for it later. Each camera records to a separate card or SSD — those are your partitions. Before the shoot: label every card with a unique Camera ID (A1, A2, B1, B2) and a session number. Orbitify reads the partition name at ingest; if two cards are both named 'Untitled', the software can't map timecode sources correctly. The result? Orphaned clips that sync to the wrong camera track. Format each partition using the camera's own format utility, not a computer — cross-formatted exFAT cards sometimes strip the system volume name that Orbitify relies on. Also: leave at least 15% free space per partition. When a card fills during a long take, Orbitify's sync engine skips the final file segment rather than splitting it. That means the last few seconds of your best performance might land in a 'partial' folder with no timecode anchor. Test this edge case on a dummy run: fill a card to 85%, record a three-minute take, then watch what the ingest report says. If it flags a truncated file, you know you need bigger cards or more frequent swaps. Not exciting, but losing a take because of partition math is embarrassing.

'We formatted all SSDs in-camera, labeled every partition with a Sharpie, and the sync just worked for twelve straight weeks on a Netflix docuseries. The days we forgot? We spent the next morning re-jamming proxies.'

— Post supervisor for a three-camera vérité shoot, speaking at a HPA tech retreat

Rhetorical question: would you rather spend ten minutes prepping partition labels or four hours reassigning sync groups in DaVinci Resolve? Exactly.

Step-by-Step: Syncing Timecodes Across Partitions

Setting a Common Jam Sync Source

You can't fix what you never established. Before any camera rolls, pick one master clock — a Tentacle Sync E, a Denecke SB-4, or even a clean camera with known-good internal TC. Jam every unit to that source simultaneously. Walk the rig: camera A, camera B, any GoPro or mirrorless body you're sneaking into the rig. I have seen crews jam seven cameras in sequence and still miss the drone's internal clock — that mismatch alone killed an entire B-roll partition. The catch is that many prosumer cameras jam to time-of-day but ignore frame rate. Check that your master is set to the exact project FPS (23.98, 29.97, whatever). One crew I helped was shooting 23.98 on the master but 24.00 on a Sony FX6 — the drift became visible at minute twelve. Wrong order. Not salvageable without a sync box per partition.

Reality check: name the production owner or stop.

Reality check: name the production owner or stop.

Checking Timecode Continuity per Partition

You've jammed. Now verify. Pull each camera's TC readout against a reference monitor or waveform — does the timecode advance at the same rate? A common pitfall: cameras that drop frames on battery swap or card change. If your partition spans three SSD swaps across a six-hour interview, you'll get gaps. The fix is paranoid but fast: record a two-minute clip on every camera after jamming, then play them back side-by-side in Orbitify. Does the clapper board's snap land on the same frame across all angles? If not, you have a partition-level drift. Most teams skip this step — then wonder why the multicam timeline refuses to align. That hurts.

What usually breaks first is the damn audio recorder. Many field recorders (Zoom F8n, Sound Devices MixPre) run free-running TC even when jammed — they assume you'll pull timecodes later. But Orbitify's sync engine hates discontinuities. If your recorder's TC jumps during a battery hot-swap, the entire partition after that point becomes a guessing game. We fixed this by powering the recorder from a single source across the whole shoot day. Overkill? Maybe. But losing a partition because an AA battery hiccuped is a rookie mistake you make once.

Aligning Clips in Orbitify's Timeline

Now you bring the mess into Orbitify. Import each partition's clips as separate bins — don't merge them yet. Why? Because timecode offsets between partitions often differ by a few frames due to drift. Drag all clips from Partition A onto the timeline, then overlay Partition B. Orbitify's 'Sync by Timecode' tool is your first move — it snaps most clips within a quarter-frame. But here's the trade-off: the tool assumes continuous TC across the entire partition. If a camera stopped recording mid-take and restarted, the tool will shift the rest of that clip by the gap duration. You'll see a split-screen where a hand gesture appears on camera A but camera B shows empty space. The fix is manual: find the TC break point in the metadata (Orbitify shows timecode stamps per clip), split the Partition B clip at that frame, and nudge the second half. Tedious, yes. But faster than re-shooting.

'We jammed five cameras to the same Tentacle. Or so we thought. One had phantom power engaged — the TC chip overheated and drifted a frame every ninety seconds.'

— Remote DP, multi-camera doc shoot, recovered via partition isolation

The last step is grouping. Once all partitions sit aligned on the timeline, select every track and hit 'Create Multicam Clip.' Orbitify will ask if you want to embed the sync relationship or keep it as a reference. Always embed — reference sync dies if you move the project folder. Do a spot-check: scrub through the first five minutes of each partition. If you see a split where one camera's TC lags by two frames, that's a partition boundary issue — your master clock drifted between battery changes on the second partition. You'll either re-jam that partition's clips manually (select all, offset 2 frames) or rebuild from the original sync source. We've done both. Neither is fun. But a timeline that holds sync across four hours of footage? That's the payoff.

Tools and Settings That Make or Break It

Timecode generators: which ones actually work

Not all timecode boxes are created equal — and Orbitify's partition sync is brutally picky. The Tentacle Sync E generation? Solid, provided you update firmware before the shoot. The Denecke SB-4? Works, but only if you hard-set the frame rate to match your project *before* slaving cameras. I have seen crews burn two hours because a DJI Ronin 4D's internal clock drifted against a consumer-grade Lockit box — the partition seams looked fine in dailies but split apart in the timeline by 3 frames. The catch is consumer gear: cheap Amazon timecode adapters often round subframe values differently, and Orbitify treats any discrepancy as a partition boundary. Stick with pro units rated for ≤1 ppm drift at 23.976 fps. That hurts, but the alternative is resyncing 8 camera angles by hand.

— Field note from a multicam music festival shoot, 2024

Orbitify's sync preferences — what the docs skip

Most teams skip this: the 'Sync Tolerance' slider in Orbitify's advanced prefs. Default is 0.5 frames. That sounds fine until you're running mixed framerates across partitions — say, 29.97 on your A-cam and 23.976 on the B-roll rig. Bump tolerance to 1.0 frames or you'll get spurious partition splits at every TC jump. But here's the trade-off: too loose (≥2 frames) and you'll merge genuinely separated takes into one corrupted segment. We fixed this by testing with a known drift: record a clapper at the start of each partition, then check where Orbitify places the split. If the seam lands within 0.3 frames of the clap, leave tolerance at default. If not, adjust in 0.1 increments. And disable 'Auto Partition on TC Reset' — that feature is designed for single-camera runs and will butcher a multi-angled scene.

Odd bit about production: the dull step fails first.

Odd bit about production: the dull step fails first.

Partition formatting and file system quirks

The file system you choose can silently destroy timecode alignment. exFAT on a Samsung T7? Orbitify reads partition boundaries cleanly — but only if the allocation unit size is 128KB or larger. Smaller clusters introduce timestamp rounding errors that look like TC drift. APFS on Mac? Fine for internal SSDs, but external drives formatted as APFS will create hidden metadata partitions that confuse Orbitify's scan. I have seen a shoot lose 40 minutes because a DIT formatted a RAID as NTFS over USB-C — the driver added 2ms latency per file read, desyncing every partition edge by one subframe. Stick to exFAT with 256KB clusters for cross-platform sanity. Or use UDF if you're entirely in the Adobe ecosystem; its block-level timestamps match Orbitify's partition logic precisely. The odd part is — HFS+ still works, but only on macOS 10.14 or older. Not yet tested on modern Ventura builds. That's a pitfall nobody advertises.

When Your Cameras Don't Play Nice: Variations for Different Setups

Mixing brands: Sony vs Canon vs Blackmagic

The moment your camera bag holds more than one logo, the clean partition sync you tested with three identical bodies turns into a negotiation. Sony's timecode implementation, for instance, outputs a clean LTC signal through the multi-terminal—but only if you've dug into the menu and enabled it manually. Canon, in contrast, buries its timecode settings behind a 'Sync Rec' toggle that many operators miss entirely, meaning the camera logs its own drift without telling you. Blackmagic Pocket cameras? They accept timecode via the 3.5mm jack, yet the input impedance can cause a signal drop if your cable run exceeds ten feet. I have seen a six-camera interview shoot where two Sony FX6s locked perfectly, a Canon C70 wandered 14 frames over ninety minutes, and the Blackmagic 6K Pro refused to read the line entirely—turned out the breakout cable was wired for stereo, not mono. The fix is boring but vital: build a cheat sheet per camera model listing exact menu paths and cable specs. That sounds fine until you're swapping cards on a run-and-gun doc and realize the A7S III just rebooted and lost its jam sync.

Consumer cameras without timecode input

You're stuck with a GH6, a Fuji X-H2S, or—heaven forbid—a pocket camcorder that lacks any physical timecode port. Most teams skip this: they assume these cameras can't join the partition workflow at all. Wrong order. You can still sync, but the method flips from jam-sync to acoustic clap-and-pluralize. Record a sharp transient—slate clap, flash pop, or a loud handclap—at the start of every card swap. Then, in post, align the waveform peaks across all clips. The trade-off is brutal: this only works if your audio sample rates match (48kHz across the board, no exceptions) and if nobody forgets to slate. What usually breaks first is a long-take interview where the clap lands during dialog, buried under speech. I have fixed this by having a second person hold a phone running a timecode generator app—Tentacle Sync Studio or MovieSlate—and holding the phone speaker near the consumer camera's built-in mic at every restart. Not elegant. But it gives you a visible spike in the waveform that post can snap to without guessing.

Long takes vs multiple card swaps

The longer your take, the more partition splits hurt—because a single camera's internal clock drifts faster than you think. A thirty-minute continuous interview on a Sony FX3 might drift 0.5 frames; an hour-long lecture on a Canon R5 C can slip 2–3 frames. That's invisible in a single clip, but the moment you split that take across two memory cards—and the camera re-jams its own timecode on boot—the second half may jump by an entire frame or more. The catch: many shooters swap cards precisely because they're shooting long events, so the drift compounds. One concrete fix: before the first card swap, generate a 1kHz tone for three seconds on a field recorder, then keep that recorder running as the common audio reference across the whole shoot. That way, even if each partition's timecode is slightly off, the audio waveform in post aligns them naturally. Another trick—set every camera to record at the same frame rate and time-of-day mode, not free-run. Time-of-day resets to the internal clock on power-up, which is dumb; free-run preserves the jammed timecode across power cycles, which is what you actually need. Most people choose wrong. Don't be most people.

The Stuff That Breaks: Debugging When Nothing Syncs

Timecode gap at partition boundaries

You line everything up, hit record, walk away. Hours later you open the timeline—and there's a hard jump exactly where one memory card ended and the next began. The odd part is: both partitions show clean timecode internally. The break happens between them. Most teams skip checking the camera's file-splitting behavior before the shoot. That hurts. Sony FX6 bodies, for example, often insert a 2–3 frame gap when they wrap a clip and start the next partition—even with continuous timecode fed in. The camera isn't dropping sync; it's just not writing the last few frames of Partition A into the same contiguous stream. You can fix this by locating the last usable frame on partition one, then sliding partition two's first frame backward until your waveform or dual-eye pattern matches. I have seen editors waste half a day trying to stretch or warp clips when the real fix was a simple 2-frame nudge.

Drop frames and how to spot them

Drop frames feel different. The timecode counter keeps ticking, but the picture stutters or audio goes hollow for a few milliseconds. Wrong order. Not a gap—a skip inside a running clip. The usual suspect? Your recorder or camera couldn't sustain the write speed during a partition switch. Cheaper SD cards or nearly-full drives amplify this. Pull the suspect clip into a viewer that shows frame-by-frame timecode values. Look for a jump where the frame number increments by 2 or 3 instead of 1. That's your drop. Orbitify's sync engine will show a red flag on those frames—but only if you've enabled 'detect discontinuity' in the partition settings (it's off by default). We fixed this once by swapping from V60 to V90 cards mid-project. The catch is: you can't re-generate dropped frames. You can only slip adjacent clips to minimize the visible seam, then crossfade over the blip. A 2-frame crossfade hides most of it. Three frames and audiences start feeling queasy.

What to do when Orbitify shows 'No Sync'

This one triggers panic. The software flat-out refuses to align a partition. Not a warning—a dead stop. First thing: check the timecode source on each camera. Did one camera run free-run while another used record-run? That mismatch alone kills sync before you start. I once saw a crew shoot for six hours with one ARRI on time-of-day and two Sonys on record-run. Every partition boundary looked random. The fix was brutal: manual sync by clapper for each segment. If the timecode sources match, the next culprit is a corrupted partition header. Pull the card, re-read it with a utility like Disk Drill or ExFAT repair tools. Often the metadata that Orbitify reads for the starting timecode value gets mangled during a dirty unmount. Re-mount the card cleanly, re-export the timecode log, and try again. Still failing? Strip the audio waveform from each partition manually, load them into Orbitify as 'audio-only reference' tracks, and force a sync by aligning a transient spike—a door slam, a handclap, anything sharp. That workaround gets you 95% there. The last 5% is accepting that some corrupted partitions need to be re-shot or dropped.

'We spent three hours debugging 'No Sync' before finding one camera's battery died mid-clip. The partition was short 14 frames. Orbitify just refused to guess.'

— Post from a multicam rig op on r/edit, 2024

What breaks first is almost never the timecode itself. It's the assumptions you made about how cameras close files. Test those assumptions before the real shoot—record a partition boundary on set, immediately check it in Orbitify, and fix the workflow before you're stuck with a timeline full of red flags. That single habit saves more sync headaches than any tool or setting ever will.