DIT and AC Gotchas - Knowing the Hardware

Camera to Cloud
1

Knowing the Hardware

Understanding Recorders vs Encoders in C2C Workflows

One of the most fundamental decisions in a C2C workflow is choosing between a recorder and an encoder. While both can upload proxies to Frame.io, they serve different primary functions and are suited for different workflows.

Encoders: Proxy-First Devices

What they are: Encoders are designed primarily to compress video into small, uploadable files for immediate cloud delivery.

Characteristics:

  • Primary function: Create and upload H.264/H.265 (typically 5-50 Mbps) proxy files to Frame.io

  • Workflow: Proxies uploaded to cloud; editor relinks to camera original files later if needed or Proxies serve as “Hero” files for social media or other quick turn around workflows

  • Use Cases: Quick turn around and projects that benefit from fast uploads and asset visibility.

Examples of Encoder Devices:

  • Teradek Serv 4k/Prism Mobile

  • Teradek Cube 655

  • Accsoon SeeMo/SeeMo Pro

Recorders: Dual-Purpose Devices

What they are: Recorders capture high-quality files to local media while simultaneously generating proxies for C2C upload. They can also be used for single file proxy generation as well.

Characteristics:

  • Primary function: Record high-quality “hero” media to SSD/removable media

  • Secondary function: Generate H.265 proxies for Frame.io upload

  • File output: High-res files (ProRes, ProRes RAW, DNxHD/HR) on local media + compressed proxies to cloud

  • Workflow: Can edit from either local hero files OR cloud proxies

  • Best for: Productions wanting immediate high-quality backup and monitoring. Most common with Mirrorless cameras and in some cases can allow for higher quality file capture than internal media alone.

Examples of Recorder Devices:

  • Atomos Ninja TX

  • Atomos Ultra (Ninja Ultra, Shogun Ultra)

  • Atomos Shogun CONNECT

  • Atomos Ninja V/V+ with AtomX CONNECT module

Important Gotchas:

  • What you see is what you get. Both types of devices are creating files based on a video signal. If there are any video artifacts in the video feed, they will be present in your recording.

  • Atomos proxies can easily relink to the “hero” files recorded by the Atomos device itself. However when recodring over HDMI, the camera clip name is usually not passed over HDMI. One exception is the Nikon Z9. If you need to go back to the original camera file because of a video artifact error, or for off speed clips, as long as timecode matches, clips can be replaced within the NLE.

  • Single record proxy workflows over SDI with compatible cameras the Atomos can capture Clipname and Timecode and work as an encoder. You are however limited to resolution and bit depth of the SDI port.

Native Camera Integration vs External Recorder/Encoder

Beyond choosing between recorders and encoders, productions must also have the choice to use some camera’s native (internal) C2C integration or an external device. This decision significantly impacts workflow, equipment needs, and post-production approach.

Native/Internal Camera Integrations

What they are: Cameras with built-in C2C functionality that connect directly to Frame.io without external hardware.

How they work:

  • Camera connects directly to internet via Wi-Fi or Ethernet

  • Uploads handled by camera’s internal firmware

  • No additional rigging or power requirements

  • Pairing happens directly on camera interface

Currently Available:

  • Canon: C50, C80, C400

  • RED: V-RAPTOR 8K VV, V-RAPTOR XL 8K VV, V-RAPTOR XL 8K S35, V-RAPTOR 8K S35, V-RAPTOR , V-RAPTOR XL , Komodo-X, Komodo

  • Fujifilm: X-H2, X-H2S, GFX100 II, GFX100S II, GFX100RF, X-T50, X-T5, X-S20, X100VI, X-M5

  • Nikon: ZR, Z9, Z8, Z6 (via mobile phone and NX Mobile Air app)

  • Lumix: GH7, S5ii, S5iix

  • Leica: SL3, SL3s

What they upload:

  • Some upload camera originals and proxies (RED, Fujifilm, Lumix)

  • Some upload proxies (Canon records Hero file & proxies on device but only uploads proxies to the cloud)

  • Some require companion app (Nikon uses NX Mobile Air)

Best for:
Run-and-gun/documentary work

  • Minimal equipment for mobility

  • Fast setup and breakdown

  • Solo operator scenarios

Lightweight productions

  • Travel filmmaking

  • Event coverage

  • ENG-style shooting

When you already own compatible cameras

  • No additional equipment investment

  • Utilize existing camera ecosystem

  • Simplify workflow

Productions with limited crew

  • One-person camera operation

  • Minimal technical support on set

  • Less equipment to manage

When uploading camera originals is priority

  • RED workflows uploading R3D files

  • High-resolution still photography

  • No proxy/offline workflow needed

