AAF import woes...

Rakesh-Malik wrote on 3/1/2020, 6:10 PM

I've been trying to make use of Vegas, but it's been quite a trial so far. Red import appears to be completely unworkable; Vegas doesn't recognize Red media folders as Red clips, so I end up having to import them one clip at a time, or use an explorer filter to select the R3D files and import them as a batch... neither ends up working well.

AAF import is ridiculous. I'm trying to import an edit I that did in Resolve and exported as AAF, which imports cleanly into Mistika, but in Vegas I'm being forced to find EVERY CLIP manually, which is a horrendous user experience, and a complete non-starter for anything longer than a dozen edits.

Is there something I'm missing here to make this work correctly?

Comments

Kinvermark wrote on 3/1/2020, 6:31 PM

I have had success moving between Resolve and Vegas (both directions) using FCP7 XML. In general, footage must have proper time code, but I have no experience with RED footage.

BTW, wouldn't you want to work the other way around? That is, grade in Resolve and edit in Vegas.

Rakesh-Malik wrote on 3/1/2020, 7:21 PM

I edited this in Resolve before discovering the Vegas update that caught my attention, so I'm trying to get that edit into Vegas so that I can try out the audio mixing functionality there.

I'm going to try another edit from scratch in Vegas that I'll be doing the grading and compositing in Mistika, which is a mix of Red raw and h.265 (DJI) footage, so I wanted to see what Vegas' Redcode handling was like... and so far it seems like a non-starter, so I'll make proxies for editing.