← Back
Team Delegation, Outsourcing, Remote Editors & Production Pipelines

An editor sends a project with local cache files omitted but fails to distinguish which derived media is reproducible and which generated element was actually unique to the edit.

Problem

An editor sends a project with local cache files omitted but fails to distinguish which derived media is reproducible and which generated element was actually unique to the edit.

Solution

Root Cause / Diagnostic:
Editors routinely exclude scratch folders to save space, but inadvertently omit generated voiceovers, stabilized motion track data, optical flow files, or compound clips that cannot be automatically re-rendered from raw footage.

Actionable Fix:
1. Separate Ephemeral Cache from Generated Creative Media: Place camera tracking data, audio voiceover recordings, and specialized renders into an Assets/Generated folder within the project.
2. Explicitly Document Required Regeneration Steps: Provide instructions on which sequences require optical flow or stabilization regeneration upon opening.
3. Render Critical Tracking and Stabilization Data: Bake warp-stabilized or tracked clips to standalone mezzanine files prior to project consolidation.

Pro Tip:
Warp Stabilizer and optical flow speed changes frequently drop their analysis data during project handoffs; bake stabilized shots to ProRes 422 before sending the project downstream.