Kai Mallari's Notes'

SOP_DIT_Studio

39 min read

A complete operating procedure for running a DIT station on a commercial photo shoot using Capture One Studio. This SOP covers pre-shoot setup, on-set operations, and troubleshooting for the Studio subscription tier.

Core principle: Studio gives you the full toolkit. Client Viewers, Live for Studio, Capture Pilot with overlay, and Capture One Live are four independent layers of redundancy. Set up the hardwired Client Viewer first, then stack wireless layers on top of it. If any layer fails, the others keep the client working.

This is one of three tier-specific DIT SOPs. If the photographer has Pro, use SOP_DIT_Pro. If all wireless options fail, fall back to SOP_DIT_Wired_Only.

Intent

We do this because a commercial shoot with clients at video village requires real-time image review, overlay reference, and client rating. Success means the client sees every capture within seconds, can independently rate selects, can reference the layout overlay on their own device, and can browse freely — all without interrupting the DIT’s editing workflow.

Use When

  • The photographer’s laptop runs Capture One Studio (not Pro or Enterprise — check the title bar)
  • There is a client, art director, or creative team who needs to view images at video village
  • The shoot involves tethered capture with client-facing image review and/or layout overlays
  • You are the DIT operating the photographer’s equipment

Not for: Pro subscriptions (use SOP_DIT_Pro). Not for untethered shoots where images are reviewed after the fact. Not for situations where the photographer is also the DIT and no video village exists.

Why This Matters

Without this processWith this process
macOS permissions block Live for Studio and Capture Pilot, and you discover it on set, wasting 30 minutes of crew standby timePermissions are pre-configured at home; everything connects on first attempt
Live for Studio version mismatch blocks the iPad from connecting and you have no fallback preparedApp versions are confirmed in advance; version pairing is tested at home
Capture Pilot drops repeatedly because you’re on venue Wi-Fi with 40 other devicesDedicated router isolates your traffic; drops are rare
Client can’t see the layout overlay on their iPad and doesn’t know if shots fit the compOverlay strategy is chosen in advance; Capture Pilot provides independent overlay toggle on the iPad
HDMI cable is too short for video village, or display flickers, and you have no backupCable length, adapter compatibility, and spares are tested before the shoot
Client rates on both Live for Studio and Capture One Live, creating conflicting ratingsRating protocol designates one device per reviewer; no conflicts

Baseline: a DIT who shows up with cables and software but no systematic pre-shoot preparation.

What Studio HAS That Pro Doesn’t

Before proceeding, understand what the Studio tier gives you — these features shape the architecture of this SOP:

  • Client Viewers with Follow Capture. Independent always-on display windows that auto-follow the latest capture. Unlike Pro’s standard Viewer, Client Viewers persist across app switches and don’t get covered by other windows.
  • Live for Studio (iPad app). Dedicated iPad app for independent browsing and rating over the local network. Higher stability than Capture Pilot. Does NOT display overlays.
  • Capture Pilot with independent overlay toggle. On Studio, the Capture Pilot iPad app gains overlay, grid, and guide toggle icons. The client can show/hide the overlay independently of your workspace — you control content, they control visibility on their screen.
  • Capture One Live has no overlay (same as Pro). The cloud viewer shows rendered images without overlays regardless of tier.

Your overlay-capable display paths are the hardwired Client Viewer monitor AND Capture Pilot on iPad.

Architecture Summary

LayerToolNetworkOverlayClient Rates IndependentlyReliability
1Client Viewer (HDMI)None (cable)Yes (coupled to workspace)NoHighest
2Live for Studio (iPad)Local Wi-FiNoYesHigh
3Capture Pilot (iPad)Local Wi-FiYes (independent toggle)YesMedium — drops common
4Capture One Live (cloud)InternetNoYesDepends on internet

The 8-Step Pre-Shoot Setup

InputsPhotographer’s laptop with Capture One Studio (license active), dedicated portable router, Ethernet cable, HDMI cable + adapter, iPad with Live for Studio app (version 1.4.0+ for Capture One 16.7+), second iPad with Capture Pilot app (if overlay on iPad needed), overlay files (PNG/PSD/TIFF with transparency), power strips, charging cables, laptop cooling pad, all adapters.

Step 1: macOS configured for tethered shooting

Configure the photographer’s Mac so that macOS does not interfere with tethering, networking, or display output during the shoot. MUST be done at home before the shoot — the DIT cannot fix these on set without the photographer’s admin password.

  1. System Settings > Privacy & Security > Local Network — Toggle Capture One ON. If not listed, open Capture One, start Image Server, accept the macOS prompt.
  2. System Settings > Network > Firewall > Options — Confirm Capture One is in the allow list. If the firewall is on and Capture One is not listed, Live for Studio and Capture Pilot will silently fail.
  3. System Settings > Privacy & Security > Screen Recording — If using a window manager (Rectangle, BetterTouchTool), grant Screen Recording permission.
  4. System Settings > General > Software Update > Automatic Updates — Turn off all toggles.
  5. System Settings > Siri & Spotlight > Spotlight Privacy — Add the capture destination folder.
  6. Stage Manager — Disable via Control Center > Stage Manager > Off.
  7. Energy Settings — Set to never sleep when plugged in. Use caffeinate -d in Terminal or Amphetamine as a safety net.

