Skip to main content
twentyonehub
Participant
May 13, 2021
Question

Issue with importing XML

  • May 13, 2021
  • 1 reply
  • 2347 views

Hi all. I've been having this weird issue with conforming XML files (either from FCPX or even Premiere Pro) and I'm not sure if I'm missing something. Basically the workflow is such;

 

1) offline editor provide a xml based on the edit ( media file linked to proxy files normally )

2) colorist grab the xml , grade and export the graded clip in proress 4444 but in separate folders (just to avoid same shot diff in out point issue ) 

3) online editor grabs the graded clips and conform using whichever software. 

 

In my situation, I'm the online editor and I worked my timeline on Premiere Pro ( somehow seems easy and fast for me to make simple changes ) and my composition on NukeX ( export shots that need to composite from premiere pro ) but the issue is I can never conform the XML from the offline editor in Premiere Pro. The common issue would be; 

 

1) media timecode / duration does not match ( works well if i did my steps below )

2) having to locate each folder of the graded files to link ( anyway around this ? )

3) speed ram ( this is the biggest headache of all time. most of the time i have to eye match the and if that don't work i'll most likely ask the offline editor to give me the keyframe timecode ) 

 

Hence, my workaround at the moment ( its redundant but somehow works for me and also speed up my time of conforming) is to import the XML in Resolve ( had to learn about resolve just to solve this issue) , link the graded clips to it and re-export back an XML so that when I import the new exported XML from resolve, it will automatically sync all files into premiere pro. 

 

Am i missing anything that I do not know of ? 

1 reply

R Neil Haugen
Legend
May 13, 2021

I've heard of colorist pals needing to do the import to Resolve/XML/import to PrPro thing at times. While at other times, the XMLs worked.

 

So I think some things don't pass through the XML as well as others when coming from FCPx or at times, even a PrPro XML.

 

Weird that a trip through Resolve fixes it though. Time-consuming extra step.

 

Neil

Everyone's mileage always varies ...
twentyonehub
Participant
May 14, 2021

Guess I'm not the only one. Haha. 
Wonder why this hasn't been rectified by Adobe. Would be great if they have the same similar conforming from bin like Resolve does. At least that saves the time of conforming to resolve and export a new xml to premiere.

 

The worst will be speedram actually. It could be as simple as from premiere pro to premiere pro. That data just lost in translation when exported to XML. I'm sure there's an easier way to find out how to fix this issue.

R Neil Haugen
Legend
May 14, 2021

Some users I know go from PrPro to Resolve via XML routinely with only a few bumps. Besides not wanting anything with at most two tracks ... preferably only one ... in the project when the XML is made ...

 

First, they NEVER take speed-ramped clips. They want all time changes removed prior to the XML.

 

Second, they want all transitions removed also.

 

Third ... they want all graphics removed.

 

Fourth ... most want any resizing to have been done with "set to framesize" for items simply plopped upon the timeline and auto-resized by PrPro, and for all other scaling, they want a list with timecode, clip name, and scaling.

 

And fifth ... they must have an H.264 of the project to overlay over their timeline in Resolve to check all conforms.

 

Other than that, it's a piece of cake supposedly. Ahem.

 

Neil

Everyone's mileage always varies ...