Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Partition to protect FCPX Application and Media Files

I want to keep 10.0.9 and all my current Events and Projects until such time they are "finished" (if ever). There are a lot of them and there has been a huge amount of time and effort to create and edit them. Many of the video files are irreplaceable. Additionally, there is not an unlimited amount of space to back everything up and some space is needed for 10.1 and future work to this needs to be considered.


Given: 10.0.9 works with a database system. We know that Events and Projects need to have an electronic path connection, hence, moving things around could "break" the path and then things won't connect and won't work. This is a concern.


Given: My Mac Pro (MP) has a 250GB SSD drive where 10.0.9 is located and, consequently, it has with rather limited space on that drive. The MP also has a 3TB and a 2TB drive where media files are located. However, there is another copy of 0.9 on a MacBook Pro (MBP) but this is only for backup purposes and is not used as an edit machine, although it has in the past.


In kb/HT550 step 1 to save a copy of FCPX it says to "... create a new folder in the Applications folder." Note that the kb is silent about any situation where one might have a second copy of FCPX. The MP is the main computer for doing video editing and there should be both the new .1 and the old .9 versions on it, and both need to be operational. The kb instruction says to compress the .9 version as a zip file. This is not an operational file.


Partitioning:

Question 1: If the existing media files are put into a partition on the 3TB drive and the .9 FCPX version is put into a partition as an operational application on the SSD, can it be used to edit files on the 3TB drive?


Question 2: Then, if the .1 version is downloaded and put on the SSD, will it cause problems with the old .9 application and "it's" media files (inside a partition on another drive)?

Mac Pro, OS X Mavericks (10.9.1)

Posted on Jan 8, 2014 6:48 PM

Reply
21 replies

Jan 10, 2014 11:16 PM in response to Tom Wolsky

Actually, that is just what I got through doing. Copied it from the MBP to a Passport drive, then from the Passport drive to the MP but on one of the hard drives and not the SSD that had the new 10.1 version.


Puting it on the Hard Drive along with all the X.9 video media visually puts the two together. I'll rename it tomorrow but at least it works the way it is.


The next question, though, is going to be how to handle all the X.9 files: Events and Projects. I'll go back and read up on the KB articles to see what they might have to say as well as do some searches for posts here.


As for now, though, I'd consider this case is closed. WHEW!!!


Note to Apple: PLEASE, for someone elses sake, Please write a KB article about the ins and outs of maintaining the "old" 9 version along with the "new" .1 version. Not everyone will find this thread. Or the KB for that matter.

Jan 11, 2014 8:47 AM in response to Tom Wolsky

In the KB HT5550 it would be a very good idea to add in Step 2 or 3 something that says:


"Note: if the old X.9 application is not compressed/zip-ed then it will be replaced by the new X.1 version!"


And, the old X.9 version will be long gone (unless there is a copy somewhere else).


Also, it would be a good idea, since some users have a second drive on their machine, to provide an option:


"For users that have a second drive, the old X.9 version can be moved to that drive and the new X.1 version installed on the main drive" (or words to that effect).


As far as those who have "outboard drives", I would assume (Uh oh!) that the same would apply, but I don't know. I was able to copy X.9 to a portable drive and then move it to the computer's second hard drive.

Jan 11, 2014 8:55 AM in response to Alchroma

Al - Your screen shot was really helpful and that is what really got me going. The devil is in the details and as always there are little nuances. Moving the old X.9 application to a different drive is what worked in my situation but maybe how it gets re-named makes a difference. In my case the name change wasn't that huge so whatever the programmers did with the algorithm to help the new X.1 application "find" the old version worked with the (re)named X.9 version I had worked in my case (darn it!).


Thanks again for providing your screen shot - "a picture is worth a thousand words."

Partition to protect FCPX Application and Media Files

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.