Welcome, Guest
Username: Password: Remember me

TOPIC: Multicam clips duplicate on XML import

Multicam clips duplicate on XML import 05 Mar 2019 07:51 #99154

Hello there,

Here is my situation: working on a feature length documentary with a fellow editor who is overseas. She and I have (fairly) identical hard drives, all our footage organised the same and we started from an Identical library (massive amount of logging and keywording done).

Now we are exchanging XML project files (timelines), but when I import an XML, all the Multicam clips used within it seem to "regenerate" in the browser and are imported again into the event. I can not delete these duplicates without affecting the timelines I just imported.

This is problematic, not only because it clutters up the library with duplicates, but the new multicam clips are also lacking all the keywords. It ruins any efficient use of the find-frame function and is just hella messy overall.

I can't believe this is normal behaviour, so what am I doing wrong?

PS: one thing to note is that I like to have my timelines (projects) in their own event (containing no media). Could that be a problem?
Last Edit: 05 Mar 2019 10:01 by davíð alexander.corno. Reason: one word missing
The administrator has disabled public write access.

Multicam clips duplicate on XML import 05 Mar 2019 10:34 #99156

  • ronny courtens
  • ronny courtens's Avatar
  • OFFLINE
  • Moderator
  • Posts: 4188
  • Thank you received: 886
  • Karma: 195
Hello David,

It's just a matter of how you transfer the project to your co-editor. Short story: don't just export an XML from the Project, but first copy the Project over to a new Event in your Library and then export the Project XML. My good friend Sam explains this in full detail here. It starts around 6 minutes:



- Ronny
The administrator has disabled public write access.

Multicam clips duplicate on XML import 10 Mar 2019 01:13 #99229

Thank you so much Ronny! This was very informative, albeit not quite successful... What Sam Mestman demonstrates is how to move projects (timelines) between libraries without getting multicam/compound duplicates, but there is no XML-ing involved. Luckily our two libraries have all the media and cache externally, so even though it's a massive project (4000+ video files, more sound files) each library is only about 220mb – which we can easily ship over the internet back an forth, to then import projects (timelines) the Sam Mestman way. Not as easy and elegant as sending 100kb XML files, but a workaround I will make do with for now.
The administrator has disabled public write access.