Preparing Avid Media Composer Projects for Cold Storage Archival

What an Avid Cold-Storage Archive Must Preserve

A cold-storage archive is an offline preservation package containing the Avid project, required media, supporting assets, and instructions needed to reconstruct the edit. Its acceptance test starts with a practical question: can another editor reproduce the approved sequence without production storage?

Copying the project folder leaves that question unanswered. Bins can reference managed media on shared storage, linked camera files on external volumes, and audio on local drives. Those references travel with the bins; the referenced files require their own preservation plan.

An editable project archive retains sequence structure and access to source media. A flattened reference export supplies a rendered comparison target. It cannot provide independently adjustable cuts, tracks, or effects, but it gives the restoring editor something concrete to check against.

Define the promised deliverable before copying begins: a reduced editorial package, a camera-original archive, or both. Record the handoff owner and the person responsible for accepting the restore. That decision sets the scope of every collection and verification step that follows.

Find the Media and Effects Your Sequences Still Depend On

An approved sequence plays cleanly from proxies. Its camera-original volume is absent. Playback establishes that the editorial media exists; a future conform still needs its own source check.

Start with approved sequence names and editable alternates, then trace their dependencies outward. Inventory source bins, project-specific settings, and the exact Avid Media Composer release used at wrap, including the maintenance version.

• Separate linked media, Avid-managed media, proxies, and camera originals.
• Locate external audio, imported graphics, title assets, fonts, and LUTs.
• Record third-party effect names, versions, presets, and availability concerns.
• Check original camera folders independently and document their relationship to editorial clips.

Give each dependency an asset description, current location, preservation action, and verification status. An entry reading “linked camera volume; production path; preserve complete folder; unverified” exposes unfinished work.

Recording an effect version does not preserve installation rights or future compatibility. Keep that distinction visible in the manifest, especially when the approved picture depends on licensed components.

Choose Consolidation or Transcoding Without Losing Source Options

Which media treatment preserves the promised archive? Consolidation, transcoding, and source-folder preservation solve different parts of that task. A package may need more than one.

Check the documentation for the installed release before processing linked formats. Available consolidation and transcoding options depend on the material and software; a choice available for one format should never be assumed for another.

Sequence-selected media with handles keeps used ranges plus material around edits. Complete source clips preserve more replacement-shot and recutting options at a larger storage cost. Where recordings depend on sidecars, metadata directories, or spanned segments, preserve complete camera-folder structures and their internal names.

New editorial transcodes must never silently replace irreplaceable originals.

Build the Archive Media Set and Check Mixed-Frame-Rate Shots

Build a representative trial before processing the full archive. Linked sources, mixed-rate clips, retimes, transitions, and synchronized audio belong in that trial because they expose the decisions most likely to affect reconstruction.

1. Duplicate the project for archive preparation, keeping the production project separate.
2. Select the approved sequence versions and required editable alternates.
3. Establish a separate archive-media destination.
4. Record the proposed treatment, codec where applicable, handle setting, and processing options.
5. Process the trial sequence, compare it with the approved edit, then proceed with the remaining material.

Choose handles around the expected revision task and available storage. Record the actual setting and its units. “Standard handles” tells the next editor very little about the material available beyond a cut.

Keep Timing Decisions Visible

For each mixed-rate problem shot, record source rate, project rate, motion-adapter state, explicit speed effects, and an identifiable synchronization point. Preserving source timing and baking a frame-rate conversion create different future options. Conversion to project rate is not an automatic archival requirement.

Use the installed release’s terminology in the notes. Retain originals when transcoding changes temporal treatment, and inspect processed shots at speed changes, transitions, and audio sync points.

Package Bins, Managed Media, and Restore Notes Together

A restoring editor should be able to distinguish the project from its media without reconstructing the assistant editor’s desktop. An outer package can use these organizational folders:

• Project/: project files, bins, and project-specific settings.
• Managed_Media/: collected Avid-managed media.
• Linked_Sources/: preserved source folders with internal relationships intact.
• Supporting_Assets/: graphics, title assets, LUTs, presets, and component information.
• Reference_Exports/: identified sequence versions with guide audio and visible sequence timecode where appropriate.
• Documentation/: dependency manifest, restore instructions, and verification records.

These labels organize cold storage. Media Composer does not automatically discover managed media inside an arbitrary nested archive folder.

For conventional local managed MXF storage, the working hierarchy is Avid MediaFiles/MXF/numbered folders at the drive root. Restore notes must explain which archived folders belong there. Other media types and shared-storage configurations need their appropriate organization.

Document approved sequence names, archive scope, software version, media treatments, handles, original locations, omissions, and required external components. Preserve project settings separately from personal preferences, account credentials, and unrelated workstation configuration.

Restore Without the Original Drives Before Signing Off

Can the archive stand alone while production storage remains mounted? That environment cannot establish independence: healthy-looking bins may still resolve media from the original volumes.

Test from an archive copy with production shared-storage mounts and original source drives unmounted or otherwise inaccessible. Place managed media in its discoverable working layout, open the archived project, and relink preserved sources where necessary.

1. Inspect approved sequences for offline segments, incorrect source matches, missing titles, and unavailable effects.
2. Check audio-channel assignments and synchronization.
3. Verify relinks against available source identifiers, source timecode, duration, and picture content. Matching filenames alone cannot establish the correct recording.
4. Compare playback or a restored export with the approved reference, concentrating on mixed-rate shots, retimes, transitions, and sequence starts and ends.

Record the test date, operating system, Media Composer release, component versions, restored sequence names, exceptions, outcome, and accepting editor. Keep unresolved exceptions visible in the handoff. A successful isolated restore demonstrates reconstruction in that recorded environment; future releases may handle components differently.

Verify the Stored Copies and Leave a Usable Handoff

File-integrity verification and an isolated Avid restore answer separate questions. Matching checksums establish that copied files agree with the manifest. The functional test establishes whether the preserved project can reconstruct the edit.

After finalizing the contents and restore notes, generate a SHA-256 manifest recording each covered payload file’s relative path and digest. Store it alongside the package, document its coverage, and compare destination checksums after copying. Regenerate the manifest whenever covered files change.

Keep independent copies in separate locations under the organization’s retention policy. A single disconnected drive remains a single point of failure.

For tape storage, retain the archive system’s verification result, catalog or retrieval identifier, and retrieval procedure. A successful write operation cannot substitute for a functional restore test. Label the package with project identity, archive date, contents, and locations of its manifest and restore notes; assign an owner and a dated retrieval-check schedule.

Accept the archive after both integrity verification and the isolated restore pass. The decisive fact sits inside every bin: it preserves editing metadata and media references, while the source picture and sound remain in separate files.