If macOS permissions cannot be configured (no admin access):

  • Alternate: Ask the photographer to configure them remotely via screen share before the shoot day.
  • Contingency: On set, ask the photographer to enter their admin password while you walk through each setting.
  • Emergency: Skip Live for Studio and Capture Pilot entirely. Fall back to SOP_DIT_Wired_Only (HDMI only). Both wireless tools require Local Network permission — without it, the iPad will never connect.

Step 2: Network up and tested

Establish a dedicated local network so Live for Studio and Capture Pilot traffic is isolated from venue interference.

  1. Set up the dedicated portable router. Use a known SSID and password. Disable AP isolation / client isolation.
  2. Connect the laptop to the router via Ethernet. Do not use Wi-Fi for the laptop.
  3. Connect iPad(s) to the router’s Wi-Fi.
  4. Confirm all devices are on the same subnet (e.g., all 192.168.x.x).
  5. Do NOT use the venue’s production Wi-Fi. Interference from walkies, lighting dimmers, and other wireless gear will kill the connection.
  6. If using Capture One Live, route cloud traffic through a separate interface (laptop Wi-Fi to venue internet or mobile hotspot). This isolates cloud uploads from local traffic.

Step 3: Client Viewer on HDMI monitor — always-on display at video village

Set up the hardwired Client Viewer display — your most reliable client-facing output.

  1. Connect the external monitor via HDMI before launching Capture One. Let macOS detect and arrange displays first.
  2. System Settings > Displays — Set to Extended Display (not mirrored). Position logically.
  3. In Capture One: Window > Client Viewers > Client Viewer A.
  4. Drag the Client Viewer window to the external monitor. Resize to fill the screen.
  5. Set mode to Follow Capture (right-click an image > Follow Capture, or use the Window > Client Viewers menu). The monitor now auto-displays every new capture without any action from you.
  6. To pin a specific image: select the image, use the keyboard shortcut for Pin to Client Viewer A. The monitor holds that image until you change it.

Overlay on Client Viewer: Client Viewers do not show overlays by default. To enable, go to Settings > Appearance and enable overlay display for Client Viewers. Note: overlay visibility is linked to your main Viewer — when you toggle the overlay off on your screen, it disappears from the Client Viewer too. Assign a keyboard shortcut for fast toggling.

If display does not appear or flickers:

  • Alternate: Try a different USB-C to HDMI adapter. Some cheap hubs cannot sustain 4K60 under load.
  • Contingency: Lower the external monitor’s refresh rate to 50Hz (System Settings > Displays > Refresh Rate).
  • Emergency: Use a direct USB-C to HDMI cable (no hub). If no signal at all, check the cable length — standard HDMI is reliable only up to 15 feet (5m). Use an active HDMI or fibre-optic cable for longer runs.

Step 4: Live for Studio running on iPad — independent browsing and rating

Set up the iPad for independent client browsing and rating over the local network. Live for Studio is more stable than Capture Pilot and is the primary iPad tool for general use.

  1. In Capture One: go to the Tether Tool Tab > Live for Studio tool.
  2. Select the collection to share from the Collection dropdown (usually your Capture folder).
  3. Optionally set a password.
  4. Click the three dots (…) > Network Settings to verify the port and the Mac’s local IP. Manually assign a port number instead of leaving it on auto.
  5. Start sharing.
  6. On the iPad: open Live for Studio. Your session should appear on the Shared Projects screen. Tap to connect.
  7. If the session does not appear: tap the network node button on the iPad and manually enter the local IP and port number.

Client workflow: The client taps Follow (binoculars icon, top right) to auto-display the latest capture. They can stop following at any time to browse freely. Star ratings and colour tags applied on the iPad sync back to your Capture One session in real-time.

Important: Turn on Prevent Sleep in the Live for Studio iPad app settings (gear icon). iPads in Follow mode drain battery faster — keep a charging cable at video village.

Live for Studio does NOT display overlays, grids, or guides. If overlay viewing on the iPad matters, use Capture Pilot (Step 5).

If Live for Studio will not connect:

  • Alternate: Stop sharing, wait 5 seconds, restart. Force-quit Live for Studio on iPad, reopen.
  • Contingency: Confirm both devices are on the same network and subnet. Check firewall permissions. Try manual connection with IP and port.
  • Emergency: Abandon Live for Studio. Fall back to Capture Pilot for iPad viewing, or the client views images on the hardwired Client Viewer monitor only.

Step 5: Capture Pilot running for overlay viewing on iPad (if needed)

Set up Capture Pilot alongside or instead of Live for Studio when the client needs to see overlays on the iPad. On Studio, Capture Pilot provides independent overlay toggle icons that Pro does not have.

  1. In Capture One: Capture Tool Tab > Capture Pilot tool.
  2. Basic tab: Confirm Server Name, select the Folder matching your capture destination, optionally set a password. Set Publish To to “Mobile” or “Mobile and Web.”
  3. Mobile tab: Enable “Rate images” and “Color tag images.” MUST manually assign a port number (not “auto”). Write down the port number.
  4. Click Start Image Server.
  5. On the iPad: open Capture Pilot. Server should appear in Local Servers list. Tap to connect.
  6. If server does not appear: tap ”+” on the iPad, manually enter the laptop’s IP address and your assigned port number.

