Importing an XML from Resolve to Premiere gives me a "File import error" "The importer reported a generic error."
The XML from Resolve opens correctly in FCP7, and exporting that Resolve XML from FCP as an XML version 5 from FCP7 is correctly opened in Premiere. Can anyone else verify they are getting the same result?
thanks,
Just needed someone else to have the same issue. I recommend submitting a bug report. And we can cross our fingers for them to get this right. Good thing we have FCP7 for yet another work around........
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
good luck,
LFedit wrote:
Just needed someone else to have the same issue. I recommend submitting a bug report. And we can cross our fingers for them to get this right. Good thing we have FCP7 for yet another work around........
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
good luck,
I submitted a bug report
I did on initial import, but I added additional clips to the media pool and forced conformed the sequence.
Have you noticed any frame slip in your conformed XML file once back in Premiere. I'm getting a range of -4 to +8 frames of slip when exporting 15 frame handles from Resolve. I'm wondering if its a Premiere XML export to Resolve error, or if the translation from Resolve's XML to FCP to Premiere. I haven't been able to do extensive testing yet, but it seams to be the same in FCP as well as Premiere, making me think its a Premiere XML error to begin with.
I haven't noticed any frame slipping. The only slipping I notice is in and out points change when I have a transition alignment on something other than center, but it doesn't affect the transition in and out so it's not that big a deal.
My projects tend to be XDCAM EX 1920x1080 @ 24p. I render with 24 frame handles and I just started having issues when I have offline media. Specifically, I had some Illustrator files in Premiere and I kept them there because I wanted to keep the timing the same. Normally Resolve renders black frames for the offline media.
At first I had a rendering problem when I had handles in Resolve. Then, once I got out of Resolve, Premiere would not import the XML.
Funny thing is that I tried importing in CS5 and it worked!
Odd...must be a CS5.5 thing. But I think in CS5 the sequence from Resolve made Premiere crash.
I emailed Blackmagic and they said that it seems to be a problem with how Premiere handles slugs.
It appears from this thread: http://forums.adobe.com/message/3764722#3764722 , that the CS5.5.2 update is what broke the XML import directly from Resolve.
Just found that I did have one small offline file in the form of a nest in my problematic sequence, possibly that is why my handles are off. But I agree, Resolve does "normally" render out black frames for the offline media.
If you hear any updates or have any other work around I am grateful for the feedback.
Well possible work around:
1. Delete all offline clips found in Resolve, in the Premiere timeline.
2. Export new XML file from Premiere to Resolve.
3. Load new XML in Resolve, verify there are no offline clips.
4. Export the newly conformed XML from Resolve.
5. Import XML directly from Resolve in Premiere.
this worked for me...
However the XML from Resolve relinks to the original media, not the Rendered files with "...V1_0001" and even though the conform loads the correct nodes and versions in Resolve, the resulting XML export does not have any data as to the shot# or versions.
can you confirm this?
You did do the resolve to FCP setting right?
One thing you might try to do: In Resolve, unlock the tracks in the conform tab and delete the offline clips that way you won't miss any and then try the render again and export to Premiere.
I recommend making a short sequence to test it out. Like about a 4 clip sequence with clips that will be offline in Resolve. Basically, something simliar to what you have already just smaller.
When I removed the offline clips in Premiere and re exported the XML file to Resolve, the resulting XML file from Resolve imported directly into Premiere, No import error, which is why I think having no offline media it might be a work around.
Both the XML file from Resolve and FCP to Premiere has not caused any crashes on my end.
I'm using FCP XML-Round-Trip from Resolve when rendering and using "render clip with unique filename" As long as I render, then export the XML the conform works in Premiere, however the clip names in resolve reflect the original edit of the XML file from Premiere, and only in the file path is the corresponding Resolve renders. I can not find a way to auto reconnect the resolve renders to the exported XML if moved to another suite with out manually doing every shot. Any thoughts?
On a positive note, doing the above steps for removing offline media first in Premiere (I have not tested your suggestion yet of deleting offline files in Resolve) has solved my handle slip problems.
I'd suggest closing both Premiere and Resolve, reopen, and send a sequence from Premiere to Resolve with no offline clips when conformed in Resolve, render and export XML and open directly in Premiere. It's working for me now as long as Resolve exports a XML file without any offline clips, no more import errors or crashes.
Sorry that was a bit confusing.
When I render from Resolve the resulting XML file in the rendered destination folder does reconnect to the Resolve renders as it should. What I was referring to with the reconnect issue, is if I export just the XML from the timeline management panel, the resulting XML file only reconnects to the original media.
What I was trying to do was save a whole re render process from Resolve, since all the clips I needed rendered for the updated XML with the removed offline clips (which is how I got the XML to open in Premiere natively) had already been rendered.
Hope that makes sense.
I just re rendered anyway from Resolve, and as long as Resolve has no offline clips i'm able to open the XML file directly into Premiere without first going to FCP, AND not having offline clips in Resolve has fixed my handles issue as well.
Hope this is the same for you as it may be the workaround until an update is made.
amorrelle,
It's not a render issue with Resolve, it's a translation problem with offline media. If there is offline media in the original XML from Premiere to Resolve, Premiere can not interpret the missing media when coming back from Resolve with out using FCP to translate the XML for Premiere. Verify that there is NO MISSING MEDIA in your original XML send from Premiere to Resolve, if there is you will need to use FCP inbetween Resolve and Premiere. Alternatively you can create a new sequence in Premiere that won't have missing media (such as graphics, dynamic links, nests, etc) and let Resolve auto conform the project for you when you export the XML back to Resolve.
Well, now I do too... There was a title I missed. It imports fine now
. Thanks for the clarification. I've had various levels of roundtripping work in other versions of Premiere Pro but they all have had various problems. This looks to be the most complete (albeit a bit annoying). Thanks once again.
North America
Europe, Middle East and Africa
Asia Pacific