XML Import

[[email protected]]

SO.... I'm thinking I know this answer but I thought - you guys are so much more savvy than I.... We can import XML from PluralEyes - something I do all the time, so I am familiar.

I have a project from a client that has had a long-range project running, and was using a different studio that used FCP. I have all the assets including those saved XML files from 2017.

I cannot import them as I do with PluralEyes - they are in the main file looking thru Windows but do not show up recognized in Edius. While it's not crucial that I have these edits, it would make a bit of a time saver.

Since we CAN import the PluralEyes ones, I was wondering if there is a way to import these older ones or even any ones other than PE.

If so - How?
TY!
S.

[BernH]

SO.... I'm thinking I know this answer but I thought - you guys are so much more savvy than I.... We can import XML from PluralEyes - something I do all the time, so I am familiar.

I have a project from a client that has had a long-range project running, and was using a different studio that used FCP. I have all the assets including those saved XML files from 2017.

I cannot import them as I do with PluralEyes - they are in the main file looking thru Windows but do not show up recognized in Edius. While it's not crucial that I have these edits, it would make a bit of a time saver.

Since we CAN import the PluralEyes ones, I was wondering if there is a way to import these older ones or even any ones other than PE.

If so - How?
TY!
S.

When you say the client used FCP, do you mean FCP7 or FCPX? FCPX writes a different version of XML that Edius does not read. Edius does read the FCP7 version of XML.

If you have Resolve, you should be able to import the FCPX XML there, and export that out as an AAF or an FCP7 XML, which Edius can read.

If you don't have Resolve, the free version of it available on Blackmagic's website, is a great tool for doing these kinds of conversions.

[[email protected]]

Great!!! TY
Will try that :)