Premiere to Pro Tools AAF: separate voices, media and audio handles

The sound editor asks for 240-frame handles: how much audio is that?

Handles are additional audio before and after the portion used in the edit. They let you extend a cut or work on a transition. Their duration depends on the sequence frame rate.

In Export AAF files, August 18, 2026, Adobe documents Render > Trim Audio Files and Handle Frames for this extra audio. Copy Complete Audio Files delivers the full source files. Confirm what the sound editor needs and record the handle value together with the frame rate. The table converts frames to seconds.

Twelve multicam channels become a stereo export

Adobe’s AAF help specifies Breakout to Mono for a Pro Tools handoff; it splits stereo into Left and Right. To check the result, choose a segment where each voice is recognizable and compare the source file, the sequence and the recipient’s import. The number of tracks does not prove that all twelve contain different sources.

If a voice is missing or duplicated, return to the first stage where it changes. Use the multicamera and audio guide to check channel mapping before exporting again. Before turning the entire talk into a stereo mix, agree on which sources the sound editor needs to retain.

Merge Clips, nested sequences and multicam need different checks

Adobe’s AAF help states that merged clips are unsupported and must be unmerged before export. That restriction is not a general ban on exporting multicam sequences.

The 2022 Adobe guide, Audio Turnover, p.118 recommends making a sequence copy, organizing dialogue, music and effects, and unnesting audio from ordinary nested sequences. It also describes multicam sequences being flattened automatically during AAF export. Page 119 warns about Merge Clips metadata. Adobe links to this PDF from its help site, but it is not a manual for a 2026 build.

Before changing a complex edit, export a sample from a copy and verify its sources at the receiving end. If you compare a differently prepared version, use the same segment and give the packages distinct names. Preserve the previous state and record what changed; automatic flattening does not replace checking every voice after import.

Deliver the AAF, media and reference as one package

The Adobe guide, p.118 includes a reference video with burned-in timecode. Agree on its format with the sound editor, identify the picture version and include the voice map. If the edit changes, record where it changed and identify the new version before replacing the reference.

In Premiere, File > Export > AAF opens the export settings. Separate Audio places the media alongside the AAF; Broadcast Wave includes iXML. On Intel and Arm Windows systems, Adobe limits an AAF with embedded audio to 2 GB and specifies separate audio for larger exports. Keep the generated folder with the interchange file.

Record the Render audio clip effects setting. If you print the effects, Include clip copies without effects also provides copies without those effects. Verify which version the sound editor imported and which processing is audible; do not assume that all plugins and automation transfer intact.

Choose Sample Rate and Bits per Sample as agreed. Save a screenshot of the settings and give each package a versioned name. The event recording delivery guide covers the media inventory and preserving originals.

Import the sample in Pro Tools and check both sides of each edit

The Avid Pro Tools 2026.4 manual, chapter 22, pp.676–680 documents File > Import > Session Data for an existing session. Create a local test session and review the selected tracks, Audio Media Options, Timecode Mapping, Track Offset and sample rate conversion before accepting. If a warning appears, save the report offered by the importer.

To test without relying on the received folder, select Copy from Source Media and a new destination. The manual distinguishes copying from linking and consolidating: a linked session may still depend on the received media location. Record the option you used and the paths from which the media plays.

On p.679, Consolidate from Source Media trims the copies, and Handle Size is expressed in milliseconds. If you need to consolidate, agree on that margin: do not copy “240” from Premiere as if the units were the same. For example, 240 frames at 25 fps equals 9,600 ms. Check the available handles again after importing.

Listen to each microphone in a recognizable passage. Compare the edits with the reference video and try extending an edge in a copy, up to the agreed margin available in the source. Check the beginning, a late contribution and the end. Record what you verified and any missing sources.

Keep a record of what the sound editor received

Fill out the blank AAF and audio receipt worksheet. Include both application builds, frame rate, the source of each voice, settings, reference and checked passages.

This guide covers interchange checks. Coordinate the channel map from capture onward with cameras and streaming and audio systems. If you deliver a project or WAV files for another application, also review the delivery workflows and test the format that recipient accepts.

Picture changed after the mix: document the differences between versions

If picture changes after mixing, identify the revised edits before importing new audio over the mix session.