Overlay on the iPad: Once connected, the client sees overlay, grid, and guide toggle icons at the bottom of the Capture Pilot app screen. Tapping them shows/hides the overlay independently of your desktop. You control overlay content, position, opacity, and scale from Capture One. The client only controls visibility on their screen.

Capture Pilot reliability note: Capture Pilot is less stable than Live for Studio. Connection drops are common. If the connection drops, the client taps OK on the error dialog and re-selects the server from the list. Have them practice this before the shoot starts so it is not confusing mid-take.

Running both Live for Studio and Capture Pilot simultaneously: This works. The client uses Live for Studio for general browsing and rating. When they need to see the overlay on a specific image, they switch to Capture Pilot and tap the overlay icon. You can run both servers concurrently from Capture One Studio.

If Capture Pilot will not connect:

  • Alternate: Stop Image Server, wait 5 seconds, restart. Force-quit Capture Pilot on iPad, reopen.
  • Contingency: Use the browser fallback — on the iPad, open Safari and navigate to http://[laptop-IP]:[port]. Rating is limited but viewing works. No overlay in browser mode.
  • Emergency: Abandon Capture Pilot. The client views overlays on the hardwired Client Viewer monitor only. For independent browsing, use Live for Studio.

Step 6: Capture One Live shared (if internet available)

Set up cloud-based viewing for remote stakeholders or as a fallback for local tools.

  1. In Capture One: right-click Capture folder in Library > Share Online, or use the Capture One Live tool.
  2. Images upload as captured. Progress bar shows on thumbnails.
  3. Copy the sharing link. Open in a browser at video village or send to remote stakeholders.
  4. Client can star-rate, colour tag, and comment. Tap binoculars button for Follow mode.

MAY skip this step if no internet is available or no remote stakeholders need access.

Key limitations:

  • Requires internet. If it drops, client loses access until reconnection.
  • 5-15 second upload delay per image on slow connections.
  • Comments do NOT sync to Capture One desktop — only visible in the web interface and in the email summary sent when the session ends.
  • Filtered views do not auto-update when new images arrive. Client must refresh manually.
  • If running Live for Studio (local) and Capture One Live (cloud) simultaneously, cloud uploads can compete for bandwidth. Prioritize local tools. Pause cloud sharing if it is causing local issues.

Step 7: Overlay configured and strategy selected

Configure the overlay for your workspace and choose how the client will reference the layout across display tools.

  1. Load the overlay file in the Overlay tool (Capture tool tab). Adjust opacity, scale, position. Enable “Follow Crop.”
  2. Assign keyboard shortcuts:
    • Overlay visibility toggle (View > Show Overlay or via the Overlay tool)
    • Pin to Client Viewer A (Edit > Edit Keyboard Shortcuts)
  3. Choose your overlay strategy based on client needs:

Option A: Client Viewer with overlay enabled, Capture Pilot for independent iPad overlay. Enable overlay on Client Viewer (Settings > Appearance). The client sees the overlay on the hardwired monitor. For iPad overlay, the client uses Capture Pilot and taps the overlay icon independently. Best when the client needs overlay reference on both the monitor and their iPad.

Option B: Client Viewer clean, Capture Pilot for all overlay viewing. Keep Client Viewer showing the clean rendered image in Follow Capture mode. The client uses Capture Pilot on their iPad for overlay-on viewing. This decouples your overlay toggling from what the client sees on the hardwired monitor. Best when you toggle the overlay frequently for your own editing and don’t want it flickering on the client monitor.

Option C: Periodic overlay check. Between setups, enable the overlay on Client Viewer and tell the client: “Overlay is up now, take a look.” Then disable when editing. Best when overlay is needed occasionally, not constantly.

Overlay display by tool:

ToolShows Overlay?Independent Control?
Client Viewer (HDMI)Yes, if enabled in Settings > AppearanceNo — coupled to your workspace toggle
Live for Studio (iPad)NoN/A
Capture Pilot (iPad)Yes (Studio/Enterprise only)Yes — client toggles independently
Capture One Live (browser)NoN/A

△ Confirm: Agree with the art director / creative lead on which overlay strategy they prefer before the shoot starts. Clarify which device(s) they expect to see the overlay on.

Step 8: Rating protocol agreed with client

Establish who rates, how, and where — before the first frame is captured.

  • Stars are the client’s. 5 stars = select. Unrated = pass. Binary only — no 1-3-5 scale.
  • Colour tags are the DIT’s. Green = sent to Photoshop. Red = technical issue. Yellow = photographer revisit.
  • If both Live for Studio and Capture Pilot are running, have the client rate on one device only. Last-write-wins on ratings — rating on two devices simultaneously can overwrite.
  • If both Capture One Live (cloud) and Live for Studio (local) are active, designate who rates where. On-set client uses the iPad. Remote stakeholders use the browser. Last write wins on any conflict.
  • Filter by 5 stars on your browser to pull selects and relay to the photographer.

