FCP-X XML scaling issues in Resolve
Posted: Wed Jul 22, 2015 11:29 pmI am having a problem with scaling after importing an XML version 1.4 that was created in FCP-X.
I am hoping someone here can help me out, before I lose my mind.
After importing the XML, and using the clips I've already imported into Resolve, everything is found and the timeline looks good.
There are multiple transforms on some clips that were created in FCP-X. When I look at the transfer numbers for each clip, i can see that the numbers are not default, indicating that those number did indeed make it through via the XML. This is good, one would think.
I am also using a linked reference movie of the project.
The problem is this - when I compare the clips on the Resolve timeline to the ones in the reference movie, on the clips that have transform numbers on them, the scaling looks different. Both clips have a scale on them, but the clips in the reference movie are scaled more than the clips I see on my Resolve timeline.
Has this behavior been noticed by anyone else out there? Is this a bug? Or am I doing something wrong?
BTW - I have never had this issue on an XML created by Premiere CC or Final Cut Pro 7.
I am hoping someone here can help me out, before I lose my mind.
After importing the XML, and using the clips I've already imported into Resolve, everything is found and the timeline looks good.
There are multiple transforms on some clips that were created in FCP-X. When I look at the transfer numbers for each clip, i can see that the numbers are not default, indicating that those number did indeed make it through via the XML. This is good, one would think.
I am also using a linked reference movie of the project.
The problem is this - when I compare the clips on the Resolve timeline to the ones in the reference movie, on the clips that have transform numbers on them, the scaling looks different. Both clips have a scale on them, but the clips in the reference movie are scaled more than the clips I see on my Resolve timeline.
Has this behavior been noticed by anyone else out there? Is this a bug? Or am I doing something wrong?
BTW - I have never had this issue on an XML created by Premiere CC or Final Cut Pro 7.