creating AAF failing

Dear Florentine.

Thanks for confirming.

James

yes. that should have fixed the bug. they did send the fix directly to me before it was ready to be upgraded in the App store. They were very responsive.

Dear Florentine,
Have you upgraded to 4.5.4 ?

yes, there are a number of r150 tags, as I said. and, no fades associated. no picture fades in the entire film. there are audio fades which I removed and output a new XML, then tried X2Pro. No go.

is the location written in frames?

thanks so much

Was there any more references to "r150"? There should have been at least one further up in the XML that would have a relative name and filepath to a clip. Would you mind sending us the xml to investigate?

thank you. I did as directed and found multiple clips with the same name. None have fades.
there's also multiple r150 that don't look like they're associated with clip names. see screen grab.

Hi Florentine,

That error message is a known bug which has been resolved in testing, and a fix for it will be released in the next update.

If you need this resolved now there is a workout around. If you open your xml and search for the reference clip that is causing you the issue (r150) you will see it links to a named clip. If you then go to the location of that clip in Final Cut, remove all of the fades, and then re-export the xml it should work.

If that didn't solve the issue, you can try removing the problem clip completely and seeing it that allows to to export an AAF. Then you can readd that clip into Pro Tools manually. Here is page with the same issues for reference. https://forum.marquisbroadcast.com/x2pro-problem-reports/1953-aafresult-insuff-tran-material-errors-converting-xml-to-aaf.html

It's been a few years since I used XPRO2, so I'm quite rusty.
I created an XML file, located the source and destination, but receive an error message
thanks