Kai Mallari's Notes'

SOP_Photographer_Handoff

25 min read

A pre-shoot prep guide for photographers working with a DIT on tethered commercial shoots. You know your gear better than anyone. This document is about bridging your setup with the DIT’s workflow so nothing gets lost in the handoff.

Core principle: the DIT is operating your equipment on your shoot. The smoother the handoff, the more time everyone spends making images instead of troubleshooting.

This is the photographer’s counterpart to three DIT SOPs. The DIT follows SOP_DIT_Pro, SOP_DIT_Studio, or SOP_DIT_Wired_Only depending on your Capture One subscription tier. What’s in this document covers the things that, if they’re not sorted ahead of time, turn into on-set delays — admin passwords, macOS permissions, drive formats, cable compatibility.

Intent

The DIT walks in and operates equipment they don’t own. When something like a macOS permission, a drive format, or a tether setting isn’t right, it’s fixable — but the DIT is locked behind dependencies they can’t control (your admin password, your camera body, your subscription). Sorting it out on set is possible, but it’s slower, more complicated, and it’s happening with crew on the clock. This prep exists so that when the DIT opens your laptop on set, everything just works. First attempt.

Use When

  • You’re the photographer on a tethered commercial shoot and someone else is running your Capture One station
  • There’s a client, art director, or creative team who will be viewing images at video village
  • You’ll be handing off files to a client or post-production team after the shoot

Not for: Untethered shoots where images are reviewed after the fact. Not for shoots where you’re also the DIT. Not for rental equipment that arrives pre-configured.

Why This Matters

Most of these aren’t things photographers do wrong — they’re things that nobody thinks about until they go sideways on set. The DIT has seen all of them.

What happens without the prep conversationWhat happens with it
macOS blocks Capture Pilot on set and nobody has the admin password handy — 30 minutes of crew standby while everyone figures it outPermissions are set at home. Capture Pilot connects first try
Capture One updates overnight, changes tethering behavior, and there’s no rollback available on shoot morningSoftware version is frozen after a successful test. No surprises
Client gets an APFS drive and they’re on Windows — they can’t open it without downloading extra softwareHandoff drives are exFAT. Works on both platforms out of the box
Camera is in mass storage mode and Capture One can’t control itCamera is already set to PTP. Tethering works immediately
Tether cable fails mid-shoot with no spare — the shoot stopsTwo cables, both tested. Swap takes 30 seconds
Cable disconnects under tension and the camera’s USB port takes the hitStrain relief is on. Cable discipline is part of the workflow

Baseline: a photographer who shows up with the right equipment but hasn’t had the chance to systematically verify that every piece is configured and tested for tethered operation. That’s most photographers — this isn’t about doing something wrong, it’s about catching the stuff that only surfaces when everything runs together.

The 6-Step Pre-Shoot Setup

InputsYour laptop with Capture One installed, your camera body, tether cable(s), USB-C to HDMI adapter, HDMI cable, external monitor (or TV for testing), dedicated portable router, Ethernet cable, iPad(s) with Capture Pilot and/or Live for Studio installed, external SSD for handoff, overlay files from the art director, strain relief hardware.

Step 1: Capture One license and version confirmed

This one is straightforward but it sets everything else up. The DIT’s entire SOP depends on whether you’re on Pro or Studio — different tiers unlock different tools on their end.

  1. Open Capture One. The title bar shows “Capture One Pro” or “Capture One Studio.” Let the DIT know which one you have. It changes their whole approach.
  2. Confirm your license is active and won’t expire during the shoot period. Capture One > About Capture One (or check your account at captureone.com).
  3. Verify tethering works with your camera on this version: connect the camera, shoot a few frames, confirm images arrive without delays or errors.
  4. If using Capture Pilot: confirm the iPad app connects and shows images. If using Live for Studio (Studio tier only): confirm the iPad app is version 1.4.0 or later (required for Capture One 16.7+).
  5. Once it works — leave it. Don’t update Capture One or the iPad apps after this verification. Updates can change tethering behavior in ways that aren’t obvious until you’re on set.

Step 2: macOS configured for tethered shooting