△ Confirm: Verbally confirm with the client: “Rate your selects with 5 stars on the iPad. I’ll relay them to the photographer.” Confirm which iPad app they should rate on if both are running.

Outputs
Leading indicators (signals during setup)Live for Studio connects on first attempt and shows thumbnails. Client Viewer on external monitor auto-follows new captures. Capture Pilot connects and shows overlay toggle icons. Rating from iPad appears on your desktop within seconds. Overlay appears on Client Viewer and/or Capture Pilot as configured.
Lagging indicators (final result)Full chain runs for 15+ minutes at home without drops, freezes, or display issues. On set, the client can browse and rate independently on Live for Studio while you edit in Photoshop without disrupting their view. Overlay is viewable on the client’s preferred device.

On-Set Operations

These are not sequential steps — they are ongoing operational patterns during the shoot.

Active Shooting Workflow

  1. Client Viewer auto-follows each new capture — no action needed from you.
  2. The client browses independently on Live for Studio, rating selects with 5 stars.
  3. Ratings appear on your Browser thumbnails immediately. Filter by 5 stars to pull selects.
  4. Relay selects to the photographer as they come in, or batch between setups.
  5. If the client needs to check composition against the overlay, they switch to Capture Pilot and tap the overlay icon.

Switching Setups Mid-Shoot

When the photographer changes setups:

  1. Change your Capture destination folder in Capture One.
  2. Client Viewer: If set to Follow Capture, it automatically shows new captures in the new folder. No action needed.
  3. Live for Studio: Share the new folder from the Live for Studio tool. On the iPad’s Shared Projects screen, the new folder will appear. The client taps into it.
  4. Capture Pilot: Go to the Capture Pilot tool > Basic tab > Folder dropdown > select the new folder.
  5. Capture One Live: Share the new folder online if remote stakeholders need it.
  6. Brief the client: “I’m switching setups. Tap back on your iPad and select the new folder.”

Overlay Management

  • Client Viewer overlay is coupled to your workspace toggle. Use keyboard shortcut to re-enable after returning from Photoshop.
  • Capture Pilot overlay is independent — the client controls visibility on their iPad without affecting your workspace.
  • Best practice: keep Client Viewer clean (overlay off), use Capture Pilot for overlay-on viewing. This prevents your overlay toggling from flickering the client monitor.

Client Communication Protocol

  • Start of shoot: “You’ll see images automatically on the big monitor. Browse and rate on your iPad. Tap 5 stars on anything you like.”
  • Overlay check: “If you need to check the layout, switch to Capture Pilot and tap the overlay icon.”
  • Setup changes: “I’m switching setups. Tap back on your iPad and select the new folder.”
  • Capture Pilot drops: “Give me 15 seconds, I’m reconnecting.”

Troubleshooting Reference

Network & Connectivity

Live for Studio iPad cannot find the session. The iPad shows no sessions on the Shared Projects screen.

Capture Pilot “server unavailable” / connection drops. The most common Capture Pilot failure. iPad shows “server unavailable” and kicks back to the server list.

Capture Pilot sees session but shows “No Images.” iPad connects, shows correct session name, but thumbnail grid is empty.

Bonjour blocked (server not discoverable). Capture Pilot relies on Bonjour (mDNS) for discovery. If blocked by router config, iPad cannot find server.

FIX: On iPad, tap ”+” to add server manually. Enter laptop IP and port from the Capture Pilot tool.

Capture Pilot connects then drops repeatedly. Root causes: busy network > firewall interference > laptop under heavy load.

FIX: After checking network and firewall, fall back to browser method or use Live for Studio as primary iPad tool.

Simultaneous rating conflicts between on-set and remote reviewers. If the on-set client rates via Live for Studio and a remote stakeholder rates the same image via Capture One Live, the last write wins. No merge or conflict resolution exists.

FIX: Segregate rating channels. On-set client uses star ratings. Remote stakeholders use colour tags or comments only. Alternatively, remote reviewers observe only and submit feedback via a separate channel (Slack, text, email).

Capture One Live uploads compete with local traffic. Cloud uploads can saturate bandwidth and introduce latency on Live for Studio / Capture Pilot.

FIX: Separate interfaces. Ethernet for local traffic (Live for Studio, Capture Pilot). Laptop Wi-Fi for cloud uploads (venue internet or hotspot).

DHCP lease expiry drops iPad after 2-4 hours. iPad loses connection to Live for Studio or Capture Pilot after sustained use. The router’s DHCP lease expired and the brief renewal disrupted the connection.

FIX: Extend the DHCP lease to 24 hours in the router admin panel, or assign static IPs. For details, see EC - Router Config Checklist.

RF interference from wireless triggers or walkies. Capture Pilot or Live for Studio drops correlate with strobe fires (Godox, Profoto wireless triggers) or walkie use. These devices operate on 2.4 GHz and directly interfere.

FIX: Switch to 5 GHz Wi-Fi on the dedicated router. Move the router away from trigger receivers. For details, see DIT Triage - Network Setup.

