There aren’t too many to bring them in through the built in integration — in theory. I’ve had trouble accessing FCP projects through the tree.
On my computer, only one random FCP project appears in my tree. When I try to bring that FCP project into CatDV through the tree it gets distorted like the rest of my XML files. When I try to manually open another FCP project in the tree, it will not load in CatDV. It goes through the process of loading; it says it’s processing thumbnails, etc. But when it finishing loading, it says “Read only view on 0 clips from project (java.lang.RuntimeException: Negative source clip).”
One of my co-workers has had more success than I when loading FCP projects into CatDV from the tree, but he can’t figure any rhyme or reason as to why some projects will load and others won’t.
For these reasons, we haven’t been relying to heavily on the tree to connect FCP to CatDV.
I had considered that it might be a problem with the XML file that FCP is exporting and not a CatDV problem. I did test with the original QT files – QT player, CatDV, and FCP all imported the original QT files without any problem with the aspect ratio. The problem seems to be only in the XML file, not the original QT.
Bryson, when you say, “The good news is that your integrator should be able to easily edit the XML, if FCP is reporting it incorrectly,” I don’t know exactly what you mean.
Thanks for your help!
Erica