-
Your Process for Starting a New Project
This may seem like a question that belongs in the Basic forum, but it really requires the knowledge of advanced users with a firm grasp on media management.
First off, I’ve been using FCP for 3 years in a broadcast environment and would classify myself as an advanced/intermediate to advanced user. My question relates to media destinations for new and ongoing projects.
Everyone in our facility took a several-day training session conducted by a Mac certified instructor. His instructions for starting a new project were the following:
1) navigate to your media drive
2) create a new folder, call it “(project name here)”
3) open FCP
4) create new project, and save it in the new folder you created in step 2
5) go to System Settings
6) set Scratch Disk as the folder you created in step 2Now all your materials associated with this project will be neatly located in one folder. Everyone in my shop does it this way because that’s how the “expert” taught us to do it.
The problem is that if you do it this way, you have to manually change the scratch disk each time you move from one project to another, otherwise you end up with render files and/or captured media in the wrong folder (a media management nightmare). FCP changes automatically if you simply set your Scratch Disk and forget it, right?
Our method seems like a work-around that’s fighting against the software, and has fewer pros than cons.I guess this method would be fine if you only work on one project at time – but who has that luxury?
So what’s your process for starting a new project?
Thanks in advance.
-
11 Replies
-
[Jeff Pierce] “The problem is that if you do it this way, you have to manually change the scratch disk each time you move from one project to another”
Correct. Yeah, this is a pain, but this is how you have to do it.
[Jeff Pierce] “FCP changes automatically if you simply set your Scratch Disk and forget it, right?”
If you have ONE scratch disk, and set that disk, and then use multiple project, the media should go into the project folder specified by that project. So if you have PROJECT A open, and capture, then the footage will go to HARD DRIVE>CAPTURE SCRATCH>PROJECT A. If you then open PROJECT B, then the captures should automatically go to the PROJECT B folder on that same drive.
The issue is when you have separate capture scratch drives for each project. If you have separate drives, then you need to change the drive manually in the project. If you have one drive, it changes automatically.
[Jeff Pierce] ”
So what’s your process for starting a new project?”I have a tutorial DVD that covers all of this…if you are interested.
Shane
GETTING ORGANIZED WITH FINAL CUT PRO DVD…don’t miss it.
Read my blog, Little Frog in High Def -
Thanks for the repy Shane.
So if I don’t use multiple scratch disks (which I don’t) then there’s no reason for the method I discibed, right?
Again, thanks in advance.
-
I use a single scratch disk and let FCP create the relevant folders for me. Like you, I really can’t see much benefit of having all of your media and render files in the same place as your project files, graphics etc. This has been discussed, and as far as I’m aware it doesn’t make any difference in terms of performance.
All of my media goes on the external RAID 5, and all of my project files, graphics, client samples etc go on my internal RAID 1, all arranged into corresponding folders. Final versions then go onto a second external RAID 5, arranged by date for easy reference.I find this system to work really well, but I think it’s down to personal preference. Your problem is that you work with other editors who are using a system you’re not comfortable with. I’m on your side with this one.
-
“Your problem is that you work with other editors who are using a system you’re not comfortable with.”
Bahh…to hell with them! 🙂
Seriously though, several of them hate it to, but they’re less likely to question process. If I introduce them to a new method that utilizes the software more effectively, then I think everyone will be on board with it — we’ll see.
One quick follow-up question: I frequently have projects that contain no digitzed video. They’re either all graphics or the video comes as QT files. In this case, FCP never creates a folder on the Scratch Disk for the project — so I have to do it manually (and make sure my project name matches that folder name exactly. Any thoughts on a better practice for this?
Again, thanks in advance.
-
[Jeff Pierce] “FCP never creates a folder on the Scratch Disk for the project — so I have to do it manually (and make sure my project name matches that folder name exactly.”
I wouldn’t bother with manually creating a capture folder if nothing is being captured anyway – just work on your project as normal, then when you render FCP will create a render directory relevant to the name of your project file. As long as your media is on a fast, secure RAID then there’s nothing to worry about regarding performance – just stick it all in a folder called ‘Project A Media’ and separate into folders such as ‘Graphics’ ‘Video”Audio’ etc. That way you can import the folder called ‘Project A Media’ into your project, and it will maintain an organised directory structure in the FCP browser.
-
hey shane, i can’t get that link to work for your Organization in FCP… is it correct?
-
Here:
https://store.creativecow.net/p/63/getting_organized_in_final_cut_pro
Shane
GETTING ORGANIZED WITH FINAL CUT PRO DVD…don’t miss it.
Read my blog, Little Frog in High Def -
Here’s what I do and have done since VideoCube, Media100, Avid and FCP. It has also generally been my understanding that performance wise, this is also best, but I have done it other ways and noticed no problems or differneces.
On system drive I have a projects folder. In that folder, broken down by clients, I have folders for each project. Within that folder is the FCP project file, a folder for psd files, a folder for after effects projects, a folder for dvd sp projects, a folder for illustrator files, a folder for jpegs, etc. Whatever the project requires determines the organization. Mainly, the project folder is created media like still images and maybe small sound files. The point is this is a folder that will stay on my system and doesn’t contain any timecoded media. I always put an alias of currrent project folders on my desktop.
I let FCP create the capture scratch folders. I have my media drives selected and let FCP do all the orgainizing work. Capture scratch folders and render folders are reserved for captured timecoded media. I never render an AE animation to my capture scratch folder, or put music imports in there. In other words, it wouldn’t be the end of the world if the folder were accidentally deleted. It can all be recaptured.
On the media drives, I also create other media folders for things like After Effects renders, LiveType renders, Motion Renders, Quicktime Exports for compressor and/or DVDSP, Music files, Stock Media and stuff like that.
Works for me. Keeps project files separate. Keeps renders on fast drives. Keeps TC materials separate.
Bret Williams
Web Design . Motion Graphics . Video Editing
http://www.bretwilliams.com -
I would agree with Brett, it seems a little crazy saving your project, autosave projects and media all on the same drive. If it dies, you lose everything!
If you keep your projects and media on separate drives, then when one goes you can at least either drag the media into a new project and you have all of your logging (and your timelines via the autosave folder), or if your media drive goes you can just recapture using your project.
I partition my main drive into a system partition and a projects partition. Any project file of any sort is on that drive, organised by software/client/job.
Of course the beauty of FCP is that you can do what you like, there is always another way.
best wishes
Nick -
My media is a mirrored raid so that’s protected. And the system/project drive is time machined, so pretty safe and backed up!
You could also have autosaves to a third drive.
Reply to this Discussion! Login or Sign Up