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

An automated transcode job starts before the ingest checksum completes, allowing a damaged source file to become the basis for downstream proxies.

Problem

An automated transcode job starts before the ingest checksum completes, allowing a damaged source file to become the basis for downstream proxies.

Solution

Root Cause / Diagnostic:
Watch folders that trigger transcoding immediately upon file appearance can start processing partially copied or corrupted media before hash verification concludes. This allows corrupted frames or incomplete clips to propagate undetected into proxy files, masking critical source errors until final conform.

Actionable Fix:
1. Configure transcode watch folders to trigger strictly on an upstream .complete receipt file generated only after MD5/xxHash64 verification matches the camera card.
2. Set ingest automation to write incoming files to a staging quarantine directory, moving them to the active transcode pool only post-validation.
3. Verify ingest logs for zero CRC/hash mismatch errors before dispatching batch jobs to Adobe Media Encoder or DaVinci Resolve render nodes.

Pro Tip:
Configure transcode daemons to poll sidecar .md5 manifests; if the calculated hash does not match before transcode initialization, automatically abort the job and alert the DIT.