Unable to update projects and events FCP X 10.1 is not recognizing my SAN disk

What's the question?

Same issue... I kept all my Final Cut Project and Event folders in the root directories of their respective external drives. I'm absolutlely maticulous about storage - I keep all my original media in separate folders with dates and a brief description on them (it's pretty much all h.264 .mov's from a 5D3 and .wav files from a zoom H4N from each shoot). I would then import that media directly into my event folders on the same drive, without transcoding or copying. I'd then create a new project on the same drive, and I'd be off to the races editing.

The update to Mavericks and with 10.0.9 seemed to brake FCPX... super sluggish, compount clips going offline and unable to reconnect, export/ render issues, etc, etc. Had to roll back to Mountian Lion and then everything worked again. I thought 10.1 might have taken care of some of those issues, but things are even worse now after a second attempt upgrading to Mavericks and 10.1. One external drive encountered an error while upgrading the project/ event folders, and now 10.1 won't recognize the library on that drive or allow me to open it. Another external drive with the same type of file structure "updated" and I can see all my media in the library, but the project files are nowhere to be found in the library. Combing through the forums yet again, but there doesn't appear to be a solution... what should I do now?

As much as I love Apple, FCPX has been an painful experience from day one, and I'm beginning to feel like a continuous/ ongoing beta tester.

Same problem with slow performance - not able to share a project. Tom Wolsky we believe suggested to turn off the App Nap feature of FCP which came with Mavericks. It worked for us! Thank you! (With Finder, go to the FCP application, do CMD + I (info) and turn off App Nap in the left window. It solved the sluggishness problem.

Hi Sevamma, thanks for your reply, but I tried that a long time ago when I made my first attempt at upgrading to Mavericks and 10.0.9 - it had no effect on performance or any of the other problems I was having.

However, I have found a partial fix to my new problems upgrading external drives to 10.1 and Mavericks ...I noticed that a few of my external drive's Sharing & Permissions were set to "read only" and the "Ignore ownership on this volume" was unchecked. I've had problems with FCPX and these settings in the past, so I restored the external drive to it's original state from a backup, set all the permissions to "read & write", checked the ignore ownership box, and then attempted to update the Projects and Events through 10.1 again... it worked this time without an error! It's odd, because the permissions have changed on their own from time to time. Anyone know why?

The only issues I've encountered so far is that each updated project's timeline needs to pre-render again in the project's timeline (10.1 seams to be overstepping the project's old render files and wants to create new ones), which takes a while... it makes a pre-rendering pass... does some stabilizing/ optical flow analysis... does some more pre-rendering... most of the project's orange render bar clears, but some still remains... scrubbing/ playing the playhead over a few of those leftover orange areas prompts FCPX to render them, but... I'm still left with a few orange areas that won't complete their optical flow anaylsis. Those areas drop frames during playback/ stutter in the exported file... so I'm left with no option but to tweak them in some way so that it forces FCPX to re-pre-render the clip in the timeline. A simple roll of the clip by a single frame in either direction is enough to force it, but I wish I didn't have to do any rendering/ tweaking in order to work with my old projects.

My advice... backup all your drives, set all external disk permissions to read & write, check the ignore ownership box and then cross your fingers before updating. Also, save your old projects and events folders when FCPX asks you just to be safe. If things appear to have gone smoothly during the update, go through all your projects to make sure everything's working as it should before you make your next backup (all of my external drives have a cloned backup, so a stitch in time saves nine before overwriting your backup).

Beta tester reporting back for duty, lol.

I think I found a solution too, but it has to be confirmed by someone else.

The external drives that refused to update were formated in ExFat. So I tried to move an event and a projet on another drive with a different format (Mac Os Extended). I launched the update with FCP 10.1 and, BINGO, this time it worked, no error message. So maybe the ExFat format causes trouble for the updates...

Chiquard wrote:

I think I found a solution too, but it has to be confirmed by someone else.

The external drives that refused to update were formated in ExFat. So I tried to move an event and a projet on another drive with a different format (Mac Os Extended). I launched the update with FCP 10.1 and, BINGO, this time it worked, no error message. So maybe the ExFat format causes trouble for the updates...

It has always been clear in FCP X documentation that the volumes containing projects and events need to be formatted as Mac OS Extended. I believe your observation may well help other people suffering from this problem.