Multiple iPads: one on Live for Studio, one on Capture Pilot. This works. Designate each iPad for a specific role (browsing vs overlay viewing). Rating on one device only — last-write-wins applies. For details, see DIT Triage - iPad Disconnected.

Router reboots mid-shoot. All wireless connections drop simultaneously.

IP Conflicts (Two Devices Get Same Address). Symptom: Intermittent connectivity — devices sometimes reach each other, sometimes not.

FIX: Assign static IPs or set DHCP reservations. → EC - Router Config Checklist

Ethernet Adapter Not Working. Symptom: USB-C to Ethernet adapter not detected.

FIX: Try a different USB-C port. Check System Settings > Network for the Ethernet interface. Some adapters need drivers on macOS Sequoia.

macOS-Specific Issues

Local Network permission silently denied. No visible error in Capture One, but Live for Studio and Capture Pilot fail to connect. This can also happen after a macOS update resets permissions — even if you verified it at home the day before.

FIX: System Settings > Privacy & Security > Local Network > Capture One ON. Re-verify on shoot morning if any OS updates occurred overnight (including MDM-pushed updates on corporate/agency laptops).

Sequoia tethering regression. Intermittent failures — rainbow wheel for 30 seconds before images appear in some configs. Sonoma 14.2 also broke camera connectivity.

FIX: Pin to a known-good macOS + Capture One version pairing. If tethering works, do not update the OS.

Automatic updates interrupting a shoot. macOS downloads and prompts for updates, consuming CPU and bandwidth.

FIX: Disable before shoot day. System Settings > General > Software Update > Automatic Updates > all off.

Spotlight indexing CPU spike on new RAW files. Each new file triggers indexing, consuming CPU.

FIX: Add capture destination folder to Spotlight Privacy exclusion list.

Stage Manager interfering with Client Viewer window. Groups windows by application, pulls Client Viewer off external display when switching apps.

FIX: Disable. Control Center > Stage Manager > Off. Use Spaces with “Displays have separate Spaces.”

Sleep/wake causing display detection loss. Mac sleeps, loses external display on wake. Client Viewer windows disappear and display arrangement resets.

FIX: Energy settings: never sleep when plugged in. caffeinate -d or Amphetamine as safety net.

Sonoma+ breaks ad-hoc networking. Internet Sharing (Mac-hosted network) unreliable on Sonoma+.

FIX: Do not rely on ad-hoc. Bring a dedicated router. Browser fallback (IP:port) may still work.

Display & Video Output

Client Viewer windows do not persist after Capture One restart. If Capture One crashes or is restarted, all Client Viewer windows close and their position, size, and mode are lost.

Overlay visibility on Client Viewer is coupled to your main Viewer. Toggling overlay off on your workspace hides it from all Client Viewer windows.

Display arrangement resets on cable reconnect. Unplugging HDMI causes rearrangement and Client Viewer jump.

USB-C hub display dropouts. Cheap hubs can’t sustain 4K60 under load. Intermittent black frames.

FIX: Use a known-good adapter (Apple, CalDigit, OWC). Avoid multiport hubs for video.

Sequoia display flickering. Sequoia 15.1 introduced HDMI flickering. Partially fixed in 15.3/15.6.

FIX: Lower refresh rate to 50Hz. Prefer DisplayPort over HDMI. Keep a spare adapter.

HDMI cable too short. Standard HDMI reliable up to 15 feet (5m) only.

FIX: Active HDMI cable or fibre-optic HDMI for longer runs. SDI converters as alternative. Spare standard cable for short-run backup.

Client monitor colour mismatch. Consumer TVs/field monitors display colours inaccurately.

FIX: Manually set colour profile in System Settings > Displays. Brief client: composition reference only, not colour-critical.

Capture One Software Issues

Live for Studio version mismatch blocks connection. Capture One 16.7+ is not compatible with Live for Studio versions prior to 1.4.0. The iPad will not connect at all.

FIX: Confirm app versions before the shoot. If the client is bringing their own iPad, ask them to verify the app version in advance. Carry your own iPad as a guaranteed fallback.

Live for Studio does not display overlays. Live for Studio shows the fully rendered image with edits, but composition overlays do not pass through.

FIX: Run both Live for Studio and Capture Pilot simultaneously. The client uses Live for Studio for general browsing and rating. When they need the overlay, they switch to Capture Pilot and tap the overlay icon.

Follow mode breaks when you switch Capture folders mid-shoot. Live for Studio does not automatically jump to the new folder. The client’s iPad appears frozen on the old folder.

Image Server doesn’t auto-start after crash/restart. Client iPad goes dead on Capture Pilot.

FIX: Immediately restart Image Server after any relaunch. Capture Pilot tool > Start Image Server. iPad should auto-reconnect.

Crash loses Client Viewer layout. Client Viewer positions, sizes, and modes are not saved between sessions.

FIX: Save workspace (Window > Workspace > Save Workspace). Memorize rebuild: Client Viewers > A > Follow Capture > drag to monitor > maximize. Practice under 20 seconds.

Memory leak during long sessions. 8+ hour sessions see memory climb, causing slowdowns.

