Please don't double-post. I deleted your duplicates.
Actually - after posting here I chatted with Adobe support (Nasseem) and was advised to post the same question under the XML SDK section - which is what I did. I would appreciate if you could leave that one there and delete this one if no other replies come through. Nasseem seemed to think that I would get more replies under the SDK section.
[moved to premiere pro sdk forum]
I believe this was a bug that was fixed in CS5.5. I just tried it myself on Mac in CS5.5, and the UUID for a masterclip was correctly roundtripped from import to export. Do have a sample XML that we could look at in CS5.5, along with repro steps?
I am using CS5.5 and that is where I have a problem (PC).
I'm attaching sample XML files.
toonboom.xml is where the initial export comes out of
fcp...xml - is the output from Final Cut (I don't want to use that)
premiere...xml - is the output from Premiere - where it's noticeable that the clips have newly generated UUIDs.
(* the FCP and Premiere XML files include "with" and "without" effects. It makes no difference for the end result, I think, but it makes a difference in the viewing of the clips in the editing packages)
I export a single XML from ToonBoom Storyboard Pro 3D
Import that into Premiere
Export back to XML
* - in the future it would include editing too but right now I'm just trying to match the two XML files and align the clips
Thanks for looking into this!
I just noticed something that might be more important - retaining the comments!
I noticed that in the comments section there's a code that relates to the same code as in the original app - ToonBoom, since in TB there isn't any mention of a similar code to the uuid.
FCP retains the comments - which is probably why it works better with TB
<mastercomment1>SB_PSOBJID : 065a3992ac7cd60d</mastercomment1>
<mastercomment2>SB_BITMAP_P : 0.0000000000;0.0000000000;1.0000000000;1.0000000000;1.0000000000;TRUE</mastercomment2>
If I can get the XML importer to bring in comments then I can get away with having wrong uuids
Any chance of that happening?
Is there a script importer of XML to Premiere I can tinker with?
What I need to do is get back into TB the editing I've done in Premiere. The new in/out start/end information of each clip really. To do that, I need TB to recognize which one of its originally exported clips is being used and manipulated.
I am not a proper developer/coder and don't know much about c++. I am more of a hoppyist/ novice scripter.
Right now my written code separates the important data from Premiere's exported XML, and I'm still in that process. What I intend on doing, for the time being, is try and compare clips by the clip name (parsing both the Premiere XML and the original TB XML), and generate a new XML based on the TB format and - hopefully - copy the uuid and comments from the original XML based on the comparison. I hope it works - I'm still in the process.
Of course - it would be much easier if I had something to hang onto like importing the comments into Premiere from the XML. That way I will not need to rely on the original XML. I also fear that I will run into errors during the comparison and new XML generation since the comparison by clip name might, I fear, cause duplicates - if clips have similar names.
I was hoping there's a simpler way to make this work - like a settings file, or a pre-written xml importer that can just have some tags turned on and off based on criteria.
Just verified - I don't need UUIDs. I should probably change the subject line of this thread or start a new one.
What I do need is the comments section.
So - any idead out there how to bring in the comments section in XMLs into Premiere (and out again)?