How to Match a Reference Edit Back to Original Source Footage

When you have a flattened reference video and the original source footage, rebuilding the edit means identifying which source clip was used for every cut and locating the exact source frames.

This process is commonly described as source matching, eye-matching, overcutting, or rebuilding a source-based conform from a flattened reference.

CutMatch is designed to automate the visual source-matching portion of that workflow. It compares the shots in a reference edit against the available source media, identifies likely matching clips and frame ranges, and exports a source-referencing CMX3600 EDL for conform and finishing.

The same workflow applies whether you are rebuilding a trailer from a longplay, matching an offline edit back to camera originals, reconstructing an edit from a reference export, or working with source media whose editorial metadata no longer provides a reliable path back to the original footage.

When do you need to match a reference edit to source media?

The exact situation varies, but the underlying problem is usually the same:

Common use cases include:

Trailer and marketing conforms

A trailer, promo, commercial, social cutdown, or marketing edit may be supplied as a flattened reference rather than as a source-linked timeline.

If the original feature, episode, longplay, or other source material is available, each shot in the reference needs to be matched back to the corresponding source before the edit can be properly conformed or finished.

Traditionally, an editor or conform artist does this manually by eye: locate the shot, find the matching frame, determine the source in and out points, and rebuild the sequence event by event.

Matching offline or proxy edits back to original camera media

Editorial may have used proxies, compressed dailies, downscaled media, or other offline files while finishing requires the original camera footage.

Normally, filenames, source timecode, reel metadata, XML, AAF, or another interchange format can reconnect the edit to the originals.

When those relationships are missing, inconsistent, or no longer reliable, the visual content of the approved reference can provide another way to match the edit back to the original source media.

Rebuilding from a flattened reference

Sometimes a post-production team receives:

• an approved reference video;
• the original footage or longplay;
• but no usable source-linked timeline.

The editable project may exist elsewhere, may not have been included in the handoff, may be incompatible with the finishing environment, or may no longer be available.

The source-matching problem is the same regardless of why the metadata is unavailable: identify the original clip used for each reference shot and determine its exact source frame range.

Moving an edit between editorial and finishing environments

An edit may originate in Premiere Pro, Final Cut Pro, DaVinci Resolve, or another editorial system and ultimately need to be reconstructed for conform or finishing.

When a clean XML, AAF, EDL, or project interchange is available, that should generally be the first choice.

But if the transferred metadata does not reliably identify the available source media, visual source matching can help rebuild the relationship between the reference edit and the originals.

Reversioning, remastering, archival, and older edits

Existing finished material sometimes needs to be rebuilt from the original footage for a new version, higher-quality master, localization, archive, restoration, or client revision.

The original project does not necessarily need to be “lost.” It may simply be easier or more practical to work from the approved reference and available source media.

Reconstructing an edit from a finished video and the original clips

Another variation is having:

• a finished MP4, MOV, or MXF;
• a collection of the original recordings;
• and no usable timeline identifying which portions of those recordings appear in the finished edit.

The finished video can first be divided into its individual shots. Those shots can then be matched against the original footage to reconstruct a source-based edit.

The reference-to-source matching workflow

The overall workflow is:

Flattened reference → cut-list EDL → visual source matching → source-referencing EDL → conform

There are two distinct problems to solve:

1. Where are the cuts in the reference?
2. Which source clip and frames correspond to each cut?

CutDetect handles the first problem. CutMatch handles the second.

Step 1: Identify the cuts in the reference video

CutMatch works from reference events described by a cut-list EDL.

If you already have an EDL whose events accurately describe the cuts in the reference, you can use it directly.

If all you have is a flattened MP4, MOV, MXF, or other reference video, the first step is to identify the edit points.

CutDetect analyzes a flattened reference video for hard cuts, lets you review and correct the detected edits, and exports a CMX3600 cut-list EDL.

For a detailed walkthrough, see How to Detect Scene Cuts and Generate an EDL from a Reference Video.

The result is an EDL describing where each reference shot begins and ends.

It does not yet identify the original source footage.

Step 2: Match the reference edit back to the source footage

Load the reference video, its cut-list EDL, and the available source media into CutMatch.

CutMatch generates compact visual signatures from reference and source frames and compares them across the source pool.

For each reference event, the goal is to determine:

• which original source clip contains the shot;
• where the matching source frames occur;
• the correct source in and out points;
• and whether other candidate matches should be considered.

This replaces much of the manual searching normally required when eye-matching a reference edit to source media.

The result is not simply “these two clips look similar.” The useful output is a source identification and frame range that can be written back into a conform-ready EDL.

Step 3: Review the proposed source matches

Visual matching should still be reviewed before the conform is considered complete.

Source media may contain:

• alternate takes;
• repeated performances;
• similar camera angles;
• duplicated media;
• repeated frames;
• graphics or text overlays;
• reframing;
• baked color treatments;
• or shots that are not present in the supplied source pool.

CutMatch presents the reference event beside the proposed source match so the editor can inspect the result, review alternate candidates, manually assign a different source, or adjust the source offset when necessary.

A good match should remain consistent across multiple frames, not merely resemble the reference in a single still.

Step 4: Export a source-referencing CMX3600 EDL

Once the matches have been reviewed, CutMatch can export a CMX3600 EDL containing the identified source clips and source timecodes.

That EDL can then be imported into DaVinci Resolve or another compatible finishing workflow and connected to the original source media.

The result is a source-based reconstruction of the reference edit rather than a timeline containing only the flattened reference video.

CutMatchFrame-signature source matching and source-referencing EDL export for Mac.

Step 5: Compare the rebuilt conform against the reference

The flattened reference should remain the visual authority during the final conform check.

