DaVinci Resolve and AAF Problems with Nuendo 14

Nuendo
1

Nuendo can’t seem to correctly read MXF files which are crucial to the Film/TV Post Production workflow. I’m not sure if BlackMagic is specifically trying to prevent Nuendo from working because ProTools is shoveling money in their direction, but this problem needs to be solved asap. Here is the issue. I use Sound Devices 664 and above to name my track ie; Boom, Plant Mic, Character Names for the Lavs. when I import them into DaVinci Resolve I can see that information. when I export as an AAF file then import that AAF into Nuendo I get files labeled A1, A2, A3, etc. the Metadata is there but Nuendo can’t read it. I have tried every possible export through DaVinci and I get the exact same outcome. If I export it to ProTools, everything works perfectly and all the files are named accordingly (the metadata works). I can at that point export another AAF from Pro Tools then import that AAF into Nuendo and it works. but why would I come back to Nuendo if I’m already in ProTools? Team we need to address this ASAP!!! I can’t express that enough.

If I import that audio - not as an AAF, but individually un edited, Nuendo gives me the opportunity to choose “Name Format” and that gives me the track info (metadata) correctly. That tells me Nuendo is 1/2 way there. it just needs to be able to read the full metadata inside of an AAF file. I haven’t tried embedded AAF, because I have had bad luck with files and fades, etc missing. and plus if it’s bigger than I believe 4GB in size the video won’t work. Also as a note I’m not exporting the Video with the Audio in the AAF export. It’s Audio only.

If I rename the Track in DaVinci Resolve from A1 - A* then export AAF. Nuendo will rename the Tacks to match IE (Boom, Character). That is again only Half the Battle. Most editors aren’t sound people so they don’t take the time to separate the audio onto those specific tracks. That adds Days to my workflow going though each file name to make sure it is the correct actor talking. This is just really annoying that the Developers can’t figure this out. I’ve been with Nuendo since 7.4 and in all of these upgrades they haven’t been able to address video/Post Production even though Steinberg’s biggest claim on this program is that its a post production powerhouse.
I was going to try and export an XML but Nuendo only accepts OMF and AAF.

If anyone know how to fix this without going into ProTools first please share and email me Koedfilms@gmail.com

4 Likes
2

This issue has been discussed again and again, but it still hasn’t been addressed properly. The root of the issue is that Pro Tools does not strictly follow its own official AAF standard. Over the years, it has developed its own “flavor” of AAF.
DaVinci Resolve appears to prioritize exporting AAFs in this “Pro Tools flavor.”

Pro Tools can correctly read the rich metadata (such as your “Boom” and “Lav” track names) from this type of AAF.

Nuendo, on the other hand, seems to adhere more closely to the official AAF standard and therefore fails to interpret this specific “Pro Tools-flavored” metadata, even though it can access the same information when you import the files directly.
This is why your Pro Tools workaround functions perfectly—it’s effectively “translating” the AAF into a format Nuendo can understand.

All I can recommend is to export a Broadcast Wave–based AAF, not an MXF-based one.

Before exporting:
Delete any muted audio clips from the timeline rather than simply muting or disabling them. This is known to cause the FFFFFC2B error.

Remove all crossfades and audio fades; use clip fade handles only.

If you’ve used audio track layers, right-click and Flatten Audio Track Layers.

Ensure all audio on the timeline shares the same sample rate and bit depth.

Go to DaVinci Resolve > Preferences > User > Editing and check the box for “Align audio edits to frame boundaries.”

On the Deliver page, select the Pro Tools AAF preset.
This is the most important step: change the Format from MXF OP-Atom to Broadcast Wave, and set the Codec to Linear PCM.
Set the Bit Depth to 24 (or 32, to match your project).
Crucially, uncheck “Embed Audio.” This will create an AAF that references external .wav files in a “Media” folder—something Nuendo handles much more reliably.

In the Video tab, uncheck “Export Video.”
Export your reference video separately as a clean QuickTime file.