The 2022 Adobe guide, Change Lists, p.119 describes a list of changes between two versions and explains that there is no single format. Agree on the information the sound editor will receive. Keep the old and new references with guide audio, version identifiers, frame rate and start timecode.

For a shortened talk, log each removed, added or reordered segment with its position in both versions. Also note changes to music, ambience or a voice even when the picture stays the same. “We shortened the talk” is not enough to locate the remaining work.

If the sound editor requests an EDL, Adobe documents activating the Timeline, choosing File > Export > EDL and selecting tracks in EDL Export Settings (CMX 3600). Save each version separately and record which tracks you included. The help recommends simple sequences, ideally one video track and two stereo audio tracks without nesting. Have the recipient check the file; exporting it does not prove that they can reconstruct every change.

An EDL for one version and a list of differences serve different purposes. For the test, compare an unchanged passage, a trimmed passage and a new passage against the references. Even if only the total duration changed, do not assume you can shift the entire mix by one frame offset: edits may occur at several points.

The AAF lands on the right tracks but changes routing or plugins

For Pro Tools 2026.4, chapter 22, pp.667–669 documents Track Data to Import > Choose. Selected attributes replace the corresponding destination attributes; attributes you do not import are retained. Before accepting, decide what should come from the AAF and what belongs to the existing mix.

Make a session copy and record the outputs, sends, plugins and automation on a sample track. To preserve those elements, exclude their attributes from the import and verify that they remain afterward. The table identifies controls in the manual; it is not a complete preset for every AAF.

Match Tracks and Overlay: check destination, content and timing separately

The 2026.4 manual, pp.664–665 distinguishes importing to a new track from choosing an existing one. Match Tracks requires matching names, types and channel formats; it does not compare picture edits. For the initial test, import the segment onto new tracks in a session copy and listen against the reference. Then agree on what should move to the mix tracks.

Under Main Playlist Options, p.673, referenced for AAF on p.683, Import – Replace Existing Playlists replaces the destination main playlist. Import – Overlay New On Existing Playlists trims and replaces material where the new material overlaps, leaving non-overlapping material intact. Before using Overlay, check which passages overlap the previous edit.

Also review Timecode Mapping and Track Offset, p.680. Absolute retains source positions; Relative retains the offset from session start; Map Start lets you choose another start time. The manual states that Absolute is disabled if the AAF starts later than the current session. Record the dialog options and warnings, then compare the edit and its automation against the picture change list.

Compare a voice in an unchanged passage, the edge of a trimmed passage and an added contribution. Also check outputs, plugins, levels and pauses. If something differs, record the first point and the version change that caused it before importing the rest.

Fill out the blank picture changes and import worksheet alongside the receipt worksheet above. Coordinate any new material to record or deliver with cameras and streaming and audio systems.

Tracks and edits appear, but the clips have no audio

If tracks and edits appear but audio is missing, first check whether the media is included and whether Pro Tools can find the correct files. Importing into another session does not replace that check.

Record the exact warning and which files the importer requests. Check the received inventory: AAF, audio folder and picture reference. If the expected folder is missing, request the complete package before looking for a different take with a similar name. If the folder is present, try opening one source from a copy, then use relinking to check which file the session expects.

Adobe, Export AAF files, August 18, 2026 distinguishes Embed Audio from Separate Audio; the latter creates a folder alongside the AAF. Breakout to Mono generates new mono audio, and Adobe specifies enabling it for Pro Tools. Record both controls: embedding or separating media does not replace the channel decision.

Record the Premiere build and export settings for the failing package. Adobe’s help supports both delivery methods and limits embedded AAFs larger than 2 GB on Intel and Arm Windows systems. Agree on the package with the sound editor and verify a sample at the receiving end.

Relink cannot find the audio, or suggests a different file with the same name

The Pro Tools 2026.4 manual, Missing Files and Relink, pp.523–528 explains how to search for and verify missing media. Start with a session copy. If Missing Files appears, choose Manually Find and Relink. From an open session, the manual also lets you select the offline file in Workspace and use Relink Offline.

In Areas to Search, include the received folder and check the Search column. Select a source in Files to Relink: Find Links becomes available once files are selected. Record the Linking Options criteria; the default search uses name and ID. If no candidates appear, first check that the expected file is in the package and in a folder included in the search.

