Activity › Forums › Apple Final Cut Pro Legacy › Best location for fcp project file
-
Best location for fcp project file
Posted by Lava Bay on October 26, 2007 at 11:57 pmHi everyone…
I was talking to a colleague the other day about best practices with fcp projects/media management/etc. I was trying to explain to them why it’s a bad idea to save and open an fcp project file from the same drives that the media is stored on, but he wasn’t buying it. I tried to explain that media and render files should be stored on separate drives from the actual project file because of any number of potential problems, like slower system performance, crashing issues, etc. He still wasn’t buying it.
So I thought I would give the cow a chance to convince him. Any thoughts on the topic?
Nick Meyers replied 18 years, 10 months ago 6 Members · 7 Replies -
7 Replies
-
Shane Ross
October 27, 2007 at 12:06 amPROJECT file on main system drive, media on media drive. BACK-UP project file to media drive, or thumb drive, or other drive. But run the project file off the main hard drive.
If you lost the media drive, and the project was only on that…you will have lost EVERYTHING. Lose the media drive when your project file is safe on your main drive, all you need to do is recapture. Lose your main OS drive, then your project is backed up safe and sound on your Media Drive.
All bases covered.
Buying my FCP organizational DVD might not be a bad decision.
GETTING ORGANIZED WITH FINAL CUT PRO DVD now for sale!
http://www.lfhd.net -
David Roth weiss
October 27, 2007 at 12:11 amLava,
You might want to suggest to your colleague that he/she read the pretty books that came with their FCP software. Its all right in the manual on the first few pages about setting up a new project…
David Roth Weiss
Director/Editor
David Weiss Productions, Inc.
Los AngelesPOST-PRODUCTION WITHOUT THE USUAL INSANITY™
A forum host of Creative COW’s Business & Marketing, and Indie Film & Documentary forums.
-
Rich Rubasch
October 27, 2007 at 1:05 amI think even better than Shane’s suggestion is this. We have added a 500 gig drive to the open bay in our G5s. This is in addition to an internal 3-drive RAID in the Jive. We also have an external 4-drive Raid that our rooms can share via removable sleds.
Our System, apps and user settings etc are on the internal System drive. All project files for After Effects, FCP, DVDSP and the rest go on the 500 gig internal drive.
All media files and render files go on our Raids. Desktop basically has three drive icons. All of our edit bays are pretty much the same, so it’s easy to stay organized between systems.
Has worked for us…
Rich Rubasch
Tilt Media -
Glaremedia
October 27, 2007 at 1:28 amWe also back up onto apple idisk as i remember once an editor arriving at work one morning to find his Avid did not exist as thieves had taken it in the night!
-
Nick Meyers
October 27, 2007 at 1:32 amhaving the project file on the same drive as my media means i can pick it up and move it from system to system.
project backups go to a separate drive.
autosave vault is on the system drive.in a shared storage situation, with multiple people needing access to the same projects,
i’ve also worked with the project files on the same drive as the media.nick
-
Shane Ross
October 27, 2007 at 1:39 amI have worked on Shared Storage projects too. They ALL have the projects on their local systems…and backup to the SAN. This way only THEY can access the project file and make changes, but anyone can copy the backup to their system and access it.
Again, work locally, and then if you want to be mobile, just back up to the drive, then carry it.
BUT…to each his own.
GETTING ORGANIZED WITH FINAL CUT PRO DVD now for sale!
http://www.lfhd.net -
Nick Meyers
October 27, 2007 at 10:11 pmwe had seven systems, including 3 editors, who all needed access to the same pool of projects.
most larger projects are not just a “project” but rather a “cloud” of project files.
(as Mark Raudonis says “the SAN is the Project”)this was a feature, and we’d broken it into more than ten sections/projects. there was also a new dailies project each day, which needed accesing by various assistants.
editors could find themselves working in any section,
and assistants would need to “top up” the edit projects on a daily basisrather than confuse things with people having their own version of the project, and then who knows how many copies of those projects zipping around, we just made them all available to everybody.
luckily there were never conflicts about who was working in which section.another way to approach this might have been to have the projects and other, smaller, files on the SAN, but on a separate partition.
nick
Reply to this Discussion! Login or Sign Up
