Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

WHAT IS YOUR FAVORITE PREMIER>RESOLVE>PREMIER WORKFLOW?

Also wondering about this. What I've been doing so far is to save an XML file out of Premiere, load that XML into Davinci, then output from DaVinci as a DPX file . But I've been outputting each DPX clip into a separate directory, then reloading them one by one back into Premiere. I'm new to DaVinci so I've been wondering if there's an easier way to import the separate clips back into Premiere?
 
I've been grading our new short the last couple days. Man, I love Resolve! I just wish it was actually inside Premier.... heh.

My workflow:

Edit in Premier, then Export an XML.
Bring that into Resolve. No problems at all, as long as I don't have nested sequences. Perfect conform.
Grade.
Render new clips and export XML.
Import that XML back into Premier.
Get pissed off because Premier gives me some generic error message about the XML.
Import the same XML into FCP 7 with no problems.
Export it back out of FCP 7 with no changes at all.
Import the new (Fixed by FCP 7?) XML into Premier.
BAMM. Works.
I talked to BMD tech support today. They don't seem to know all that much about XML.
This work-around is a pain, and I have to make sure to have enough coffee on hand to keep it all straight in my head, but it works.

I love Reslove. It retains astounding file fidelity. Power windows rock and the tracking is a God-send but the difficulties with round-tripping have me considering Scratch.
 
I must be doing something wrong, but I had never been able to go with XML from premiere (5,5,2) and get clean timeline in Resolve.
My work around became rendering the timeline from Premiere in prores444 and then scene detect in resolve.
Not ideal but works.
 
*Make a copy of your sequence that has picture lock; rename the copy 'online' and then replace all your nested clips with slugs
*Flatten your edit down into one or two layers and then delete all of the empty video/audio layers
*Export FCP XML from Premiere
*Import XML into Resolve
*Color, render out DPX sequence
*Load DPX sequence into After Effects (do your sharpening, grain, de-noise, vignettes on an adjustment layers if necessary) and save.
*In Premiere, import your After Effects comp and insert it on the top layer of your on-line sequence. Dip the opacity to 50% to verify the picture stays in synch.
*Send to AME

(If you have nested sequences, you'll have to color them in separate sessions within Resolve using the same process)
 
Christopher Barrett said:
I've been grading our new short the last couple days. Man, I love Resolve! I just wish it was actually inside Premier.... heh.

My workflow:

Edit in Premier, then Export an XML.
Bring that into Resolve. No problems at all, as long as I don't have nested sequences. Perfect conform.
Grade.
Render new clips and export XML.
Import that XML back into Premier.
Get pissed off because Premier gives me some generic error message about the XML.
Import the same XML into FCP 7 with no problems.
Export it back out of FCP 7 with no changes at all.
Import the new (Fixed by FCP 7?) XML into Premier.
BAMM. Works.
I talked to BMD tech support today. They don't seem to know all that much about XML.
This work-around is a pain, and I have to make sure to have enough coffee on hand to keep it all straight in my head, but it works.

I love Reslove. It retains astounding file fidelity. Power windows rock and the tracking is a God-send but the difficulties with round-tripping have me considering Scratch.
Click to expand...

Christopher,
Could you post a Resovle output XML and a FC fixed XML to compare....
this may be a simple fix for a text editor
 
Mike Harrington said:
Christopher,
Could you post a Resovle output XML and a FC fixed XML to compare....
this may be a simple fix for a text editor
Click to expand...


Strange... I just did a quick 3 clip edit in Premier (two tracks) and was fully able to roundtrip with Resolve. So there must have been something in the timeline I'm currently working with that gets messed up when I export that XML from Resolve... maybe one of the transitions.

Ugh... I hate conforming.
 
Premiere is great but their support is terrible... 3-4 day (business) turnaround... But they are making big strides tech wise which is why it makes this all the more infuriating.
 
Ive had more success sending an EDL to resolve as when I export an XML it seems to save the entire project and it won't open in Resolve. If you open it in FCP you get all the folders etc.

How do you export ONLY a specific timeline form Premiere???

Going from Resolve to Premiere I have had to do what Christopher said with FCP in the middle....

This is pretty frustrating. Maybe CS6 will have a built in CC vis Adobe's purchase of Iridas...
 
Hi Jeremy. Adobe and Resolve engineers did work together to solve a number of XML issues between CS 5.5 and CS6. I'd like to hear from some Resolve users to see if there are any remaining issues, but you can test out Resolve Lite and see how it's behaving. I haven't heard any issues in a while (save that XML doesn't support image sequences.)
 
I know this is an older post, but it was the first one that came up in my search that seemed appropriate, just wondering if there is any new info out there.... Even a link would be greatly appreciated!!!!

TYIA!!!!
 
I haven't had any issues bringing in XMLs from Premiere CS6 into Resolve. Most transitions seem to survive the process, along with static reframing (for the most part), animated pan&scans typically don't and I need to recreate them, which is a minor hassle. Generally the trip back to Premiere is painless, except on occasions some clips that have been sped up or slowed down come in broken and I need to delete and replace them on the timelines. It hasn't been a consistent clip element, but mostly speed changes and reverses. Overall it is a painless process and eats up very little time.

** I should note that this has been true of properly constructed timelines (proper framerates, consolidated layers, etc.).
 
You must log in or register to reply here.
Back
Top