FCP Workflow Extension: Two-Way Sync Between Final Cut Pro and AVScript

The round-trip between Final Cut Pro and a cloud editing platform has always been painful. You export FCPXML. You navigate to AVScript. You import. You do your annotation work. You export again. You go back to FCP. You import again. At some point you lose track of which version is canonical, and you’re doing file management instead of editing.

The AVScript FCP Workflow Extension removes most of that friction. It lives inside Final Cut Pro as a native Workflow Extension. There is no context switch. There is no file manager open on the side. The bridge between your FCP library and your AVScript cloud is a panel that docks in your existing FCP interface, right next to your browser and inspector.

This post is a full walkthrough of what the extension does and, in particular, how the Sync FCP Edit feature works — the one that auto-detects your library, shows you all your FCP projects, and lets you register them in AVScript with a single tap.

The Extension, in One Sentence

The AVScript FCP Workflow Extension is a panel inside FCP that gives you two things: a Projects tab to import AVScript edits into FCP, and a Sync FCP Edit flow to push your FCP library into AVScript.

Both directions. No file manager. No manual FCPXML wrangling.

To install: AVScript.app ships with the extension bundled. Install AVScript.app, then open Final Cut Pro, go to Window → Extensions → AVScript, and the panel appears.

Requirements: macOS 13+, Final Cut Pro 10.6.5+.

The Problem This Solves

Here is a real scenario that happens on almost every documentary or long-form production that uses both FCP and a cloud annotation platform:

You’ve been cutting in FCP for three weeks. You have a library with fourteen FCP projects across four events — rough cuts, selects, interview sequences. You want to upload those sequences to AVScript so Story AI can transcribe everything and your producer can review the cuts in a browser.

Without the extension, this means: export each project as FCPXML, one at a time. Open AVScript. Create a project. Import the FCPXML. Repeat for all fourteen projects. Then, when AVScript sends you annotated metadata back, export that FCPXML and re-import it into FCP. Repeat.

It’s twelve to twenty manual steps for something that should be automatic.

With the extension, the same outcome is: tap Sync Edit, confirm the library, check the projects you want, tap Create. AVScript reads the library structure directly, creates all the projects in one go, and links them to the files already in your cloud library. The metadata roundtrip back into FCP is a single tap on a project row.

Direction One: FCP → AVScript

Auto-detecting your library

Tap Sync Edit from the Projects tab. The extension scans ~/Movies for .fcpbundle files and identifies the library you have open in FCP. In most setups this is instant — FCP keeps your most recent library accessible, and the extension finds it.

If your library is stored outside ~/Movies, or if you want to sync from a specific exported package, you can supply the file manually: drop a .fcpbundle, .fcpxmld, or .fcpxml file onto the sync zone, or tap Pick file… to navigate.

Reading media status

Before you create projects, the Sync View tells you the cloud status of every file from the library’s Proxy Media folder. This matters because Story AI can only run on files that have been uploaded to AVScript.

What gets created

Each AVScript project created by Sync FCP Edit corresponds to one FCP project. The project name is taken from the FCP project name. Media is linked to whichever files are already in your AVScript library.

After creation, open any of the new projects in the AVScript web editor to:

• Run Story AI transcription and analysis
• Share a player link with your producer or client for browser review
• Use Story AI to build a sequence proposal
• Annotate with markers and notes

Direction Two: AVScript → FCP

This direction is simpler. In the Projects tab, every row in the list is an AVScript project. Tap any row.

The extension generates an FCPXML from that project’s current edit sequence and writes it to a temporary file. Final Cut Pro opens it automatically — no File → Import step, no file picker. The FCPXML appears in your active FCP library as a new event.

This is how you receive back a Story AI proposal, a producer’s sequence, or any edit that was assembled in AVScript. It lands in your FCP Library as a first-class event — clips, cuts, timecodes all intact. From there you work with it exactly as you would any other FCP sequence: pull clips, apply grades, adjust audio, deliver.

The Complete Round-Trip

Put both directions together and you have a continuous loop that keeps FCP and AVScript in sync without any of the manual file management that made the round-trip painful before.

The loop looks like this in practice:

1. Cut in FCP as normal. Generate proxies.
2. Sync FCP Edit — register your FCP projects in AVScript, upload proxies.
3. Run Story AI in the web editor — transcription, emotions, visual tags.
4. Share with your team — producer reviews in a browser, builds a sequence proposal in AVScript.
5. Tap the project row in the extension — FCP opens the AVScript sequence. You decide what stays.
6. Keep cutting in FCP. When the edit moves, repeat from step 2.

Neither side is the source of truth in isolation. Both are live. The extension is the bridge.

A Third Path: Drop a .fcpxmld

For the highest fidelity import — particularly when you want to bring your timeline’s connected clips and overlay B-roll into AVScript — there is a third option: export a .fcpxmld package from FCP (drag any FCP project from the Browser to the Finder), then drop that package onto the sync zone in the extension.

AVScript parses the full timeline XML from the package, including all connected clips that live on lanes above the primary storyline. This gives you the complete picture of your edit in AVScript — not just the primary storyline, but every piece of B-roll, every graphic, every connected audio clip you placed above the sequence.

Connected Clips and the Overlay Lane

When AVScript imports a timeline that has connected clips — B-roll and graphics placed above the primary storyline in FCP (lane ≥ 1 in FCPXML terms) — it renders them as a visual overlay lane.

The overlay lane is semi-transparent orange. It is read-only in AVScript — you cannot drag clips in the overlay lane, and they follow the order of the primary storyline beneath them. This is intentional: connected clips express spatial relationships in FCP that AVScript doesn’t attempt to re-implement. They’re visible so reviewers can see the full edit; they’re locked because the editing relationship belongs in FCP.

For producers and clients reviewing in a browser, this is exactly what they need: they can see that the B-roll is there, see what’s cutting over what, and give meaningful notes about the editorial structure — without needing FCP to be installed.

What Each Tab Does

The Projects tab is the primary tab for daily use, but the other tabs complete the picture of what you can do without leaving FCP.

Why the Extension Matters

The criticism of every cloud video platform aimed at professional editors is the same: it adds steps instead of removing them. You leave your NLE, you go to a browser, you do the work, you come back. Every transition is a context switch that costs time and focus.

The extension doesn’t solve every problem — you still need to upload your media, you still need to run Story AI before the metadata is there. But it eliminates the class of friction that comes from the roundtrip itself: the FCPXML export, the browser navigation, the import, the file management. The bridge between FCP and AVScript is now a panel tab, not a workflow.

The round-trip being easy changes what you do with it. When syncing is two taps, you sync more often. When syncing more often means your producer always has the current cut to annotate, you get better notes faster. When the Story AI results land in your FCP library as native metadata the moment you tap a row, you search your transcript instead of scrubbing the timeline. The extension doesn’t change the nature of the work — it changes the cadence.

→ How Story AI works · → For FCP editors · → MetaFlow: AI metadata into FCP, Premiere, DaVinci