Streamlining the DIT Workflow: Offloading and Creating Proxies in DaVinci Resolve

November 21, 2025

Learn a reliable DIT workflow using ShotPut Pro for verified offloading and DaVinci Resolve for creating formatted proxies with on-set LUTs.


Publisher’s note: Team Mixing Light is thrilled to welcome our newest contributor, Amanda, a Tampa Bay-based freelance DIT, Camera Operator, Broadcast Engineer, and Editor, with expertise in post-production supervision and Color Grading.

Please welcome Amanda in the comments below. You can read her full bio and get links on her Author page. As always, the first Insight from our Contributors is never behind the paywall – feel free to share this page!

From camera card to post house – a reliable workflow for on-set data management and proxy delivery

When you’re working as a DIT on set, your workflow needs to be bulletproof. There’s no room for guesswork when you’re responsible for camera-original data and delivering specs that meet post-house requirements. In this insight, we walk through a complete DIT workflow – from offloading camera cards with ShotPut Pro to creating properly formatted proxies in DaVinci Resolve that match the post house’s spec sheet.

This workflow covers the essential steps you’ll encounter on most productions: verified offloading to multiple drives, syncing audio by timecode, loading LUTs provided by the DP, and generating proxies with baked-in looks at the exact specifications requested by editorial.

“The spec sheet provided by the Post House…they requested that the codec be Apple ProRes proxy, the native frame rate, and they want this at half resolution for the proxies. They want the LUT baked in…as well as the audio synced and the timecode matching the original camera files.”

Amanda J. Arismendez, DIT
As a DIT, never make assumptions about your deliverable to the editor. Ideally, you'll get detailed specs, such as this one. Notice the technical details requesting of the camera settings, plus LUTs.
As a DIT, never make assumptions about your deliverables to the editor. Ideally, you’ll get detailed specs, such as this one. Notice the technical details requested of the camera settings, plus LUTs.

Key Takeaways

  • Verified offloading with source checksums ensures data integrity across multiple backup drives.
  • Detailed offload reports provide comprehensive documentation of every clip, including metadata and visual thumbnails.
  • Timecode-based audio sync in Resolve creates clean, organized media ready for proxy generation.
  • Loading LUTs into Resolve before proxy creation bakes the DP’s look directly into editorial deliverables.
  • Two different proxy creation methods in Resolve offer flexibility for different workflow requirements.

Related Mixing Light Insights

Mentioned Resources


Chapters

  • 00:24 – ShotPut Pro
  • 02:28 – Making Proxies with Resolve
  • 04:47 – Alternate Way to Create Proxies
  • 06:32 – Wrap-up

Let’s chat in the comments!

What challenges have you encountered with on-set workflows or proxy creation? How do you handle variations in spec sheets across different post houses? If you’re a Mixing Light Premium member, head down to the comments and let’s have a conversation – including any topics about on-set workflows you’d like me to tackle.

– Amanda


This Insight In-Depth: The Complete DIT Workflow – From Card to Proxy Delivery

Working on set as a DIT means juggling multiple responsibilities – offloading footage, creating backups, verifying data integrity, and delivering properly formatted proxies to the post house. Each step must work seamlessly, as production relies on these files being flawless. We’re breaking down the complete workflow, from the moment a card comes off the camera to delivering verified proxies that match editorial specs exactly.

My typical workflow begins with:

  • Proper offloading using ShotPut Pro.
  • Proceeds through audio sync and LUT application in Resolve.
  • Concludes with two different methods for creating proxies. Understanding both methods provides flexibility, allowing you to adapt to project requirements and personal preferences.

Setting Up ShotPut Pro for Verified Offloading

The foundation of reliable data management starts with verified offloading. ShotPut Pro handles this by creating source checksums during the copy process, ensuring that what ends up on your backup drives matches the original camera files exactly.

For the camera card offload in ShotPut Pro:

  • Select the ACAM preset in ShotPut Pro.
  • Verify both destination drives are set in the copy to location with the correct folder paths.
  • Confirm the output naming scheme matches the drive name.
  • Enable source checksum verification in the settings – this creates verification data for later confirmation.
  • Drag the camera card to the drop zone and hit Play.

The replication process copies to both drives simultaneously while generating checksums. Once complete, ShotPut Pro creates a comprehensive offload report showing:

  • Card name and verification status.
  • Total size and clip count.
  • Date and time of offload.
  • Individual clip names, sizes, durations, resolutions, codecs, and frame rates.
  • Five thumbnail screenshots from each clip for visual verification.

