Missing varify effect in AAF from MC

[@tention]

I have an AAF here from MC and the editor has used Varify a lot.
Unfortunately I do not get the rendered FX but only the clean audio.
Does anyone know where to look for our mistake?

[smurfyou]

Did the editor render it before exporting? I don't remember how that works on the Avid side.

PT defaults to importing the rendered effects so there's really not much to do on your end. If it isn't getting to you for some reason I would ask the editor to put those clips in a new sequence, render/consolidate/whatever they need to do to create new media and export that.

[AndrewAction]

Originally Posted by @tention

I have an AAF here from MC and the editor has used Varify a lot.

Hi, As your file comes from MC you could ask the editor to use the new Export to Pro Tools session IF they are on one of the 2 latest versions of MC.
I have tried it with several MC Projects so far and it has worked well FOR ME.
Disclosure. My trials have been on a computer with both MC and Pro Tools installed and use the same storage.
As I do not ever do any audio work in MC I have not yet trialed this with any Plug ins. The MC export to Pro Tools session option has a broad selection of export setting available ... including markers, a huge plus over AAF's in my setup.

Andrew

[garret]

Originally Posted by @tention

I have an AAF here from MC and the editor has used Varify a lot.
Unfortunately I do not get the rendered FX but only the clean audio.
Does anyone know where to look for our mistake?

Make sure you have the little tick box ticked for importing rendered Fx when the import session data window is open when opening the aaf. I believe its the first box toward the bottom left of the window just under the track selection.

[smurfyou]

Originally Posted by garret

Make sure you have the little tick box ticked for importing rendered Fx when the import session data window is open when opening the aaf. I believe its the first box toward the bottom left of the window just under the track selection.

I was just coming to say that. I said earlier it defaulted to on but I noticed yesterday it does not

That should do the trick.