Great finding. Thank you for sharing! All my external drives are formatted in ExFat. That could explain the problems I've had upgrading to FCP 10.1 Before I re-install 10.1 next time, I will transfer all my Events and Projects to a new drive in the recommended format.

Hi all,

I have the same problem - FCPX won't let me update my files from 'Final Cut Projects' or Events to libraries - they are shown as ghost files and I can't select them.

My hard drives are Mac OS Extended, the root folders say 'Final Cut Projects/Event's rather than Final Cut Projects- Hidden, and I have read/write permissions for the hard drive.

Any other suggestions of what to do?

Thanks,

You do not select the folders. You select the drive to update the projects and events on that drive.

D'oh! THANKS!!!!

I just updated to 10.1.1 from 10.9, wasn't expecting the update projects and events process, was skeptical the second I saw it. But I allowed it to continue anyway... well another awful update, as far as I can tell it updates all the projects/events well enough providing you haven't grouped any of your projects into subfolders. All projects that I had grouped into a sub-folders within the project manager failed to update. I had some error message about some stuff not updating or missing files... basically Apples way of saying there programming is crap and they didn't test it properly, and therefore it doesn't work.

Looks to me like they forgot to refine their testing process enough to realise that it doesn't work when projects are grouped in folders. Just another example that Apple can't develop well formed programs, every major update just causes more problems than they solve, there is something seriously wrong with the way Apple now develops software. Always more hassle than it worth.

I returned to 10.9 within 20 minutes of updating.. there it will stay for the time being... though it seems there may be an easier work around for updating using the now free to use Event Manager X:

http://assistedediting.intelligentassistance.com/downloads/Event%20Manager%20X.d mg

As recommened here:

http://www.fcp.co/final-cut-pro/tutorials/1304-upgrade-your-events-and-projects- to-fcpx-10-1-libraries-the-smart-way

The update is now six weeks old and there's a ton of stuff from Apple, Ripple, Intelligent Assistance, and others about the process. Admittedly some user's workflows in earlier versions don't lend themselves to easy updating. Who knew that some were putting projects and their referenced events on separate drives.

Who knew? That's the whole point of design testing and thinking about the process that your creating, Apple should have known, they created the software and should be aware of it's capabilities and what's possible and not possible to do. When you write software you then test it in every concievable manner to check if it throws up any problems or glitches... These are not some far flung one in a million potential issues, they are fundamentally obvious operations that will take place in use, and if there was any cohernet testing process the chances of them being missed would be highly inprobable. This is an example of something that is rushed out to deadlines before their fully tested, that or the testing process is completely flawed.

I use seperate multiple internal hardrives, and the only projects that haven't updated properly are those that are organised in sub-folders, referenced projects and events are almost all located on the same drives. Though most of my projects are organised into sub-folders, and that clearly seems to be causing the issue, as they are the only projects that didn't update and can't be loaded in FCPX.1.1

The only way to correct this issue in a coherent manner seems to be using an external application designed by someone other than Apple. New feaures are not much use if the update process screws everything up, I'll take stability first and foremost. Their seems to be more than one bite taken out of the Apple these days.

Event Manager X is certainly convenient but you absolutely don't have to use it. You can easily move the events and projects into the correct location manually.

The subfolder issue is really minor and easily worked around. It wasn't worth spending days coding around it when any user can easily work through it. You make it sound as if it set your system on fire.

You are having a laugh... days recoding... I doubt it amounts to much more than a few lines of basic code, it's bad oversight not a massive coding issue. If it was just the one issue I wouldn't make such a point about it, but this is just typical of the constant rubbish that Apple chuck out these days, I spend more time faffing around with work arounds and searching for solutions to poorly programmed applications than I do on actual work.. it's all a constant break in the flow, and I am sick of Apple using their customers as bunch of BETA testers. It would be far easier for them to spend the time and money and get things right than waste millions of peoples time. They are typical of this society that bases everything more and more on profit than usability. I will never learn another application written by Apple, I may well stick with the ones I already use, but I see no point in repeating this sort of experience with the appalling functionality that has plagued this application for 2 years by learning anything new Apple puts out.

Minor it maybe, but all these constant minor issues have become a bit too major... it's not surprising so many people are going back to Windows systems. I only upgraded to 10.1 in the hope they sorted the horrendous key-framing interface out.