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

A pipeline creates proxy files with identical names to camera originals in the same searchable library, making automated relinking choose the wrong media class.

Problem

A pipeline creates proxy files with identical names to camera originals in the same searchable library, making automated relinking choose the wrong media class.

Solution

Root Cause / Diagnostic:
Generating proxy media with identical filenames, extensions, and directory paths creates file namespace collisions inside NLE asset management engines. When automated conform or relinking occurs, the system matches on filename alone and inadvertently connects low-bitrate proxies into the high-resolution mastering sequence.

Actionable Fix:
1. Enforce distinct naming conventions (e.g., appending _Proxy or changing file extension to .mov ProRes Proxy) and store proxies in a dedicated /Proxies/ directory tree.
2. Configure NLE proxy attachment workflows using native proxy linking tools (which track media class tags) rather than generic "Relink Media" file path overrides.
3. Run an asset report prior to final mastering export to verify that 100% of timeline clips link to high-bitrate camera originals rather than proxy streams.

Pro Tip:
In Premiere Pro or DaVinci Resolve, always use the dedicated "Attach Proxies" function rather than replacing source clips, ensuring the NLE maintains strict internal separation between raw and proxy media classes.