Page 1 of 1

Experience bringing timelines from Resolve to Premiere?

PostPosted: Sat Jun 16, 2018 10:14 pm
by Dustin Bowser
I just recently cut and sound designed and finished a short piece in Beta 4 and was incredibly impressed by the entire workflow. I did a project on Beta 1 as well and am amazed to see how far it has come in terms of stability and usability.

Because my experience was so smooth, I'm seriously considering using Resolve 15 for a editing a Feature Film that I'll be starting in the next week.

The one thing I wanted to check in on before I go down that road however is how smoothly will I be able to get my Sequences from Resolve into Premiere? I know that the producers will not be happy if I have sandboxed the entire Film edit within Resolve and they'll never be able to find another editor to get in there and work with it. If I can spit out my Sequences to Premiere to future proof the piece in case they need to do anything with it in the future I'll feel a lot more comfortable.

Anyone have any experience with this?

ALSO that said, if we do decide to go the Resolve route to edit this film, I would love to be in contact with the BMD team here because it would be great to work something out to share some of our process for use as Customer Case Study promo material. We'll be doing a lot of interesting things that Resolve will uniquely be allowing us to do. I'm quite excited. Of course if we did this it would also be great to have direct access to a support line in case we hit any major snags ;)

Re: Experience bringing timelines from Resolve to Premiere?

PostPosted: Sun Jun 17, 2018 2:54 am
by Uli Plank
If you:

– have proper Timecode
– have proper reel/tape names
– a clear file organization
– and no speed changes

Then there is a good chance that you can move edits back and forth between DR and PPro. You can even do grading in DR, render the files and still use the edit in PPro. But, as always, do some extensive testing of your workflow and specific needs.

Re: Experience bringing timelines from Resolve to Premiere?

PostPosted: Sun Jun 17, 2018 5:26 am
by Danny Field
I started writing a way to do this.... but hit a bit of a snag.

Usually I export XML [Final Cut Pro] file from Premiere into Resolve. And it works great.

Once at picture lock I'd export the timeline XML and Resolve opens it no worries. I used to have issues with the other exported formats but currently XML seems really solid. I've even been able to work with proxies or issues with filename extensions.

Now.... you want to go the other way. So I created a rough edit with some shots from last night's filming

Edit tab, you can export your Resolve timeline as XML. BUT here lies the issue

It spits out a fcpxml and Premiere Pro only likes the earlier version of XML. I had a look for some converters such as this [http://intelligentassistance.com/xtocc-cc.html] but this seems to mac only. And I've heard issues where it brings the timeline as one big file, not clips.

I tried manually fudging the data inside as XML is only clip info and where they sit in the timeline; but Premiere still came up with 'not supported'

Sorry I couldn't give you the answers you were looking for.

Re: Experience bringing timelines from Resolve to Premiere?

PostPosted: Sun Jun 17, 2018 6:13 am
by Uli Plank
Resolve can export a XML in version 7 format any time, just choose it.

Re: Experience bringing timelines from Resolve to Premiere?

PostPosted: Mon Jun 18, 2018 2:28 pm
by Sam Steti
Hey,
In my experience, first be aware - as Uli wrote - that you can choose a FCP7 XML (so no FCPXML) to achieve what you need, in both ways...
Now, where you may encounter issues is about transitions, speed changes, PTZR maybe, etc... So theses are specifically what you should test to have your own point of view.

I don't roundtrip anymore since 2017 (thus stay in Resolve for the edit too), but I used to change my workflow only to adapt to the XML way : then transitions, retimings aso. where done at the very final edit, after projects where graded and resent to (for me) FCPP7.
Just a way to avoid basic XML issues... In this specific case, it always worked great.