This workflow offers the highest chance of success without using Pro Tools. While it may not preserve your “Boom” track names, it should at least provide a stable, correctly synced timeline—an improvement over the default workflow.

If track name metadata still fails to import, you’ll need a dedicated translation tool.
AATranslator is the recommended solution among many post-production professionals facing this exact issue.

1 Like
3

Thank you.

Yeah, I’ve already done all those things because I found that gave the most accurate. I’m just disappointed in Steinberg yet again for having a far superior DAW but fails to handle the simplest task that even a moron would have to use in the film industry. It’s like if you’re gonna make a mistake or something that doesn’t work Steinberg, please do it on the top level. Don’t do it at the very base bare minimum level.

I mean, even if they had a function to re-link to the original audio of the field recorder that would solve all of the issues that’s all they have to do allow you to just re-link to the original audio

Now the other thing I found that works, but you gotta separate all the tracks first or you don’t you can do it track by track when you bring up the info bar in nuendo you can click on individual clips and it’ll say file in the first slot and then it’ll say description in the second slot if I change the file name to boom it does it correctly but you can only do that to one audio clip cause if you try to second clip, it will say that clip is already made so you can’t do it in the file section. You have to do it in the description section and then it’ll change every audio clip to say whatever you want to say that’s been highlighted.

1 Like
4

Hey! So, I followed this guide and pretty much made a Nuendo AAF export in Davinci Resolve.

I had an issue with the export, though.

I have multiple timelines set with an audio track for each character that speaks. In each timeline, the audio tracks are set:

Dialogue A

Dialogue B

Source Audio

When exporting each AAF for a timeline and importing it to Nuendo, there are a few audio events that are out of sequence.

i.e. Dialogue B line 12-15 audio would replace line 1-5. I also had the Source Audio be jumbled a bit, too.

What would you recommend as a workaround? I had to export the AAFs like, 3 times to get it to work.

1 Like
5

Following along and adding my voice that this needs to be addressed comprehensively on Nuendo’s side. Please, Steinberg!

6

It’s hard to diagnose from afar, but I’m glad you managed to recover the timeline.
Nuendo is notorious for strictly adhering to the rules without offering clever workarounds. I once looked into writing an external app that could handle the import process without needing to buy paid utilities or maintain a Pro Tools license just for that purpose. I even suggested SB to do so. This makes maintaining updates simpler.
Here are something’s to consider when exporting from Resolve/Fairlight.
Delete any hidden or disabled clips.
Flatten/ decompose all layered compositions.
Disable any retimed or stretched clips.
Sub-frame clips can sometimes cause major issues.
Assign unique names to all used clips. For example, files like “xml.mov” are often split and reused across tracks, leading to naming confusion—especially if they lack SMPTE timecode. Clips from .mp4 sources are common culprits.
Iam sure you are already aware of these issues.
I hope SB is looking into this

1 Like
7

So, I decided to scrap my exports and try to redo it (first time doing a full project in DVR and roundtripping it)

Two things for anyone who might stumble on this in the future:

  1. There is a Sound to Film Export Guide by Fredo somewhere on the forums. Following that guide to a T netted me no problems whatsoever, and everything works as it should
  2. I was using a custom export based on the Avid AAF file at first, which was giving me grief for hours. The big issue came to when I tried ticking the “Commercial Workflow” and related. AAF seems to have an incompatibility glitch when those options are ticked. Using the Avid AAF set to specifications is the trick.
  3. I made a rookie mistake of trying to edit my video in sections and export the AAF in sections, too. When that happens, any track with a matching name can be overwritten if you’re not careful. Easily circumvented by exporting an AAF file of your main timeline containing all your sections.
2 Likes
8

If you do have the Recorder files on you, you can just export Davinchi timeline not from the Exports page, but from Timeline→export and than choose AAF. This will give you a simple aaf pointing to the original files. Nuendo can read this without problems.

1 Like