Budget-conscious productions

  • Avoid external device costs

  • Reduce rental expenses

  • Minimize power/media needs

Limitations to consider:

  • Limited to specific camera brands/models

  • May have slower upload speeds than external encoders

  • Camera battery drain from Wi-Fi/processing

  • No additional monitoring beyond camera screen

  • No secondary recording backup

  • Upload capabilities tied to camera’s processing power

When to Use External Recorder/Encoder

Best for:
Multi-camera productions

  • Standardize C2C across different camera brands

  • Uniform proxy specifications across all units

  • Consistent workflow regardless of camera choice

Cameras without native C2C support

  • Sony (FX6, FX9, Venice, etc.)

  • ARRI (Alexa, 35 etc.)

  • Blackmagic

  • DJI

  • GoPro

  • Panasonic (unsupported Lumix models)

When professional monitoring is needed

  • Atomos devices provide high-quality HDR monitoring

  • Director/DP need larger, calibrated screen

  • Focus pulling requires professional monitor

When secondary recording backup is critical

  • Insurance against camera card failure

  • Immediate ProRes/DNx backup files

  • High-value/non-repeatable content

Productions requiring optimized proxy bitrates

  • Fine-tune compression for available bandwidth

  • Adjust quality vs speed balance

  • Control file sizes precisely

When relinking to camera originals is essential

  • Traditional offline/online workflow

  • Automatic recording ensures clipname, timecode, and record triggers match camera files exactly

  • Lab dailies workflow integration

Rental house packages

  • Camera doesn’t have native C2C

  • Standardized equipment across departments

  • Established workflow with external recorders

When real-time upload during recording is needed

  • Atomos, Teradek Prism/Serv 4K, and Accsoon support uploading while recording

  • Immediate availability for remote viewing

  • Live sports/events coverage

Advantages:

  • Works with virtually any camera

  • Professional monitoring capabilities

  • Backup recording to separate media

  • Fine control over proxy encoding

  • Can optimize bitrate for bandwidth

  • Upgradeable independently of camera

Limitations to consider:

  • Additional equipment cost

  • More complex rigging and power management

  • Heavier/bulkier camera package

  • Devices in video pipeline may strip record triggers, timecode, or clipnames

  • Requires SDI for reliable clipname (HDMI often does not cary clip name)

Hybrid Approach: Mix and Match

Many productions strategically combine both methods:
Example Scenario: Three-Camera Commercial
A-Camera (Sony Venice):

  • Use Atomos Ninja

  • Need professional HDR monitoring for DP

  • Want ProRes backup recording

  • Upload proxies to Frame.io

B-Camera (Canon C400):

  • Use native C2C integration

  • Simpler handheld setup for mobility

  • Camera uploads proxies directly

  • No additional rigging needed

C-Camera (DJI Ronin 4D):

  • Use Teradek Cube 655 encoder

  • Gimbal work requires minimal weight

  • Small encoder doesn’t affect balance

Result: Each camera optimized for its specific role while all feeding into unified C2C workflow.

Practical Considerations

Camera Original Files vs Proxies:

  • Native integrations uploading originals (like RED R3D) require significantly more bandwidth

  • If uploading multi-GB camera files, calculate bandwidth needs carefully

  • External encoders creating 5-15 Mbps proxies are much more bandwidth-efficient

Metadata Reliability:

  • Native integrations generally have excellent metadata since it’s coming from source

  • External devices depend on camera’s SDI/HDMI implementation

  • The devices are camera agnostic, but require the camera to be identified in the menu

  • Some cameras require specific menu settings to output metadata and timecode on video signal out

Key Questions to Ask During Prep

What does your production want to achieve with Camera to Cloud?

  • Establish expections and manage them accordingly

Do our cameras have native C2C integration?

  • If yes, test it thoroughly before committing

  • If no, external device is only option

What are we uploading?

  • Camera originals → May need native integration or plan on manual uploads
  • Proxies → External device often more efficient

What’s our camera package?

  • Single brand with C2C → Consider native
  • Mixed brands → External standardizes workflow

What’s our bandwidth situation?

    • Limited bandwidth → External encoders with optimized bitrates

    • Good bandwidth → Native integration with originals possible

What’s our post workflow?

  • Offline/online with relinking → External device with automatic recording
  • Direct edit from uploads → Either can work

What are our crew responsibilities?

  • Solo/small crew → Who does what?
  • Full crew with DIT → External devices manageable

Common Mistakes to Avoid

Not testing native integration bandwidth needs

  • Uploading camera originals requires significantly more bandwidth than proxies

  • May overwhelm available connection

Using HDMI with external devices for relinkable workflow

  • HDMI rarely passes clip name

  • SDI required for clipname/timecode/triggers

1 Like