FIX: Restart Capture One during lunch break. Save workspace first. Restart Image Server and re-share Live for Studio after.

Tether cable disconnect during file write. RAW file may be corrupt.

FIX: Wait for transfer indicator. Keep spare tether cable. Reshoot if corruption occurs. The card copy is almost always intact — import from card after the shoot to recover. For full corruption scenarios, see EC - Crash Recovery Sequence.

Capture One crash recovery (Studio). Target: under 90 seconds.

Disk full during shoot. Tethering stops with “Cannot save file” errors.

FIX: Stop shooting. Delete preview cache (10-50 GB), empty Trash, or redirect capture destination to a different drive. For emergency response steps, see EC - Disk Full Recovery.

iCloud syncing the capture folder. Files appear to vanish or show upload badges. macOS is trying to sync RAW files to iCloud because Desktop & Documents sync is enabled.

FIX: Move the capture destination outside Desktop/Documents, or disable iCloud Desktop & Documents sync. See DIT Triage - Slow Performance.

Time Machine backing up the capture folder. Disk I/O spikes during tethering, UI becomes sluggish. The backupd process is consuming disk bandwidth.

FIX: Exclude the capture folder from Time Machine. See DIT Triage - Slow Performance.

Capture Pilot histogram blank. Known bug — histogram overlay renders blank.

FIX: Known display bug. Don’t waste set time. Client doesn’t need the histogram.

Capture One Live filtered views don’t auto-refresh. New images matching filter don’t appear until manual refresh.

FIX: Tell reviewers: “Refresh to see new images.” Suggest Follow mode (binoculars) instead of filtering.

Client ratings not syncing. Ratings from Capture Pilot, Live for Studio, or Live don’t appear on desktop.

FIX: For Capture Pilot, confirm “Rate images” enabled in Mobile tab. For Live for Studio, ratings should sync automatically — check the network connection. Ratings only sync while connected. Live comments do NOT sync to desktop.

Antivirus Real-Time Scanning Slowing Captures. Symptom: Each capture takes 100-500ms longer than expected. Check Activity Monitor for antivirus processes.

FIX: Add capture folder to antivirus exclusion list. → DIT Triage - Slow Performance

Multiple Capture One Instances Running. Symptom: Session locked, “database in use” error.

FIX: Activity Monitor > search “Capture One” > force quit duplicates.

Session or Catalog Corruption. Symptom: Session shows no images or errors on launch.

FIX: Re-import from capture folder — sidecar adjustments are preserved. → EC - Crash Recovery Sequence

Preview Cache Corruption. Symptom: Thumbnails display incorrectly.

FIX: Capture One > Settings > Performance > “Clear Cache.”

Mac Hardware & Performance

Thermal throttling. Sustained tethering + RAW processing + Capture Pilot server + Client Viewer + Live for Studio is a very heavy sustained workload. CPU/GPU throttle, causing lag.

External SSD disconnect. USB-C SSD disconnects under load or if bumped.

FIX: Direct USB-C connection (not through hub). Tape cable. Consider tethering to internal storage, syncing to external later.

USB-C port contention. Camera + display + SSD + power can exceed available ports.

FIX: Plan port allocation before shoot. Thunderbolt dock with passthrough charging. Keep a port map.

Camera body swap mid-shoot. Photographer swaps bodies without warning. Tether drops, Capture One shows “No Camera Detected.”

FIX: Wait for macOS to detect the new body (2-10 sec). Capture One should auto-detect. If not: Camera > Select Camera, or unplug/replug, or restart Capture One. For the clean swap procedure, see DIT Triage - Tether Drops.

High-megapixel bottleneck (100MP+ medium format). Transfer times of 4-8 seconds per frame on Phase One/Hasselblad. Preview generation consumes significant RAM. UI becomes sluggish after 100+ frames.

Camera Firmware Broke Tethering. Symptom: Tethering stopped after firmware update. No on-set fix for bad firmware. → Firmware Known Issues and EC - Card Import Fallback

Wireless Tethering as Emergency Fallback. If all wired tethering has failed, some cameras have built-in Wi-Fi. Very slow but functional for review. → EC - Camera Brand Setup

No Power at Video Village. Options: battery-powered field monitor (2-5 hours), iPad on battery via Capture Pilot/Live for Studio (8-10 hours), or long extension cord. → DIT Triage - Environment

Tethering Completely Dead — Card Fallback. All troubleshooting exhausted. → EC - Card Import Fallback

iPad & Client Device Issues

iPad battery drain. All-day Live for Studio or Capture Pilot use with Prevent Sleep enabled drains significantly over a full shoot day (8-12 hours).

FIX: Power strip to video village. Charging cable at the iPad. Route cleanly if mounted.

Live for Studio version mismatch. Older iPad app versions will not connect to newer Capture One versions.

FIX: Confirm app version before the shoot (1.4.0+ required for Capture One 16.7+). If the client is bringing their iPad, verify in advance. Carry your own iPad as fallback.

Images loading slowly. Rapid-fire bursts create 5-15 second preview backlog.

FIX: Brief client about delay during fast shooting. Keep iPad in thumbnail view during bursts.

