Error with AAF export

Awesome -- thank you! I'll be on standby.

Clay,
I have pushed this through to the developers to determine why the wrong audio is being included in the AAF, I'll let you know once I get an answer.

Any ideas? I gotta turn this around by Monday.

Thanks for your help,

Clay

I sent an audio file of what it sounds like in Pro Tools — still getting the “tinny” sound from the disabled boom mic.

It seems like we are still having pro lens. I forwarded an email to you all with an excerpt. Let me know your thoughts...

Clay

I’ve forwarded on to my sound mixer. Will let you know! Thanks!

Clay,
if we understand right then yes, this export of a 1.6 FCPXML seems to give the correct result. The bits that are marked as disabled in the xml appear to be set to -96dB (off) in the AAF. Obviously you'll only really know when your sound editor gets back to you but it looks encouraging from here.

It would appear that processing of v1.7 FCPXMLs may not be correct in this aspect. If you get confirmation that it is correct we may come back to you for something that we can use to test with. If we can re-produce the problem here then all is OK but if we can't I'll probably be in touch.

So in other words... this export worked? You’re only getting the clear audio from the lav mic?

This is what we see in Pro Tools and the audio appears to be disabled and the rest of it seems to play fine and doesn't sound tinny at all.

Just sent you a Dropbox link!

Would you be able to provide us with a copy of the AAF you created so we can see exactly what the output in Pro Tools looks like?

Thanks,

Daniel

I'm using 4.0.32. I don't have ProTools so I can't monitor whether or not it's working. I send the AAF files off to our sound mixer, and when he opens them, the dialogue mono tracks have been merged. I will run it through right now. Could you also check?

If you convert the 1.6xml through X2Pro does the audio then work for you?

Also what version of X2Pro is it you are using?

Just did and sent over via email to This email address is being protected from spambots. You need JavaScript enabled to view it.. Thanks Daniel.

Hi Clay,

Can you try and export your project(s) as a 1.6xml to see if that helps with the problem? It is possible something odd is happening with the 1.7xmls.

Thanks,

Daniel