An AAF file functions as a professional edit-transfer format for film/TV and similar workflows, allowing edits to move between applications without rendering a completed video, instead storing the structure of the timeline—tracks, clip positions, edits, ranges, and transitions—along with metadata like timecode, clip identifiers, and sometimes markers, plus simple audio traits such as gain settings, and it can be exported as a reference-based file or with embedded or consolidated media to reduce missing-media issues.

The most typical use of an AAF centers on moving the cut into audio post, where an editor exports the sequence so the audio department can load it into a DAW, restore the session layout, and work on dialogue, SFX, music, and mixing while checking sync against a reference video with burn-in timecode and often a 2-pop; one common issue is offline or missing media despite a successful import, meaning the DAW reads the timeline but can’t locate or decode the referenced files because only the AAF was delivered, directory paths differ between systems, assets were renamed or rewrapped, linking was chosen instead of copying, or incompatible codecs/timebases were used, so the most reliable method is delivering a consolidated AAF with handles plus a separate reference video.

When an AAF imports structure but not the underlying media, it means the edit data arrived—track mapping, clip positions, edit references—yet the application cannot locate or read the audio/video files themselves, resulting in empty waveforms or silent playback; this typically stems from a reference-only export without accompanying media, path differences across systems, media renamed or moved post-export, or unsupported codec/container types in the receiving software.

Less frequently, differences in project settings—like mismatched sample rates (44.1k vs 48k) or timeline timebases (23.976 vs 24/25/29.97, drop vs non-drop)—may introduce relinking problems or odd reconnection behavior, and although relinking by directing the app to the right media directory usually solves it, the safest approach is exporting an AAF with copied/consolidated or embedded audio and handles, along with a separate burn-in reference video for sync checking.

Here's more info on AAF file format have a look at the webpage. An AAF file (Advanced Authoring Format) serves as a professional interchange tool for moving a timeline-based edit between post-production apps—most commonly when handing a picture cut to sound post—and instead of behaving like a final MP4, it works as a portable edit blueprint that outlines track structure, clip placement, in/out points, cuts, and simple fades or transitions while also carrying metadata like clip names and timecode so another program can rebuild the timeline, with optional basic audio data such as level adjustments, pan, and markers, though complex effects or third-party plugins rarely transfer properly.

The big distinction between AAF types is how media is handled: a linked/reference AAF only references external files, making it lightweight but fragile if folder paths or filenames change, while an embedded/consolidated AAF includes the audio (often with handles) so the recipient can work without repeated relinking; this is why an AAF can open but still show offline media—the timeline came through, but the system can’t find or read the sources because files weren’t delivered, paths differ (common in Windows↔Mac workflows), media was renamed or moved, codecs aren’t supported, or project settings like sample rate or frame rate don’t align, and the usual solution is relinking with the preventive measure of exporting consolidated audio plus handles alongside a burn-in reference video.

What an AAF stores can be viewed as two layers: the timeline "recipe" plus metadata, and the optional media itself—the first layer is always present and outlines tracks, clip placements, cuts, transitions or fades, and metadata like names, timecode, and source references, sometimes including simple mix/editorial info such as volume tweaks, pan, fades, or markers, while the second layer is optional, ranging from linked/reference-only AAFs that just point to external media (small but prone to offline issues if paths don’t match) to embedded/consolidated AAFs that copy the needed audio—often with handles—so the receiving team can adjust edits without requesting a new export.