This is the one that catches people. macOS has a handful of privacy and security settings that silently block the tools the DIT needs — and they all require your admin password. These are all fixable on set, but the DIT is locked behind your admin credentials, so it turns into a back-and-forth that eats setup time.

None of these are things your Mac is doing wrong. They’re privacy protections doing exactly what they’re designed to do. We just need to tell macOS that Capture One is allowed to talk to the network.

  1. Local Network — must be ON for Capture One, or Capture Pilot silently fails to connect
  2. Firewall — Capture One must be in the allow list for incoming connections, or wireless features won’t work (no error message — it just silently fails)
  3. Screen Recording — needed if the DIT uses a window manager (Rectangle, BetterTouchTool) to pin the Viewer window
  4. Automatic Updates — all toggles off during the shoot period. Re-enable after
  5. Spotlight — capture folder excluded, or CPU spikes every time a new RAW lands
  6. Stage Manager — off, or it pulls the Viewer window off the external monitor when the DIT switches apps
  7. Energy/Sleep — never sleep when plugged in, or the display arrangement breaks on wake
  8. iCloud — capture folder excluded from Desktop & Documents sync, or every RAW queues for upload
  9. Time Machine — capture folder excluded, or it competes for disk I/O during capture
  10. Antivirus — capture folder excluded from real-time scanning (CrowdStrike, Sophos, Norton, Malwarebytes add 100-500ms per file)

On macOS updates: If tethering works on your current macOS version, that’s great — don’t update within two weeks of a shoot. Sonoma 14.2 broke camera connectivity. Sequoia introduced intermittent tethering slowdowns. These things get patched eventually, but you don’t want to be the one discovering the bug on a shoot day.

Step 3: Storage prepared (exFAT for handoff)

This one is about what happens after the shoot. If the client uses Windows and you hand them a Mac-formatted drive, they can’t read it without extra software. That’s an awkward conversation nobody wants to have at wrap.

  1. Confirm sufficient free space on your capture destination (internal drive or external SSD). A full shoot can generate 50-200 GB+ of RAW files.
  2. If using an external SSD as the capture destination: format it exFAT. Not APFS, not Mac OS Extended, not FAT32. exFAT is natively readable on both Mac and Windows — no third-party software needed.
  3. If the capture destination is the internal drive (which is APFS), prepare a separate exFAT-formatted external drive for client handoff.
  4. Test the handoff drive: connect it, confirm it mounts and is writable. Copy a file to it and back.
  5. Format drives well before the shoot day — formatting erases everything.

Step 4: Camera configured for tethering

You know your camera. These are just the settings that specifically affect how Capture One talks to it over USB.

  1. USB communication mode: Set to PTP (Picture Transfer Protocol), not mass storage. Mass storage mode blocks Capture One from controlling the camera or receiving images in real time. Different brands label this differently — see the callout below for your brand.
  1. Dual card slot configuration: If your camera has two card slots, set one to back up to the card while tethering. Worth discussing the specific config with the DIT — some photographers want the card as a safety net, others want to maximize write speed.
  2. Disable auto power-off / sleep. A camera that sleeps during a pause kills the tether connection. The DIT has to wake the camera and re-establish it, which sometimes means unplugging and replugging the cable.
  3. White balance: Use consistent white balance throughout a look — either a custom preset or a specific Kelvin value. When WB shifts between frames, every image the DIT touches starts at a different colour baseline, which makes their adjustments inconsistent across the set.
  4. Camera Firmware: Do not update camera firmware within 2 weeks of a shoot. Firmware updates can break tethering compatibility with Capture One. If the firmware was recently updated, test tethering before the shoot day. → Firmware Known Issues

△ Confirm: Agree with the DIT on file naming convention before the shoot. Consistent naming prevents confusion when sorting files later.

△ Confirm: Agree on the rating protocol. The standard convention that works well: stars are the client’s (5 stars = select), colour tags are the DIT’s (green = sent to Photoshop, red = technical issue, yellow = photographer revisit). But if you have a system that works for you, just make sure the DIT knows what it is.

△ Confirm: Talk through the overlay situation with the DIT. They need to know if you or the art director have overlay files (PNG/PSD/TIFF with transparency) and what the client expects to see at video village. On Pro, overlays are visible only on the hardwired HDMI monitor — not on the iPad.