The manual lists Find By Name, Find By File ID and Find By Name And File ID. If you try another criterion, keep the search narrow and verify each result. A matching name does not prove it is the same take. Match Duration accepts files of the same duration or longer; it does not require identical duration.

Check the candidate’s Link Path, properties and waveform. For a source with multiple copies, use Find All Candidates and compare them before choosing. Record the expected file, proposed file and search criterion that found it. If the original is missing or you cannot identify the take, leave the link unresolved and ask the editor for a verifiable source.

Commit Links confirms the selected links. Page 528 states that relinking cannot be undone and saving retains the new link. Automatically Find and Relink commits without the prior review available in manual mode. Keep the previous session; after the test, listen to recognizable voices and compare edits with the reference.

Once the audio is identified, prepare the transfer with File > Save Copy In and include the audio files in use, as described on pp.232–235. Save As changes the session file but can continue using the same Audio Files folder. Save Copy In also excludes media removed from the session even if it remains on disk, so preserve originals separately. Open the resulting copy and verify paths and playback from that destination.

The worksheet records the search, candidate and verification separately. Prepare a copy and agree on the relinking test with the sound editor.

The same AAF fails in two applications: compare the handoff before changing the edit

An AAF failing in two applications does not by itself identify the cause. Compare which media or edit fails in each destination before changing formats or passing the file through another application.

For a conference or interview, distinguish the symptom: offline file, wrong voice, shifted edit or duplicate region. Ask the editor for a sample with a recognizable voice and identical in and out points; identify each package and its reference. If you compare another agreed format, record its settings and check exactly the same edits and sources at the receiving end.

Record the first passage that differs, not just “the AAF fails.” Preserve the original effects, transitions and structure before preparing variants; do not remove them throughout the edit based on a recipe from another project. With that sample and the import report, the editor can investigate a specific difference. Conversion through Logic or Resolve requires documentation for the installed versions; this guide does not cover that procedure.

Fill out the blank media and relinking worksheet. To return to the source files, use the proxies and originals guide. Coordinate delivery with cameras and streaming and the voice map with audio systems.

Some voices lose gain: identify which adjustment should have transferred

Before exporting again, record where the level adjustment was made. Adobe, Audio Gain, January 21, 2026 shows the control by selecting the clip and opening Audio Gain from its context menu. Show Keyframes, January 21, 2026 distinguishes Clip Keyframes from Track Keyframes. Record values, points and source: “we turned up the voice” does not identify the operation to compare.

In Pro Tools 2026.4, p.682, Import Clip Gain and Import Volume Automation select different data. Review both controls as agreed and save the settings. To display clip gain, the manual specifies View > Clip > Clip Gain Info and Clip Gain Line, pp.1250–1251; the line requires a track height of Small or greater. Also compare track volume automation before concluding that nothing transferred.

For a test, request a sample containing one affected voice and one that transfers correctly, with identified source level adjustments and an audible reference. Import them into a copy and compare the same passage: which data appears, which change you hear and where it differs. If the adjustment arrived as automation, discuss how the sound editor needs to work with it. If it is absent in both forms, converting existing data will not recover it.

If the levels differ, save the source values, import settings and first affected passage. This comparison lets you investigate the export without changing the entire mix.

Convert, Coalesce and Render Clip Gain change different data

The Pro Tools 2026.4 manual, pp.1256–1257 documents Convert and Coalesce between clip gain and volume automation for Studio and Ultimate. Confirm the edition and version before looking for these commands. They reorganize data already present; they do not prove that Premiere exported a missing adjustment.

To move received automation to clip gain, select a clip or range in a copy and review Edit > Automation. Convert moves data from one form to the other. Coalesce combines it with the destination data; when moving volume to clip gain, it sets volume automation to 0 dB within the selection. Inspect both curves first and agree on what to preserve.

The table summarizes the manual’s operations and checks to make. Compare before and after against the same reference, and review only the selected passage before extending the operation.

When converting or coalescing clip gain to volume, the manual warns that settings above +12 dB are lost and gain within crossfades becomes part of the automation. That limit applies to this direction of conversion. Keep the previous copy and review those points. Page 1257 also provides Bypass Clip Gain to audition without the adjustment, without deleting it.

