Premiere CS6 roundtrip?

[Mike Molenda]

I don’t think I was clear. I’ve actually been able to successfully round trip Premiere to Resolve with EDL. And I’ve done FCP7 XML to Resolve successfully, too. Thanks for the offer to help, though!

[Clay Coleman]

Having similar issues. I was handed a PPro CS6 Project (90 second mixed timeline with mostly ProRes4444 and some .r3d all at 25fps) to grade and tried the following:

1. select sequence in PPro >export > edl. This works, sort of. In Resolve, the edl didn’t bring over the resizes or the numerous retimings and speed ramps the editor used rather extensively. If I had asked the editor to go back and bake in all those effects and give me the project back, it probably would have worked far better. Not very elegant, but at least I would have had my back covered that all the shots were timed and sized as the editor intended.

2. select sequence in PPro > export > fcp xml. This does not work at all well and I can’t see using it again anytime soon. The first couple of shots came over ok, but once I hit the shots with speed effects and resizes, things pretty much went haywire. In and out points were no longer accurate. Other shots froze up entirely. Not a workable method.

3. exported a QT ProRes 4444 from PPro via AME. Brought the QT over to Resolve and ran Scene Detect. Works great, but only because the entire show is hard cuts only. Still, it’s seems currently the best method as it is the only totally reliable one.

To work really well together with PPro, Resolve either has to be able to read the FCP7 xml’s better, or, PPro has to have it’s own PPro xml export function and not rely on the fcp7 route (probably not a viable alternative over the long term). At the moment the colorist has to be moderately adept at both PPro CS6 and FCP7 to troubleshoot and solve the issues.

Kinda clunky. Needs a fix.

[Michael Griggs]

According to the manual, speed change effects (as in ramps) are not supported. The entire clip has to be one speed (be it faster, slower, etc.) for it to translate.

Having used the export-the-entire-sequence-as-one-file method, I agree, Clunky to say the least…especially if/when anything beside straight cuts are used. Obviously you can still get away with keyframing for dissolves and such, but if there are any “special” (read: third party plug-in) transitions, that would make things MUCH more difficult.

The next project I get that comes from Premier, I’m gonna try using xml to bring it into FCP7 first; then round trip from there. (Had plenty of success running projects through Legacy.) At least I won’t have to keyframe all the dissolve transitions again…not to mention the fun of trying to scene detect and split a 90 minute feature…..

[C-deeq Rapheal]

WOW,

This is the error message
“the project contained a sequence that could not be opened. No sequence preview preset file or codec could be associated with this sequence type ”

I used to color correct in After Effects. I have since got my hands on the Red Epic, the Scarlet, and I plan on buying two Black Magic cameras. Therefore, I decided to change the way that I color correct. I first sterted using speed grade. Speed grade has the capabilities of being a great software. However it has some Major flaws that need to be resolved ASAP …..Which brings me to my point. Adobe Premiere can import and export FCP XML v4 However, davinci can import FCP XML v4 and FCP XML v5 but only export FCP XML v5. What that means is, if you want to import any new XML’s that use FCP XML v5, you can’t. I don’t know what needs to happen but we need Adobe to make an update so that they can support 5.0.

[Joe Maurici]

Hi guys,

Looks like this thread died in the you know what mid last year.

I think I have found a workaround, using CS6 and Resolve 9. If i’m missing something obvious please don’t hesitate to tell me.

In Prem Pro I am using native R3D files to edit. Once the edit is does export a XML file as is.
Import the XML into the Timeline section of Resolve and it should bring in the clips needed but have trouble linking them to the Timeline itself.

So once you have your clips in Resolve, go into the Media Pool and Select your clips in Reels. I.e. Select all of your A001 clips. Then right click and select Clip Attributes. Click on Reel Name. Select ‘User Defined and put in ‘001’. Do the same for all your other reels ‘002’, ‘003’ etc

Go back into Premiere and choose only the A001 clips you have edited and change the Tape Name to ‘001’ as we did in Resolve. Do the same for any A002 clips etc. Then export an EDL from Premiere.

Go back into Resolve and into the Timelines section import your EDL and it should all re-link perfectly… Should!

I tested this with a Speed change in the EDL and XML.

All the best
Joe

[Margus Voll]

You can only have constant speed changes not variable speed change or it will not work.

—

Margus

https://iconstudios.eu

DaVinci 9, OSX 10.7.4
MacPro 5.1 2×2,93 24GB
GTX 470 / Quadro 4000
Multibridge 2 Pro

[Jake Russell]

I am trying your method, but in Resolve media pool, User Defined is grayed and not adjustable out when I click into Clip Attributes.

How do I lift this restriction?

[Margus Voll]

what did you mean by that ?

if you have constant speed changes in footage it should work fine out of the box so to say.

—

Margus

https://iconstudios.eu
https://vimeo.com/iconstudioseu/videos

DaVinci 9, OSX 10.7.4
MacPro 5.1 2×2,93 24GB
GTX 470 / Quadro 4000
Multibridge 2 Pro

[Jake Russell]

Using Joe’s method above, I am unable to manually change the Reel inside of Davinci. There were no speed changes in my footage.

[Margus Voll]

you get reel already in edl on xml or from file name folder name etc.

you can not do it manually clip by clip

—

Margus

https://iconstudios.eu
https://vimeo.com/iconstudioseu/videos

DaVinci 9, OSX 10.7.4
MacPro 5.1 2×2,93 24GB
GTX 470 / Quadro 4000
Multibridge 2 Pro