Step 5: Cables and hardware packed and tested

Pack everything and verify each component individually before combining them into the full chain test in Step 6.

Step 6: Full chain tested at home

This is the step that separates a stressful shoot from a smooth one. Individual components can all test fine on their own and still fall apart when you run them together under load.

  1. Connect camera to laptop via tether cable. Shoot several frames. Confirm images arrive in Capture One without delays or errors.
  2. Connect external monitor via HDMI. Confirm the Viewer window displays on it and updates when new images arrive.
  3. If using Capture Pilot or Live for Studio: connect iPad to the router, confirm the connection, confirm ratings sync back to Capture One on the laptop.
  4. Load an overlay file and confirm it displays correctly on the Viewer.
  5. Run the full chain for at least 15 minutes. Some issues — thermal throttling, connection drops, cable faults, memory leaks — only appear under sustained use. A 30-second test won’t catch them.

If something fails during this test, you have time to fix it. On set, you don’t.

Outputs
Leading indicators (signals during setup)Capture One opens and shows your license tier in the title bar. Camera tethers and images arrive within 2-5 seconds. External monitor shows the Viewer window. iPad connects to Capture Pilot or Live for Studio on first attempt. Overlay displays correctly on the HDMI monitor. Ratings from iPad appear on the laptop within seconds.
Lagging indicators (final result)Full chain runs at home for 15+ minutes without drops, freezes, cable faults, or display issues. On shoot day, the DIT opens your laptop and the workflow is operational within minutes — no permissions to fix, no drives to reformat, no cables to hunt for.

On Set — Your Role During the Shoot

These aren’t sequential steps — they’re ongoing patterns from the first frame to the last.

Tether Cable Discipline

The tether cable is the most failure-prone piece of hardware in this workflow. You already know to be careful with it, but a few things are worth calling out because they’re easy to forget when things are moving fast.

  • Route the cable so it won’t be stepped on, caught by C-stands or light stands, or yanked by crew walking through the set.
  • Use strain relief at the camera body. The USB port on the camera is fragile. A tug on the cable without strain relief can damage the port — and that’s a repair, cannot be fixed on set.
  • Give the DIT a heads-up before moving beyond cable range. If you need to reposition and the cable is at its limit, a quick “I’m moving” gives them a chance to manage the slack or tell you it’s time to disconnect cleanly.
  • If the cable disconnects mid-shoot: pause shooting and let the DIT know. Shooting while disconnected means frames go to the card but don’t appear on the client monitor or in the DIT’s workflow. The DIT will tell you when the connection is back.
  • Never force a cable back in. Check the orientation and inspect the port first. USB-C looks symmetrical but it’s not always cooperative.

Communication with the DIT

The DIT can handle a lot on the fly, but there are a few things that go better with a heads-up:

  • Call out setup changes before they happen. Lens swap, background change, new look, moving to a different set — a few seconds of notice lets the DIT switch folders, update the iPad feed, and brief the client.
  • If you’re doing a rapid-fire burst: a quick “I’m doing a burst — images will queue up” keeps the DIT from thinking something is wrong when 15 frames land at once.
  • If the DIT says “hold”, please hold. They might be restarting software, switching capture folders, reconnecting a dropped iPad, or troubleshooting a display issue. Shooting during a hold creates orphaned files or missed frames. They’ll tell you when you’re good to go.
  • Announce when a take is final. “That’s the one” or “Moving on” tells the DIT they can relay to the client and prep for the next setup.

What to Expect from the DIT

  • A 2-5 second delay between your shutter click and the image appearing on the client monitor. Longer for high-megapixel files or when the laptop is under load. This is normal.
  • During Photoshop retouching, the client monitor may show a static image (the last selected frame). Also normal.
  • The DIT manages overlay display, client ratings, and folder switching. You don’t need to touch Capture One.
  • The DIT will relay client star ratings (selects) back to you — either live or batched between setups.

Deep Dive Reference

For on-set troubleshooting, start with → DIT Troubleshooting

For extended technical information on camera tethering, cable specifications, and what happens when handoff prep isn’t completed, see DIT_Edge_Cases:

Official Documentation

