Final Cut Pro to Nuendo or Cubase — and back.

Why Nuendo cannot open the Final Cut export

Nuendo and Cubase Pro import AAF. Neither reads FCPXML, and Final Cut Pro writes nothing else — it has no AAF import or export in any version. The AAF is the one format both ends hold.

Coming back is the same gap mirrored: an AAF from the mix is not something Final Cut can open, so that leg runs through AAF back into Final Cut.

Final Cut to Nuendo, step by step

1. Break apart compound and multicam clips

   Clip → Break Apart Clip Items. These clips do not expose their contents to any converter. Nesting is followed three container levels deep — on a deeply nested project that can cost most of the timeline. The report counts every clip that fell out, but fixing it in Final Cut is the only way to get the material back.

2. Export the XML from Final Cut Pro

   File → Export XML. A single .fcpxml or the .fcpxmld bundle — drop either one in.

3. Convert to .aaf with per-channel media

   Drop the file in and pick .aaf. Under Channels, switch on Separate combined channels: every channel is written as its own mono file while the tracks stay stereo — the delivery form for Nuendo and Cubase.

4. Collect the media

   Collect next to output gives you one folder to hand over — Name/Name.aaf plus Name/Media/. MXF-wrapped audio becomes WAV automatically.

5. Import in Nuendo — and read the report

   File → Import → AAF. The report next to the output is a loss list, not a clean bill — read it before the turnover goes out.

6. Coming back: the mix into Final Cut

   The returning AAF converts to .fcpxml or the .fcpxmld bundle — audio on role-named tracks, volume keyframes, overlapping blends. See AAF back into Final Cut.

What travels — and what does not

• Audio positions — in samples on AAF’s 48 kHz timeline grid, not quantised to frames.
• Volume automation as real AAF curves, fades, crossfades and clip gain — a level at or below −96 dB is read as a true mute.
• Named markers are written into the AAF.
• Stereo stays stereo — and if the picture editor handed you a pair split across two mono tracks, Combine split stereo tracks puts it back together, with a review window before anything is written.

What does not come along: pan — Final Cut’s panner is neither read nor written here. Track and clip colours ride in a private AAF comment that only this converter reads back. Exact track names give way to roles on the return leg, and empty tracks have no representation in FCPXML.

We open the AAFs we write in Nuendo ourselves. AAF dialects differ between applications, so convert one reel with the demo and open it on your own system before a delivery depends on it.

FAQ

Does this work with Cubase as well as Nuendo?

AAF import is a Cubase Pro and Nuendo feature; the smaller Cubase editions do not have it. The file is the same either way.

Should I switch on Separate combined channels?

Yes — switch it on for Nuendo and Cubase deliveries too. Every channel is written as its own mono file while the tracks stay stereo; that is the form to hand over.

My stereo arrived as two mono tracks. Why?

Then the split happened before the conversion — some editors deliver a pair that way. Switch on Combine split stereo tracks and confirm the pairing in the review window.

Can I convert a whole show at once?

Yes — hand it a batch of project files, pick one target, convert. Each file gets its own status and its own report.

Related