FCP Project Import

[john.wilson]

FCP Project Files do not import at all! My scenario is as follows:

I create a Final Cut Pro Project file (.fcp) and try to upload it into FCSVR by dragging the file into the FCSVR window while logged in as admin.
This throws an error that says, “Unable to analyse project – invalid format.”
Then I export the project as an XML file and upload it the same way and receive no error.

All of the files are uploaded beautifully as well as the .xml file; however, when I check out the .xml file, it is copied to the folder of my choice as a .fcp file! At least that is the extension that shows up. I can tell it is really still an .xml file because when I open it with FCP it converts it to a .fcp file (FCP informs me of this on execution).

After I make changes to the file and save it (using Command+s), I go back to FCSVR and try to check in the file I checked out. The file checks in just fine.
However, when I try to check the file out again, I get a different error message that says, “Final Cut Pro Download failed (Project File not found).”

I have checked the device, which is on my Xsan volume, and the file is there. Actually, so is the .xml file.

The only work around I have found is instead of just saving my changes with Command+s, I can export another .xml with the same name as the original and upload that file into FCSVR, but that will overwrite the file already there, making version tracking unavailable.

I have seen this problem in a few places and I wonder if it is around the board, or if it is just on some installs. Any ideas or fixes would be awesome.

NOTE: I have also posted this question on Apple's Discussion site. Here is the link: http://discussions.apple.com/thread.jspa?threadID=1648275

[MattG]

First - checking in the xml is confusing the process. Version 1.1 of FC Server expects to receive an actual .fcp binary during upload. It does the same when checking out: it delivers an .fcp binary.

I have a hunch that you are getting the invalid format error because your Final Cut Server itself is not logged in as the admin user. If this is the case, keep the machine logged in and see if you still have the issue with the original .fcp binary.

[john.wilson]

Wow, that seems to work fine. Is that the final solution for now then, just keep the server logged in as admin?

[keithkoby]

We're seeing this now and we are logged in as admin (the same admin that installed fcs) on The FCS.