For audio cards, the process follows the same verification workflow:

  • Deselect the ACAM preset and select the sound preset.
  • Verify destination folders and naming scheme.
  • Drag the sound card and initiate the offload.
  • Review the completed offload report showing card name, verification status, and destination locations.

These reports become your documentation trail. If production calls three months later asking about a specific clip, you have detailed records of every offload with visual confirmation.


Syncing Audio and Loading LUTs in Resolve

With verified camera and audio files offloaded, the next phase happens in DaVinci Resolve.

  • Creating a bin for the card (labeled “A001” for the first A-camera card) keeps everything organized as you build the project.

Audio sync by timecode is straightforward in Resolve:

  • Import all camera and sound files into the bin.
  • Select all clips and choose “Auto Sync Audio.”
  • Select “timecode” as the sync method.
  • Resolve matches timecode stamps and pairs each camera clip with its corresponding audio file.

Before generating proxies, you need to load the LUT provided by the DP. This ensures the baked-in look matches what the DP approved on set:

  • Navigate to “Settings” and open the “Color Management” tab.
  • Select “Open LUT Folder” to access Resolve’s LUT directory.
  • Copy the DP’s LUT file into this folder.
  • Confirm the LUT appears in the available list and save.
  • Select all media, right-click on LUT, and apply the provided LUT to all clips.

Generating Proxies – Two Methods

Method One: Generating Proxies from the Media Page

This Media Page method generates proxies directly from your source clips using Resolve’s built-in proxy tools. This approach is efficient when you want straightforward proxy generation without timeline creation.

Setting up proxy generation:

  • Navigate to “Settings”, then “Master Settings” under “Optimize Media and Render Cache.”
  • Set proxy media resolution to half (matching the post house spec sheet).
  • Confirm “ProRes 422 Proxy” is selected as the codec.
  • Specify the proxy folder location on your drive.
  • Save the settings.

Generate the proxies:

  • Select all synced clips in the media pool.
  • Right-click and select “Proxy Media,” then “Generate Proxy Media.”
  • Wait for render completion (approximately five minutes for typical card volumes).

Verify the output:

  • Navigate to the proxy folder location.
  • Drag one proxy file back into Resolve’s media page.
  • Confirm the timecode matches the original camera file exactly.

This verification step catches any issues before you deliver to the post house. The timecode must remain frame-accurate to maintain sync throughout the editorial process.


Method Two: Creating Proxies via Timeline Render

The timeline render method offers more control over the final output and works well when you need specific timeline settings or want to manage clip order precisely.

Creating the timeline:

  • Select all clips in the media pool and right-click.
  • Choose “Create Timeline Using Selected Clips.”
  • Label the timeline (for example, “A001” for A-camera, first card).
  • Start timecode at zero.
  • Create a custom timeline resolution at half the native camera resolution (matching the spec sheet requirement).
  • Confirm frame rate matches the native camera recording.

The timeline now contains all synced clips at the correct resolution with the LUT applied. Scrub through the timeline to verify everything appears correct before rendering.

Rendering individual clips:

  • Navigate to the Deliver page.
  • Select “Individual Clips” (not the full timeline) – this creates separate files rather than one continuous output.
  • Under the File tab, select “Source Name” to name each rendered clip after its original camera file.
  • Under Video settings, select “Apple ProRes” as codec and “ProRes 422 Proxy” as type.
  • Choose the proxy folder location on your drive.
  • Add to the render queue and render all.

This method generates individual proxy files, each named to match the original camera files, making them easy to identify and manage in editorial.


Verifying Media Before Delivery

Verification doesn’t stop at render completion. Before delivering proxies to the post house, play through each clip to confirm:

  • Complete audio playback from start to finish.
  • Verify no visual glitches or rendering artifacts.
  • Smooth playback without dropped frames.
  • Audio and video remain in sync throughout the clip.

This quality control step catches problems before they reach editorial, saving time and maintaining your reputation as a reliable DIT.


Workflow Considerations and Next Steps

This workflow represents the core DIT responsibilities on most productions: Verified data handling, proper audio sync, look management, and proxy creation. Some productions also require live grading on set, which adds another layer to the workflow but follows similar principles of verification and proper handoff to post.

The key to successful DIT work is developing reliable systems that scale across different productions while maintaining the flexibility to meet specific post-house requirements. Each spec sheet may request different codecs, resolutions, or delivery formats, but the underlying workflow of verified offload, proper sync, and accurate proxy creation remains consistent.



 

Is your career calling out for help?

Answer the call with a Mixing Light Membership. Gain client-tested tips, workflows, and add new skillsets from our pro Contributors!


JOIN NOW! You don't have to do this alone!
Loading...