Investigate Blackmagic Cloud Storage for Camera-to-Cloud

[erik-sutton95]

Goal

Investigate the feasibility of supporting Blackmagic Cloud Storage as an additional Camera-to-Cloud destination alongside Frame.io, and define an implementation path if Blackmagic provides a supported integration route.

Why it matters

Productions centered on DaVinci Resolve and Blackmagic Cloud should not need to route every delivery through Frame.io. A second destination would give crews more choice while preserving the existing on-device caching, optional LUT baking, and field-upload workflow.

Proposed investigation

• Confirm whether Blackmagic exposes a supported public or partner API for third-party iOS uploads
• Document authentication, account, project, library, and destination-selection requirements
• Validate supported media, proxy, metadata, sidecar, resumable-upload, duplicate, and status behaviors
• Determine whether the current export, cache, internet-hop, progress, retry, and cancellation pipeline can be shared with Frame.io
• Define a destination abstraction so Blackmagic Cloud Storage can sit beside Share and Frame.io without duplicating delivery logic
• Assess credential storage, privacy, rate limits, background transfer, failure recovery, and any commercial or partner-program constraints
• Record explicit blockers and alternatives if no supported upload API is available

Success looks like

The investigation produces a source-checked feasibility decision. If supported, it leaves a concrete architecture, user flow, authentication plan, test strategy, and implementation task for adding Blackmagic Cloud Storage as a selectable delivery destination. If unsupported, it documents the blocker clearly enough to avoid an unofficial or fragile integration.

Open questions

• Is there a supported API for uploading media directly from a third-party iOS app?
• Does access require Blackmagic partner approval or a specific Blackmagic Cloud plan?
• How should OpenZCine map accounts, projects, libraries, folders, and Resolve cloud workflows?
• Which originals, proxies, LUT-baked exports, metadata, and sidecars should be offered?
• Can uploads resume reliably in the background and recover across the camera-Wi-Fi internet hop?
• What user-visible state confirms that an upload is available to the intended Resolve collaborators?