Understanding the Integration
Knowing How the Integration Works
-
Every integration is different - Native camera integrations work differently than external encoder integrations. There are standards that all integrations must meet, but it is left to the Partner to tailor the integration that best meets their customer’s needs.
-
Three types of integrations: Internal firmware, external recorders/encoders, and apps - each follows specific functionality guidelines and undergoes Frame.io certification.
-
Original asset upload - Certain cameras (RED, Fujifilm, Nikon, Lumix) support uploading camera originals through C2C. The Red VRaptor and Komodo cameras can upload .r3d files to Frame.io. However, Frame.io does not do not debayer and can not play back undebayerd “raw” video files. The mirrorless cameras do not upload any “raw” recordings to Frame.io. They will only upload .mp4, or .mov containers and this is limted to h.264, h.265, and Prores codecs.
-
Proxy + Master workflows Cameras - Some cameras (Canon C80/C400, Nikon with NX Mobile Air, Fuji, and Panasonic) record both master and proxy simultaneously. The proxy file is uploaded to Frame.io
-
Proxy + Master workflows Recorders - Atomos recorders only upload HEVC h.265 proxy files. They will not upload any Prores or RAW recordings to Frame.io
-
Relinking proxies - Many C2C devices support master recording and simultaneously generate proxies that can be relinked to “hero” media using clip name and timecode. These recordings have the same start and ending timecode and can easily use fit into the a linked proxy workflow in many popular NLEs.
File Upload Behavior
-
Assets must be created first - The device must record a file to be uploaded. This requires device storage media for C2C to work.
-
Assets created before proper device pairing may not upload after the device is paired.
-
Assets recorded in a pause state will not upload.
-
Automatic upload after stop-record - Proxies upload automatically when recording stops.
-
Real-time upload capability - Some devices support uploads while recording (Atomos, Teradek Prism/Serv 4K, Mavis, Accsoon)
-
Offline resilience - C2C integrations track assets created offline and automatically upload them once reconnected to network.
Variables Across Integrations
Every manufacturer implements C2C differently based on:
-
Resolution capabilities
-
Frame rates
-
Codec options
-
Container formats
-
Compression methods
-
Upload timing (post-record vs real-time)
The better you know your device’s integration and its strengths and limitations the better your Frame.io Camera to Cloud experience will be.