Live for Studio Freezing on iPad. Symptom: Live for Studio app becomes unresponsive during burst shooting or rapid captures.

FIX: Force-close the app on iPad (swipe up, swipe away). Reopen. If recurring during bursts, reduce capture rate or inform client of brief lag during rapid sequences.

Client Viewer Stops Following Capture. Symptom: Client Viewer on external display stops showing new captures.

FIX: Click in the Client Viewer window > ensure Follow Capture is enabled (check the toolbar). Manual image selection overrides Follow Capture — re-engage by clicking the Follow Capture button.

Storage & File Handoff

Drive format incompatibility. APFS/HFS+ drives are unreadable on Windows without third-party software.

FIX: Use exFAT for any handoff drive. Supports files up to 16 EB. If tethering to internal (APFS), copy to exFAT drive for handoff. Do not use FAT32 (4 GB limit).

On-Set Environment

Power loss at video village. Monitor goes black, router drops, all wireless connections die. macOS may rearrange displays.

FIX: When power returns — wait for monitor and router to boot, verify display arrangement, reopen Client Viewer if it closed, restart Image Server and Live for Studio sharing. A small UPS (600VA) prevents this entirely. For details, see DIT Triage - Environment.

Client brings own device (not iPad). Android tablet or Windows laptop — no Capture Pilot or Live for Studio apps available.

FIX: Send them the Capture One Live web link (works in any browser, requires internet). If no internet: the client views images on the hardwired Client Viewer monitor only. See DIT Triage - Environment.

Multi-client scenario (agency + brand). Multiple stakeholders at video village with potentially conflicting feedback and rating authority.

FIX: Designate one rater (usually lead art director). Others observe or use Capture One Live with limited permissions. Agree on rating lanes before the first frame. See DIT Triage - Environment.

Venue IT insists you use their Wi-Fi. Corporate/venue policy forbids rogue access points.

FIX: Use venue Wi-Fi for internet only (laptop Wi-Fi for Capture One Live uploads). Keep the dedicated router for local laptop-to-iPad traffic — it doesn’t need internet access. See DIT Triage - Network Setup.

Photographer Handoff Not Done

Arriving to an unprepared laptop. The photographer didn’t follow SOP_Photographer_Handoff. macOS permissions aren’t set, software may have been updated, camera may not be configured for tethering.

FIX: Run the 5-minute arrival assessment: check Capture One tier and license, test tether, check macOS permissions, check admin access, test display, check storage space. If admin access is available, fix permissions in 5-10 minutes and proceed with the full SOP. If admin access is unavailable, fall back to SOP_DIT_Wired_Only.

For the complete triage framework, decision tree, and specific failure scenarios, see DIT Triage - Photographer Unprepared.

Live for Studio version mismatch from photographer updating apps. Photographer updated Capture One but not the iPad app (or vice versa). Live for Studio shows no sessions.

FIX: Update the iPad app on set if possible. Or use Capture Pilot instead. Or use the DIT’s own iPad. See DIT Triage - Photographer Unprepared.

Deep Dive Reference

For on-set troubleshooting, start with → DIT Troubleshooting

For extended root-cause analysis, prevention strategies, and edge cases beyond this troubleshooting section, see DIT_Edge_Cases:

Official Documentation

Capture One:

Apple:

TetherTools:

Switching Workflows Mid-Shoot

If a core capability fails during the shoot and cannot be recovered, transition to a simpler workflow. → EC - Downgrade Transition

What failedSwitch to
Live for Studio only (Capture Pilot works)Continue with Capture Pilot as primary iPad viewer
Client Viewers + Live for Studio (Capture Pilot works)SOP_DIT_Pro workflow
All wirelessSOP_DIT_Wired_Only
Tethering completely deadEC - Card Import Fallback

Quick Reference

Pre-shoot checklist for someone who has run this SOP before:

  • Capture One Studio license active (check title bar)
  • Capture One version tested with tethering (do NOT update before shoot)
  • Live for Studio iPad app confirmed at version 1.4.0+ (required for Capture One 16.7+) — do not update day-of
  • Capture Pilot iPad app confirmed working — do not update day-of
  • macOS: Local Network ON, Firewall allows Capture One, auto-updates OFF, Spotlight exclusion, Stage Manager OFF, never sleep
  • Dedicated router packed + tested
  • Ethernet cable, HDMI cable + adapter, backup HDMI cable
  • Active HDMI extender or fibre cable if long run
  • Overlay files prepared (PNG/PSD/TIFF with transparency)
  • Keyboard shortcuts assigned: overlay toggle, Pin to Client Viewer A, Follow Capture
  • Capture Pilot manual port number set (not “auto”) and recorded
  • Live for Studio port and IP recorded
  • iPad(s) charged, Prevent Sleep enabled in Live for Studio settings
  • Spare iPad packed as fallback
  • Charging cables + power strip for video village
  • Overlay strategy agreed with art director (Client Viewer, Capture Pilot, or both)
  • Rating protocol agreed: stars = client, colour tags = DIT
  • Rating device designated (rate on one device only if running both Live for Studio and Capture Pilot)
  • External drives formatted exFAT
  • Full chain tested at home 15+ min: tether + Client Viewer + Live for Studio + Capture Pilot + overlay on Capture Pilot
  • Browser fallback tested (IP:port in Safari)
  • Internet tested (if using Capture One Live)
  • Workspace saved
  • Laptop PSU, cooling pad, all adapters packed

