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 :)

Anyone succeed at exporting PPro edits to Resolve?

R

Rob Ruffo

Well-known member
Joined
Dec 28, 2009
Messages
2,493
Reaction score
0
Points
0
Location
Montreal
If you use subclips or nested sequences, it make an unusable XML and unusable EDL (puts subclip name in file, not clip name with relevant timecodes.) This really needs to be fixed! Has anyone found a work-around?
 
Use Final Cut Pro?

No seriously ... first import the XML with FCP 6 or 7, and then re-export from FCP. Not 100%, but it may sort you out.

Both Premiere and Resolve's XML input/output are designed around interacting with FCP - so FCP behaves better when interacting with them.

I also resolved issues with importing Premiere XML output in Color 1 by running it through FCP 6.

The only surefire way to fix this however is to get rid of the subclips and nested sequences.
 
That's a major problem! And a scar on the face of an otherwise beautiful piece of software! It probably takes me more time to manually enter the subclip and nested sequence timecodes each time I have a project than it would for them to fix the problem!

CS5 is truly high-end pro software now, except for this one silly issue. What pro editor would work without making subclips!?
 
With the death of Color, Resolve is now the king of professional (affordable) Color Grading software.. Exporting edits from CS5 to Resolve is not just a mere option.. It's a must logic step.. I think it's just a matter of weeks for Adobe to "resolve" the Resolve problem..
 
i'm not even sure nested sequences would translate into resolve properly, as it takes information from another timeline, and resolve works with 1 timeline, and 1 timeline only referencing to what's in that. I'll have to test out of fcp for myself to be 100% sure though. subclipping i don't think should be an issue out of FCP, but i also think Premiere has an issue of using a older format of xml output and Resolve is optimized for the newest that comes out of FCP. That's something Adobe is gonna have to work on.

and it's pretty common to have to "prep" a timeline before it goes off to the conform. having xml support at this level is a major luxury, even the top end 100k systems just a short while ago needed a decent amount of prep on the timeline. unnesting sequences, grading speed ramped or slow downed shot separately, superimposed shots separately. collapsing the whole timeline down to 1 track of video for the EDL. very little native codec support so all your online files had to be converted to DPX or some other high quality picture sequence. and now the technology is easier than ever. I'd just give it some time, i'm sure it's on Adobe's to do list, as well as Blackmagic's
 
The Resolve manual states that the software will not import nested sequences. It does import multiple tracks pretty smoothly out of FCP (I have no idea how many it will do). If I could get it working as nicely with PP as it does with FCP I'd be damn happy. Adobe has said they're working on this... so hopefully soon.
 
But... It would be possible to just translate those nested sequences into a series of cuts referring to a series of clips on the drives. I mean if you play back the parent sequence, that is what PPro will do in real time - nested or not, it's just one clip piece after another as an end result. Crossfades and that - fine - but straight cuts, whether derived from nested sequences, subclips or any other form of presentation are just a series of pointers to files on drives - surely translatable to a (correct) series of lines of text on an XML or EDL export.

Who cares if its nested - I don't need the nests or the layers to be preserved, just the "edit event list" they describe

In the past other systems may not have offered this, but in the past off-line and on-line were much more separate and done by much more invariably different people.
 
Rob Ruffo said:
But... It would be possible to just translate those nested sequences into a series of cuts referring to a series of clips on the drives. I mean if you play back the parent sequence, that is what PPro will do in real time - nested or not, it's just one clip piece after another as an end result. Crossfades and that - fine - but straight cuts, whether derived from nested sequences, subclips or any other form of presentation are just a series of pointers to files on drives - surely translatable to a (correct) series of lines of text on an XML or EDL export.

Who cares if its nested - I don't need the nests or the layers to be preserved, just the "edit event list" they describe

In the past other systems may not have offered this, but in the past off-line and on-line were much more separate and done by much more invariably different people.
Click to expand...

Well, this is why subclips/nesting sucks, and why I try not to use them.

You are right though, the software vendors should just "un nest" them dynamically when creating EDL/XML for interchange.

That's really the problem with XML ... the X stands for "eXtensible" and so people do.

We need a real standard ... not a de facto standard like FCP XML, an actual standard. A base set of transitions and timeline/media descriptors that will be supported.

Then software like Premiere Pro should ask you, "will you be sharing your XML with Premiere users or interchanging with users of other systems?"

Now, the same tool becomes useful for sharing projects with full features of the native software, and with a button click it becomes a standards compliant interchange tool.

I don't know how interested anyone really is in this. Too many vendors depend on user lock in. Its a historical business model they have not broken free from.
 
Christopher Barrett said:
The Resolve manual states that the software will not import nested sequences. It does import multiple tracks pretty smoothly out of FCP (I have no idea how many it will do). If I could get it working as nicely with PP as it does with FCP I'd be damn happy. Adobe has said they're working on this... so hopefully soon.
Click to expand...

Patience... But not too much...

Cheers

Dave
 
You must log in or register to reply here.
Back
Top