-
All replies
-
Helpful answers
-
Jul 12, 2016 10:48 AM in response to stopmotionby Meg The Dog,Are you asking about the FCP project file or about media files for your project?
MtD
-
Jul 12, 2016 7:19 PM in response to Meg The Dogby stopmotion,I was asking specifically about FCP 6 project files (the ones w/ the fcp extension), not the media files that you import into them. I read in an excerpt from a book on FCP 7 that you can locate your FCP project files anywhere you like and that the author no longer suggested keeping them on the boot drive which used to be Apple's recommendation also. I was wondering if there were any FCP 6 mac users who had their project files located on a drive other than their boot drive.
-
Jul 12, 2016 8:51 PM in response to stopmotionby Drew Reece,★HelpfulI'm quite sure we used to have them scattered across many disks
The .FCP project files are pretty small & not written to that often I don't think it make much difference to your SSD to move them elsewhere. You will want to relocate the autosave vault in the FCP settings too if you are that concerned about what is written to your boot disk.
I think you get a lot more performance benefit from having a scratch disk & another disk for the large media files.
-
Jul 12, 2016 8:51 PM in response to Drew Reeceby stopmotion,Thanks for your feedback. I do have my scratch disk folder on an external drive where I also store all my media files. I think, to be cautious, I will move my project files off my boot drive in order to save some wear on my SSD.
-
Jul 13, 2016 1:59 PM in response to stopmotionby Shane Ross,★Helpful" My boot drive is an SSD drive and I'd like to be writing to it as little as possible."
Why? Writing to SSDs is very fast, that's the point of them. Putting it on an external might slow you down again. And they take up VERY little space.
Store them on the boot drive. Best suggestion
-
Jul 13, 2016 12:22 PM in response to stopmotionby Drew Reece,Ideally the scratch disk should be a separate disk, not the same as your main media disk. That way the IO is not all reading & writing to one bus. Spinning disks also have seek time which would slow performance when FCP had to read/ write media & save to scratch (I'm assuming the disks are large spinning models).
I think you are focusing on the wrong thing by moving the project files, SSD's will eventually fail - they have limited writes. Preventing a few kb of writes per day seems like it would be a negligible benefit. I suspect your browser or other apps (with log files) write more data than that to the SSD every day.
You should max out the RAM before you consider tiny changes like this, memory can also be written to disk, which will be the boot disk by default & may be many MB's per day depending on your setup.
Sorry if you have considered all this & already setup your system to max out performance, it just seems like you may be missing a bigger picture - maybe it is us that are not seeing what you have already setup.
-
Jul 13, 2016 1:56 PM in response to Shane Rossby stopmotion,Initially I was concerned about unnecessarily shortening the life span of my SSD boot drive because of the limited writes, but also, I had read in a book on FCP 7 where the author (Larry Jordan) said he no longer suggested keeping your project files on the boot drive and that you could locate them anywhere. But after considering your input and that of Drew Reese, I'll just leave them where they are.
Thanks for your feedback.
-
Jul 13, 2016 1:57 PM in response to Drew Reeceby stopmotion,Switching the scratch disk to a separate drive is something I can do. Thanks for the suggestion and for your other input as well.
You and Shane Ross have convinced me to leave my project files where they are.
Appreciate the replies, guys.