FFAStrans forum

another thing, as you can see in the screenshot here below, in my Bin I have two different media, both file are Mxf op1a and are copied in the UME/1 folder, but as you can see in the screenshot the Media files in the bin are represented with two different icons, this means that when I import your aaf in the bin, Avid consider the Media file in the UME/1 folder as a linked file, when I import the aaf called P0878935_Cut.....Avid consider the Media file in the UME/1 folder as a real media files. obviously the goal is to create an aaf which when imported into avid, recognize the file as a real media file.

OK good to know.
The additional aaf example from you is pretty different again to the last ones. thats good because it hints me on what data in the aaf is mandatory for avid and what not. Anyway, the number of overall differences between my (or better the pyaaf) version and your examples, not sure if i can get this to work. It's a shame that we don't have the documents for the current aaf version from Avid.

But well, no risk no fun Stay tuned...

ok thanks emcodem

Hi emcodem, any news about the creation of aaf from op1a mxf ?
thanks

Yeah it's not the best time for these kind of experiments currently hehe... In my job we always have this "pre-summer-high" before the "summer-low" starts, so i am buried in work currently.

I'm looking into it from time to time but the stuff that needs to be done requires a longer session in one piece, this on and off all the time is not good.
Good thing takes time

yes I know very well this pre-summer-high, don't worry and thanks again