[Will Rogan]

Juan,

Thank you so much for your quick reply.
It turns out that I had not clicked on the new sequence that the AAF generates in the Avid bin. In a panic for a deadline I was still looking at the previous one.
Now that I check the new sequence, all the new renders link up correctly.

Best
Will

[Will Rogan]

Solved!

Juan,

When pointing the media pool to the whole /mxf directory, my clips all link up.

Thanks,
-Will

[Will Rogan]

Juan

Thanks for the reply.

The media is online in my avid project before AAF export.
I did add my avid directory to my media pool.

I moved things around in the avid media folders because I know exactly what I have in there. I am coming from an already consolidated project that has media only in mxf/1. I move that media into a new folder called /2. Then I transcode a copy of my sequence and all that new media goes into the /1 folder. This is a means of consolidating/transcoding a sequence without using a second drive. I send an AAF from the newly transcoded sequence and add that /1 folder to the Resolve media pool, because that’s where the transcoded media from that sequence is.
I will try this again and add the entire /mxf directory to the media pool

I transcoded everything in the sequence to DNxHD 145, and checked the box in the Consolidated/Transcode window that says to include media already at the “target resolution,” which I assume means that Avid will copy the DNx HD 145 media that is already in the sequence. Is that the case?

Thanks,
Will

[Will Rogan]

In my experience, you have to render out the MXF files from Resolve with the advanced export option set to None, as opposed to Avid AAF round trip. Files rendered out this way relinked for me, whereas with Avid AAF Round trip selected, they did not.

-Will