At one stage a place I used to work would conform in Flame then do a publish workflow that would then be brought into Resolve for grade. Mainly because Resolve was slow and inaccurate.
Is the reverse now an alternative ?!!
1 Like
premiere xml → resolve, make sources sequence using resolve → import exported sources (media management currently broken, use render to small dpx into one larg tmp folder then import that back and relinklink to source media then export trimmed rushes for only sources sequence using mediamanagent ) , throw these trimmed original files into flame, name shots, export plates → relink resolve timelines to rendered plates → export AAF from resolve → import aaf back into flame.
that will get you timewarps into flame proper from premiere AT LEAST FOR THIS ONE PROJECT THAT I AM TRYING
they just fixed 19.0.3 to export AAFs with timewarps again. , scales and stuff still get lost in translation…
1 Like
I’ve had decent luck on this one job - just import Premiere XML into Resolve, don’t bother linking media. Immediately export XML via timeline menu again, and then conform in Flame.
That XML behaved better than the original Premiere. Christoph also showed that on his fxphd course (where I first leared that trick).
But it’s been several months since I last had to do that.
https://www.fxphd.com/watch/?idCourse=597 around min 17.
1 Like
My only problem with Resolve for conforms is either I, or Resolve are kind of terrible at complicated, frame accurate, TWs. If they don’t come in right I don’t feel like I can get them frame accurate without a lot of trial and error. Simple TWs are no problem.
Again though I don’t know if that’s my or Resolve’s problem.
I think “accurate” is mostly not what you are after if you have ever seen premieres timewarp effect window you know nobody does anything there frame-accurate.
For me first step is to always get plates out, this is the first step for me, not the rebuilding of repos or perfect timewarps - but just figuring out a sensible sources-sequence and publishing out plates this is my ground truth for the whole project and is super important
Flame refusing to create such sources sequence because it cant even semi accurately figure out the amount of handles is my problem.
same goes when I reconform to these published plates, it always wants way too many handle frames and then refuses to link … ugh
Yeah, this is the main issue people are complaining when trying to switch to Resolve from anything else - that there needs to be better GUI for making conforms with TC values instead of frame ones.
Maybe we’re making progress? Adobe has just announced preliminary OTIO support in Premiere’s beta:
1 Like
Brilliant news, about time we get out of the dark ages of XML, AAF and EDL!
1 Like