10.0.4 performance much worse for me...

Make an empty project on the additional drive, and make an empty event on the additional drive, quit FCPX, re-launch, you should see the projects there if you moved them from the other user account ~Home/Movies/Final Cut Projects directory.

I hear you man, I only want to see if we can isolate the issue here, reason being is that many peple are reporting performance increases, my self included. You mention the term multi-can synced files being done by plural eyes, being unfamiliar with the app, can I ask do you make the multiclips in plural eyes or just the sync clips?

But I didn't move anything. Maybe it is a directory problem. I'm not keeping the FInal Cut Events or Projects in the Home/Movies/...directory. I opted to keep them out on the 1TB internal, because the SSD bootdrive with the apps is too small to handle all of the files associated with my workflow. Are you saying I need to copy all of the Projects over to the SSD bootdrive in the new User account to be able to access them? I'll run out of space just trying to perform this simple test!

No, absolutley no need to copy the files to the SSD. So the projecxt and event are on the the 1TB at the root in FinalCut Events and Final Cut Projects? If so, to get the new user account to recognize those projects and events you need to first create an event and project on the 1TB. It defaults to only the internal.

Just so you know what happens with Pluraleyes, which is a standalone app. 1) In a new project, you take one set of camera files from your event browser and put them into a story line, then you take the next camera's files and you create a second story line above the first, and so on with the third camera files, as well as adding the most important file for me: my external audio file which will replace all inboard camera audio. 2) Then you export the Project as an xml file. 3) Lauch Pluraleyes and perform the sync function. This creates a multicam clip (MC) which is then inserted into the Event browser, and also pops up in a new timeline in FCPX. I've done this same syncing with another project and there are no artifacts or problems with playback. In fact, the syncing is way more accurate than in FCPX. FCPX gets really confused with small clips and areas such as applause where the audio information does not give it enough to go on. Pluraleyes is so far flawless with this. So in other words, I'm taking all of my individual clips and the external 96K audio files and I'm exporting them as an xml. Pluraleyes takes over with the xml file and creates one synced multicam file ready to be edited. Does that help?

Sorry virgil s. Must be a communication problem. How can I create empty Final Cut Event and Project folders on my iTB internal, if the folders are already there in the first place? For you knowledge, I'm organizing this as if I were using an external drive to house all of my projects and events. Up until now everything has been rock solid. The app is residing on the SSD bootdrive along with the home directories, Movie folders, etc. What is different with my setup is that I have taken the Final Cut Event Folder and the Final Cut Project folder and all of their contents and kept them on the separate internal 1TB drive. I don't understand what you are saying. I can't have identical folder names on the same drive. It will default to Final Cut Event folder2, in the scenario you are suggesting. Might be worth a trip to the genius bar, because this may be a bit beyond my technical abilities.

I meant, within FCPX, in the new user account, select the mediadrive and create a new event.

In fcpx in the project organizer select the media drive and create a new project. This will look on the drive for the events forlder and the projects folder that already exist and will add them to the list at restart.

Tried that. Doesn't work. From within FCPX in the user account, only the SSD shows up as an available drive. The other internal does not show up listed in the Library and is not associated to FCPX. I can create a new event and a new project but they are only created to the bootdrive. There is no linkage showing up to the other internal's events and projects.

That's really strange, both drives should show up. Try this. On the 1TB internal, rename the folder Final Cut Events and Final Cut Projects to *Final Cut Events and *Final Cut Projects. Then start FCPX again and see if the 1TB is visible in the UI. If it is create blank event and project on the 1TB. Close FCPX, then move the contens of Events and projects into the newly created ones. Make sense?

This is all performed from within the new user account, right? I certainly don't want to endanger what I've already worked on in the admin account.

Yes, in the new user account, and then instead of moving the directories, copy them.

The events and projects are well over 600 GBs! Copying is not an option. I don't have the capacity to try this out. Maybe in a few weeks after I can archive off all the current projects. In the meantime, it looks like I'll be using proxy files until I have time to deal with this.

I tried the renaming trick and no go. FCPX does not recognize the internal 1TB HD 2 as a mountable drive in the Library. It only sees the Bootdrive, and its directories. Sorry virgil s, it seems you are stabbing in the dark. I appreciate the help, but I'll probably have to consult an Apple technician on this, unless the FCPX team adds a quick .0.5 update to address this problem. My main gripe with all of this is that there is no way to rollback to a previous working version. Once you opt to go for the upgrade, all the existing media files go through some kind of initialization process that makes them non-compatible to earlier versions. This is truly backasswards! Anyone working professionally has to be able to quickly revert to an earlier version. The new app store concept is very shortsighted and lacking in this regard. I've put this into the Apple feedback, and hope that there will be considerations made for professionals needing to have ANY version on hand to complete a specific task, even if it means reverting to 10.0! This makes the entire product look like a sloppy series of beta releases, a bs 0.1, bs 0.2...one after the next, and ergo making the initial launch not even up there with alphaware status.

Come on Apple. There are a few professionals left out here who would still like to use your products, but if you are caving to the consumer masses, we will eventually shut the door on you. Jobs wanted to keep the professionals in the fold, but as things stand today for former FCP users, it seems the multibillions of profit from the "good enough for the masses" tablet market and the CE line of stuff are what is driving the company. Come on!! 100 billion in the bank and you can't come up with one tidy recode of one software product?! Even the smallest boutique shops with a tiny fraction of your R&D budgets are vetting and cranking out solid releases of software. What's the problem here? Or maybe this IS indeed the grand strategy? A broken iMovie for all.

Since FCP X when run in the new account does not see the hard drive, this could be a permissions problem.

Is the new user an administrator account or regular user? It should have administrator privileges.

You could try to set "ignore ownership on this volume". Although some people seem to frown on this, it is the simplest most effective way if it is a machine that is completely under your control.

Select the drive on the desktop in the Finder, do Cmd-I to get the Info window and tick the box at the bottom.

This will make the hard drive accessible to all users of the machine.

The events and projects in a non-system drive ought to be available under all accounts, barring file-system permission problems, so this should at least let you experiment and figure out if your problems are related to your normal user account or not.

Went ahead and tried this. Now FCPX sees the drive in the Library, but claims there are no events or projects on it. Won't allow me to open it in FCPX to reveal anything. Guys, all nice tries, but you all have insufficient skills at troubleshooting a single remote system like this. Let me get Apple to look into this. Many thanks though for your efforts.