Camera Tethering Setup by Brand:

Capture One:

Cables:

Apple (macOS Configuration):

Quick Reference

Pre-shoot checklist for someone who’s done this before:

Software and Permissions

  • Capture One subscription tier confirmed and communicated to DIT
  • Capture One license active, not expiring during shoot
  • Capture One version tested with tethering — not updated after verification
  • iPad apps confirmed working — not updated day-of
  • macOS: Local Network ON for Capture One
  • macOS: Firewall allows Capture One incoming connections
  • macOS: Automatic updates disabled
  • macOS: Capture folder excluded from Spotlight
  • macOS: Stage Manager disabled
  • macOS: Energy set to never sleep on power
  • macOS: Not upgraded within 2 weeks of shoot

Camera

  • USB mode set to PTP
  • Auto power-off / sleep disabled
  • Dual card slot backup config confirmed
  • File naming convention agreed with DIT
  • White balance approach agreed (custom / Kelvin, consistent per look)

Hardware

  • Tether cable tested with camera + laptop
  • Spare tether cable packed
  • Strain relief packed (CableLock / JerkStopper)
  • Camera plate compatible with tether cable routing
  • HDMI cable + adapter tested with laptop
  • Backup HDMI cable packed
  • Active HDMI extender / fibre cable packed (if needed)
  • Dedicated router packed and tested
  • Ethernet cable packed
  • iPad(s) charged and apps confirmed
  • Power strip packed
  • Charging cables packed (iPad, laptop)
  • Laptop power supply packed
  • Cooling pad packed

Storage and Handoff

  • Sufficient free space on capture destination
  • Handoff drives formatted exFAT
  • Handoff drive tested (mounts, writable)

System Exclusions

  • iCloud Desktop & Documents sync: capture folder excluded or setting disabled
  • Time Machine: capture folder excluded
  • Antivirus: capture folder excluded (or impact tested)

Camera Firmware and Software Versions

  • Camera firmware version documented (known-good version: _______)
  • Capture One version documented (known-good version: _______)
  • Camera firmware: not upgraded within 2 weeks of shoot

Coordination

  • Overlay files provided to DIT or confirmed on laptop
  • Rating protocol agreed (stars = client, colour tags = DIT)
  • Shot pacing and setup change protocol discussed
  • Full chain tested at home for 15+ minutes

FAQs

  • Do I need to know Capture One?

    Not really. The DIT operates Capture One on your laptop. What you need to be comfortable with is confirming your license, setting up the macOS permissions, and testing the tether connection. The editing tools, the Capture Pilot server setup, overlay configuration — that’s all the DIT’s side.

  • What if I don’t have admin access to change macOS settings?

    If it’s your personal laptop, you do. If it’s a corporate-managed machine with MDM restrictions, that’s worth flagging to production before the shoot day. Several of the permissions the DIT needs — Local Network, Firewall exceptions — require admin access. If those can’t be set, the DIT falls back to HDMI-only operation per SOP_DIT_Wired_Only, which means no iPad browsing and no independent client rating. Not the end of the world, but it’s a narrower toolkit.

  • Should I update Capture One before the shoot?

    If tethering works right now, no. Updates can change tethering behavior, reset permissions, or introduce new bugs. The only reason to update is if you have a specific problem that a newer version fixes — and even then, give yourself at least a week to test the full chain afterward. Same goes for macOS. Stability on a known-good version is worth more than new features on an untested one.

  • What’s the difference between Pro and Studio for the DIT?

    Studio unlocks the full toolkit: Client Viewers (independent follow-capture display), Live for Studio iPad app, overlay display on Capture Pilot. Pro doesn’t have any of those — the DIT’s overlay-capable display path is the hardwired HDMI monitor only. It’s not a limitation of the DIT’s skill; it’s a limitation of the subscription tier. Letting the DIT know which one you have changes their entire approach.

  • Can I run Capture Pilot and Live for Studio at the same time?

    Yes, if you have Studio. It’s actually a good redundancy strategy — Capture Pilot for fast local viewing, Live for Studio or Capture One Live as a fallback if something drops. The DIT will sort out which device handles ratings to avoid conflicts.

  • Why exFAT and not APFS?

    APFS is Mac-only. If you hand a client an APFS drive and they’re on Windows, they can’t open it without third-party software. exFAT is natively readable on both platforms, supports files up to 16 EB, and has no practical file size limit for photography. FAT32 has a 4 GB file size limit — don’t use it.