Render Audio Clip Effects preserves a sound: verify what the sound editor received

Adobe, Export AAF files, August 18, 2026 describes Render audio clip effects as processing rendered into the audio files. With that option selected, Include clip copies without effects adds clean copies on another track. This does not promise to reconstruct an editable plugin chain at the destination. Identify which effects were applied to clips and which processing was on tracks or buses; agree on the sound to preserve and what the sound editor needs to rebuild.

For a Pro Tools destination, the 2026.4 manual, p.681 distinguishes Import Rendered Audio Effects: enabling it retains rendered effects; disabling it imports the unprocessed source according to the interchange. Record the option and the files contained in the package. Do not treat the checkbox alone as proof that you delivered originals: identify and audition each version.

Test a short passage with a recognizable effect. Compare the Premiere reference, processed version and clean copy at the destination, using the same positions and a comparable monitoring level. If the effect is audible but no plugin appears, that alone does not establish a rendering failure. If it is inaudible, check which track and variant you imported before repeating the full delivery.

Gain can also be rendered into the audio: Render Clip Gain in Pro Tools creates a new clip and sets its gain control to 0 dB, p.1257. Seeing 0 dB does not prove that the audio is unprocessed source media. Keep originals and distinct names for every variant.

Fill out the blank AAF gain and effects worksheet. Agree on references and variants with cameras and streaming and audio systems; the recording delivery guide covers the inventory and source preservation.

The clip will not extend: check where the available audio ends

Identify the source application and versions before comparing export and import controls.

Ask the editor to identify a specific cut and compare the audio available before and after it in the original source and the delivered file. Record both margins separately. A recording start may have no earlier audio even if a handle was requested; increasing an export value cannot create missing material.

For a Premiere source, Adobe, Export AAF files, August 18, 2026 distinguishes Copy Complete Audio Files from Trim Audio Files with Handle Frames. If the package has already trimmed the source, request a new sample with the agreed handles.

Also compare the copy Pro Tools created. In 2026.4, p.679, Consolidate from Source Media removes unused areas from the copies and retains the selected Handle Size in milliseconds. Avid recommends at least 1000 ms to extend edits that sound cut off; this is not a sufficient margin for every handoff. If the package contains more audio than the consolidated copy, review the import. If the audio is missing from the package, return to the editor.

To test in a copy, place a clip on a test track with no neighboring clips and select the entire clip. The manual, p.919, provides Edit > Trim Clip > To File Start, To File End and To File Boundaries. These commands extend to the referenced file’s boundaries but stop at neighboring clips on the same track. Record the audio revealed at each end; a neighbor can limit extension even when source audio is available.

Preserve the original edit, compare the same cut before and after receiving the new package, and listen to a word and its surrounding ambience.

Crossfades are missing after import: check media, position and curve

If crossfades are missing after import, check the available audio, transition position and curve separately. A missing fade does not prove that the clips lack handles.

Adobe’s AAF help states that transitions appear between two clips and requires each clip to be at least as long as the transition. With transitions at both ends, the clip must cover their combined duration. Record whether the affected transition is between clips or at an end, along with duration and frame rate. These limits apply to the cited help; for an earlier version, check its documentation and a project sample.

In Pro Tools 2026.4, pp.928–929, a crossfade requires overlapping material beyond the edited boundaries. If there is not enough, the application offers to skip the fade or adjust the selection. Before accepting a change, record the warning and check which source lacks the needed margin. The table distinguishes the media needed for each position; it does not prescribe a single duration.

To rebuild a transition in a copy, use the Selector to select the range around the splice and choose Edit > Fades > Create. The manual, pp.928–934, lets you inspect and audition the curve before applying it. Record duration, position and Link. Avid recommends Equal Gain for phase-coherent or nearly phase-coherent material and Equal Power for material that is not; do not apply the same curve to every splice just because the durations match.

Compare the received cut, editor’s reference and test variant at the same monitoring level. Listen for clicks, a word losing its attack, or a level dip or boost at the splice. If the surrounding audio is available but AAF transitions are missing, record the first affected cut and request a new sample with its settings. Do not infer missing handles solely from an absent fade.

Fill out the blank handles and crossfades worksheet. Include the test in the recording handoff and coordinate sources and review with cameras and streaming and audio systems.