FAQs

  • What if there’s a version mismatch between Capture One and the Live for Studio iPad app?

    Capture One 16.7+ requires Live for Studio 1.4.0 or later. If the iPad app is older, it will not connect at all — no error message, just silence on the Shared Projects screen. Check the app version before the shoot. If the client is bringing their own iPad, ask them to confirm the version in advance. Always carry your own iPad as a guaranteed fallback.

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

    Yes. This is the recommended Studio workflow. The client uses Live for Studio for general browsing and rating (more stable, better browsing experience). When they need to see the layout overlay, they switch to Capture Pilot and tap the overlay icon. Both servers run concurrently from Capture One Studio without conflict.

  • Why can’t the client see the overlay on Live for Studio?

    Live for Studio does not pass through composition overlays. It shows the fully rendered image with all edits applied, but overlays, grids, and guides are not transmitted. This is a feature limitation, not a configuration issue. Use Capture Pilot for overlay viewing on the iPad.

  • Does the overlay on the Client Viewer monitor toggle independently from my workspace?

    No. Client Viewer overlay visibility is coupled to your main Viewer. When you toggle the overlay off on your workspace, it disappears from the Client Viewer too. This is why Option B (Client Viewer clean, Capture Pilot for overlay) is often the best strategy — it decouples your editing workflow from what the client sees.

  • Should I update Capture One or macOS before a shoot?

    No. Updates can break tethering, change interface behavior, break Live for Studio compatibility, or introduce new bugs. Only update if you have a specific problem that a newer version fixes AND at least a week to test the full chain. If tethering works, do not touch the OS or the app.

Common Traps

“It worked at home” complacency. The full chain worked perfectly in your living room. You skip the on-set network test. Venue Wi-Fi interference, a different router config, or a macOS permission that got reset after a software update causes Live for Studio to fail in front of the client. Always re-test the chain on-site before the shoot starts.

Updating software the night before. Capture One pushes an update notification, you install it “to be safe.” The update breaks Live for Studio compatibility (version mismatch) or changes tethering behavior. Now you’re troubleshooting unfamiliar bugs on set with a crew on the clock. Never update software right before a shoot.

Treating Capture Pilot as the primary iPad tool. Live for Studio is more stable and provides a better browsing experience. Capture Pilot drops connections frequently. Use Live for Studio as the primary iPad tool for browsing and rating. Use Capture Pilot specifically when the client needs overlay viewing. If you make Capture Pilot the only iPad tool, every drop is a visible failure.

Not clarifying the overlay strategy with the art director. You assumed Option B (Client Viewer clean, Capture Pilot for overlay) but the art director expected the overlay on the big monitor at all times. Or you set up Capture Pilot for overlay but nobody told the client how to toggle it. Agree on overlay strategy and demonstrate the toggle before the first frame is captured.

Rating on two devices simultaneously. The on-set client rates on Live for Studio. The same client also rates on Capture Pilot “just to check.” Last write wins — one rating silently overwrites the other. Designate one rating device before the shoot. If both apps are running, rate on Live for Studio only.

Keeping This SOP Alive

This procedure is a hypothesis about how to run a DIT station on Capture One Studio. When you follow it and something doesn’t work as described, update the SOP — don’t blame yourself or the client.

Refactoring triggers:

  • A new macOS version breaks a permission path or display behavior ⇒ update the macOS-specific troubleshooting section
  • A new Capture One version changes Live for Studio behavior, Capture Pilot behavior, or Client Viewer features ⇒ update Architecture Summary and relevant steps
  • A Live for Studio app update changes the version compatibility requirement ⇒ update Step 4 and the Quick Reference
  • A new edge case appears on set that isn’t covered ⇒ add it to the Troubleshooting Reference
  • The photographer handoff keeps failing at the same point ⇒ update SOP_Photographer_Handoff with more specific instructions
  • You keep skipping a step ⇒ it’s either unnecessary or the default has changed — clarify or remove

When this SOP needs more than a tweak:

  • Iterate: A step needs refinement or a new workaround exists ⇒ update the step
  • Pivot: Live for Studio gains overlay support, making Capture Pilot unnecessary for overlay viewing ⇒ restructure the overlay strategy around the new architecture
  • Dissolve: The team standardizes on Pro subscriptions and this tier is no longer encountered ⇒ archive with a note

North: Where does this come from?

  • SOP_Photographer_Handoff (what the photographer must prepare before the DIT can use this SOP)
  • Capture One Studio feature set and subscription tier capabilities

East: What opposes this?

  • SOP_DIT_Pro (the constrained alternative when only a Pro subscription is available)
  • Ad-hoc / improvised DIT setups with no systematic preparation

South: Where does this lead?

  • SOP_DIT_Wired_Only (fallback when all wireless options fail)
  • Post-shoot file handoff to client (exFAT drive with selects)

West: What is similar?

Graph View

Backlinks