Common Traps

Updating software the night before. The update notification pops up and it feels responsible to install it. But updates can change tethering behavior, reset macOS permissions, or break Capture Pilot compatibility in ways that aren’t obvious until you’re on set. If it works today, leave it alone until after the shoot. This catches experienced photographers more often than beginners — because experienced photographers are the ones who stay on top of updates.

Skipping the chain test. You tested the tether cable. You tested the HDMI cable. You tested Capture Pilot. But you never ran them all together for 15 minutes. On set, the laptop thermally throttles under the combined load of tethering + display output + Capture Pilot server, and images stop arriving. The chain test catches the interactions between components that individual tests miss.

Moving beyond cable range without warning. You’re focused on the shot and you reposition without thinking about the cable. The strain relief catches it — or it doesn’t, and the USB port takes the force. Either way the tether disconnects, the DIT loses the feed, and the client monitor goes dark. A quick “I’m moving” gives the DIT a chance to manage the slack or disconnect cleanly.

Shooting during a DIT “hold.” The DIT says “hold” and the client is waiting and the light is right and it feels wrong to stop. But the DIT is saying hold because they’re restarting software, switching folders, or reconnecting a dropped connection. Frames shot during a hold land on the card but not in Capture One — the DIT can’t see them, can’t edit them, can’t show them to the client. When the DIT says hold, they mean it.

Reformatting a drive on shoot day. You realize the handoff drive is APFS, not exFAT. Reformatting at the DIT station wipes whatever was on it. Or worse — the DIT discovers the format mismatch at wrap when copying files for handoff, and there’s no exFAT drive available. Format drives at home before the shoot.

Letting the camera sleep between setups. You step away to discuss lighting. The camera auto-sleeps and kills the tether connection. The DIT has to wake it and re-establish the connection, which sometimes means unplugging and replugging the cable. Disable auto power-off before the shoot — it takes 10 seconds and saves real time on set.

Keeping This SOP Alive

This document is a hypothesis about what makes the photographer-DIT handoff smooth. If you follow it and something is missing, wrong, or unnecessary, the document needs updating — that’s not a reflection on you or the DIT.

Refactoring triggers:

  • A macOS update introduces a new permission requirement → add it to Step 2
  • Capture One changes its tethering protocol or subscription tiers → update Step 1 and the FAQs
  • A new camera body has a different USB mode or tethering requirement → update Step 4
  • The DIT keeps asking for something that isn’t on this list → add it
  • A checklist item is consistently irrelevant → remove it

When this SOP needs more than a tweak:

  • Iterate: A step needs refinement or a new piece of hardware enters the workflow → update the step
  • Pivot: Capture One changes its subscription model and eliminates tier differences → restructure around the new licensing
  • Dissolve: The team moves to wireless tethering and this cable-based workflow is no longer the default → archive with a note

North: Where does this come from?

  • The photographer’s knowledge of their own gear — nobody knows your setup like you do
  • SOP_DIT_Pro and SOP_DIT_Studio (the DIT SOPs that depend on this preparation being done)

East: What opposes this?

  • “We’ll figure it out on set” — sometimes you do, but it’s always with a crew on the clock
  • Corporate-managed laptops where admin access is restricted — flag this early

South: Where does this lead?

  • A DIT who can start the SOP_DIT_Pro or SOP_DIT_Studio workflow without friction
  • SOP_DIT_Pre_Shoot_Preparation — the DIT’s pre-shoot preparation that builds on this handoff
  • Reliable tethered shooting with minimal downtime
  • Clean file handoff on exFAT drives that work on any platform

West: What is similar?

  • Pre-flight checklists in aviation — systematic verification before the operation begins, not because the pilot doesn’t know how to fly, but because complex systems have too many variables to hold in your head
  • SOP_DIT_Pro and SOP_DIT_Studio (same workflow, opposite perspective — the DIT’s side of the same shoot)

Graph View

Backlinks