Place the reference above the reconstructed source timeline and compare:

• shot identity;
• event boundaries;
• source in and out points;
• duration;
• motion phase;
• scaling and reframing;
• and any editorial treatment that needs to be restored.

Difference, wipe, split-screen, or similar comparison methods can help identify events that require additional adjustment.

Why use visual source matching?

Traditional conform workflows are strongest when the editorial metadata remains intact.

That may include:

• source timecode;
• reel names;
• original filenames;
• stable media relationships;
• XML;
• AAF;
• or source-referencing EDLs.

When that information correctly identifies the original media, there is no reason to replace it.

Visual source matching becomes useful when the images clearly correspond but the metadata connecting the reference to the available source footage does not.

Instead of asking “Which source file has the right filename, reel, or timecode?”, the matching process can ask “Where does this actual image from the reference appear in the original footage?”

That is why the same technique can solve several otherwise different conform and reconstruction problems.

Matching proxy or offline footage to camera originals

The reference and source media do not always need to be identical encodes.

For example, an offline edit may have been created from lower-resolution proxy files while the conform uses higher-quality camera originals.

The reference may also differ from the source in compression, resolution, moderate scaling, reframing, flipping, or color.

Because CutMatch compares visual frame information rather than depending entirely on filenames or editorial metadata, these workflows may still be matchable when enough of the underlying image remains recognizable.

The final result should always be reviewed against the reference.

What CutMatch can and cannot rebuild

CutMatch focuses on reconstructing source-based picture events.

If a reference event corresponds to a particular section of an original source clip, CutMatch can help identify that clip and determine the corresponding source frame range.

It does not recover the original NLE project.

That means it does not reconstruct every:

• effect;
• keyframe;
• transition;
• title;
• graphic;
• audio edit;
• mix decision;
• color grade;
• composite;
• or other operation that may have been applied to the underlying source shot.

The source-matched timeline should therefore be treated as the reconstructed picture foundation for conform and finishing, not as a forensic recreation of the original Premiere Pro, Final Cut Pro, or DaVinci Resolve project.

What kinds of reference edits work best?

CutMatch currently works best when the reference consists primarily of recognizable source shots connected by straight cuts at normal speed.

Matching can become more difficult when the source image has been heavily transformed.

Examples that may require manual attention include:

• speed changes or retiming;
• dissolves and fades;
• heavy reframing or cropping;
• complex compositing;
• split screens;
• graphics covering significant portions of the source image;
• heavily altered source imagery;
• and source material that was never supplied.

These events can be handled as exceptions during the final conform pass.

Does CutMatch replace XML, AAF, EDL, or normal relinking?

No.

If reliable editorial metadata already connects the edit to the correct source media, use it.

Visual source matching is most useful when the visual relationship is intact but the editorial relationship is not.

CutMatch is therefore complementary to traditional conform methods rather than a replacement for them.

Does CutMatch use AI to identify the source footage?

CutMatch performs its source matching locally on the Mac and does not require an LLM or cloud AI service for the matching process.

Reference footage and source media do not need to be uploaded to an AI API in order to search for source matches.

This can be particularly useful when a production contains a large source pool or when local media processing is preferred.

Source matching, eye-matching, overcutting, and conforming

Different post-production environments use different terminology for closely related parts of this workflow.

Source matching means identifying the original media and frame range corresponding to a reference shot.

Eye-matching usually describes manually finding that correspondence by visually comparing the reference and source media.

Overcutting often describes rebuilding a flattened edit by placing the original source shots over the reference.

Conforming is the broader process of reconstructing the final sequence using the correct source media and editorial decisions.

CutMatch focuses on automating the visual source-matching step.

Example: rebuilding a trailer from a feature or longplay

Consider a 90-second trailer supplied as a flattened reference.

The original feature is available, but the trailer timeline does not contain usable links back to the source.

A manual conform artist would need to repeatedly:

1. identify a reference shot;
2. search the feature or source pool;
3. locate the matching frame;
4. determine the source in point;
5. determine the source out point;
6. rebuild the timeline event;
7. and repeat the process for every cut.

With CutDetect and CutMatch, the workflow becomes:

Trailer reference → CutDetect creates the reference EDL → CutMatch matches the reference events → matches are reviewed → CutMatch exports a source-referencing EDL → conform and reference check

The same process can be used for promos, commercials, episodic marketing, social versions, offline-to-online workflows, archival edits, or other flattened-reference conform jobs.

When is CutMatch a good fit?

CutMatch is a strong fit when:

• you have a flattened reference edit;
• you have the original source footage, longplay, or camera media;
• the reference consists primarily of recognizable source shots;
• normal metadata-based relinking is unavailable or incomplete;
• manually finding every source shot would be time-consuming;
• and you want to rebuild source-based picture events for conform or finishing.

CutDetect + CutMatch

If you already have an accurate reference cut-list EDL, you can begin with CutMatch.

If all you have is the flattened reference video, CutDetect can first identify the hard cuts and create the reference EDL.

Flattened reference → CutDetect → cut-list EDL → CutMatch → source matches → source-referencing EDL → conform

CutDetect

CutDetect for Mac detects hard scene cuts in reference videos, provides visual review and correction tools, and exports CMX3600 EDLs.

Read the scene-cut detection and EDL workflow guide →

CutMatch

CutMatch for Mac visually matches reference events to the original source media, supports candidate review and manual adjustment, and exports a source-referencing CMX3600 EDL.

Test your media with CutMatch

Different references and source pools can vary substantially in how well they match.

The practical way to determine whether a particular job is suitable is to test representative material.

Explore CutMatch for MacSee the workflow, watch the demonstration, download CutMatch from the Mac App Store, or try CutMatch Preview for free.