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

A remote editor receives an NLE project without the generated proxy database, so previously created proxies cannot be relinked to the supplied media paths.

Problem

A remote editor receives an NLE project without the generated proxy database, so previously created proxies cannot be relinked to the supplied media paths.

Solution

Root Cause / Diagnostic:
NLEs link proxy media through internal database pointers or relative sidecar paths. When proxy files are transferred without the associated project metadata or directory hierarchy, the NLE fails to match proxies to source camera footage automatically.

Actionable Fix:
1. Maintain Symmetrical Directory Trees for Proxies: Mirror the camera raw folder structure exactly inside a designated Proxies root folder using identical file names and extensions.
2. Standardize Ingest Batch Proxy Attachment: Attach proxies at the master bin level using batch relinking rules rather than attaching them manually clip-by-clip.
3. Script Proxy Verification Checks: Run automated file-matching scripts or project management scans before shipping drives or cloud archives to remote talent.

Pro Tip:
Never rename proxy files during generation; keeping the exact file name (or appending only _Proxy if required by the NLE) allows automated batch-relinking in a single click.