-
Interchange – why leave XML out of the fun?
Imported translated FCPXML to XML in to Pr CC 2015 using XtoCC.
This leads to this error:
It does not import in Pr CC 2014 or Pr CC.
That same XML works flawlessly in FCP7 which “hasn’t been updated” in 5 years.
It works in Ae CC 2105, which has a version of what used to be Wes Plate’s Automatic Duck (Pro Import Ae).
This same XML works flawlessly in Resolve 11.
Will more CUDA performance help me here? Maybe I need a $5,000 GPU to get things done?
-
4 Replies
-
I’m concerned with who the ‘we’ is trying to save your project.
John Davidson | President / Creative Director | Magic Feather Inc.
-
Now we get to subscribe to and rent error messages? 😉
-
[Jeremy Garchow] “It does not import in Pr CC 2014 or Pr CC.
That same XML works flawlessly in FCP7 which “hasn’t been updated” in 5 years.
It works in Ae CC 2105, which has a version of what used to be Wes Plate’s Automatic Duck (Pro Import Ae).
This same XML works flawlessly in Resolve 11.”
Hopefully you’ve shared your XML with Greg Clarke at Intelligent Assistance. My experience is he’s very responsive and helpful with fixing any bugs in XtoCC.
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
https://lnkd.in/Cfz92F
facebook.com/dlawrence
twitter.com/dhl
vimeo.com/dlawrence/albums -
I’ve seen this happen as well. What I did was import into Resolve and export a new XML.
But the in’s and out’s of Adobe-land can be shaky.
Reply to this Discussion! Login or Sign Up