After importing AAF, I have mixed up metadata. The tracks match the recorded sounds, but the names are mixed up in the individual tracks. This is the second time I’ve had this happen, each time from someone different from AVID. If they sent it from DaVinci, it’s fine…
The problem is said to be in AVID. If you import audio composed of multiple tracks and not mono tracks, it messes up the metadata. I don’t understand… I guess it doesn’t bother anyone, just me 
It does bother people. We’ve requested updates to AAF import several times. I think the prevailing ‘idea’ is that Steinberg is conforming to specs and companies like Avid are not so they have to change.
Of course that means nothing for those of us that can’t tell people what to do and have to receive these AAFs anyway, and it doesn’t look good to complain to the rest of the production when PT users don’t face the same problems (a general note, not this one in particular).
It’s frustrating.
3 Likes
Just had a similar issue, AAF that would not import well using Nuendo (tried N8, N12, N13 & N14). Only one track in the AAF was available for import, Nuendo did not see the other ones.
Then tried to open & convert the AAF in Vordio => it works.
AAF Import update would be very appreciated.
Yeah, but Steinberg should communicate with Avid (or any other company) about these issues.
If you go to Avid forum they will say it is Steinberg issue, here it is “Avid broke the specs”.
I know they are “rival” companies, but there should be a better communication..
Or maybe we are simply wrong, maybe they communicate very well, but dont have time and r&d recurses for development.
AAF is not an Avid format. Avid and Steinberg can do what they want with their respective implementations. Avid is never going to change what they have done so far because that would risk breaking backward compatibility, and I say that because the argument has been that Avid’s implementation is more “loose” and allows things that aren’t technically “correct”. So if Avid adjusted and took that “functionality” away it would break things in the Avid space. They’re just not going to do that.
What is left is for Steinberg to either adapt, or not.
Right now I’ve spent a lot of money on a Pro Tools subscription simply because Steinberg is being stubborn about this so I’m literally stuck having to get it in order to open some projects that won’t import correctly in Nuendo. It absolutely, 100% sucks. Anyone asking for a value proposition on getting either - if they have to interchange with people in the Avid space and where they aren’t sticking to the “correct” way of doing things - is going to realize that Pro Tools is better value. Of course there is more to it than that, but the reality is that I need both for this one incredibly irritating reason.
And before someone says “Oh but your clients should just do things the right way” I’ll just point out that this is not how it works in some markets. If I’m saying I’m doing a job they will assume I’m using PT. I’m not going to tell them I’m not and as far as they’re concerned there is no difference because they don’t know about it. But if I start asking for new AAFs to be delivered then the risk is that I’m the odd one out because every other engineer they interact with has no problems (because they are on PT). So right or wrong it makes the work situation less smooth and that’s something they care about. They want to be able to get an experienced video editor to output an AAF to me and that’s it. No problems to solve.
There are a few key areas in post where I think Nuendo really needs ‘more love’. VCAs, parts of the automation system, and yes, AAF import.
3 Likes
It’s exactly as you write. The problem may be on Avid’s side, but if ProTools doesn’t have a problem with it and they are the majority on the market, I can’t insist on following the standards from my position, because the one who doesn’t cause problems will simply get the job… It’s a shame that all sorts of conveniences are constantly being improved, but the absolute basics don’t work. Or we have to buy external programs for it 
1 Like
Agree
Yep, that sound rather fammiliar
Man, we should get a beer together and cry our tears
1 Like
At some point, AAF between Media Composer and Avid was broken.
So far for communication.
Fredo
1 Like
I’ve never tried this App is it good? Does it work on all AAFs? If so, why can’t SB make AAF import ‘work’ as expected?
I’ve only used Vordio in this specific case for now.
In that case it worked to convert the AAF to a AES31 ADL (.adl), that imported fine in Nuendo 14. Haven’t tested other functionality of Vordio.
The reason why this worked for me, and the Nuendo AAF import feature didn’t, may be found in what the conversion to AES31 actually does. See Convert – Vordio
eg Wrap source media – External WAVs will be rewrapped into new WAV files with cleaner file names. Embedded audio is always wrapped as new WAVs.
and/or:
Transcode incompatible audio – Any source media that is not compatible with audio software (video files) will be transcoded into WAV files.
Further testing would be needed.
Thanks for this. I’ve used Vordio to get AAF’s into Reaper for many years now, but have recently switched to Nuendo. I’ve been using Pro Tools for prepping and re-exporting ‘better’ AAF’s for Nuendo. I’ll give the .adl a try.
tg
Yes it is good.
They consistently adapt to AAF-related challenges, developing and implementing effective workarounds. Their very existence is defined by their role as a solution provider, ensuring seamless workflows despite technical limitations.