Tutorial - Project Folder Organization
Wednesday, March 10, 2010 at 8:07PM On March 11, 2010 (100311 for those of you that were there…) at the SF Cutters users group meeting I presented my workflow and folder structure for the way I’ve been working for about 15 years. Its a proven method with a lot of thought that has gone into it. I don’t pretend that my way is the only way but it has been developed over time with much fore thought. I would really like to get a run down, step by step, of how other people work in order to compare notes and possibly come up with an even better organizational process.
Some important things to keep in consideration. The workflow has to protect the editor from dumb mistakes, keep track of versions over time so that when I producer says, “I want to see what we had last Friday again” you can find it, and it has to be open and inviting to others to slide into a project and finish up.
You can download a zip file of my folder structure here. Included is a sample project that includes my internal Bin Structure which is outlined here.
ANIMThis is where all the files that make animations would go. For example, After Effects Projects, Motion Projects, perhaps, LiveType Projects (you really shouldn’t be using that anymore) or if you are into 3D you could put your 3D files there. These are the files that MAKE your animations, NOT the animation renders themselves.
ANIM RENDERS
Here is where you would put the QT movies that are created by your ANIM files. One exception to this would be your Motion projects. Since you don’t need to render a movie as the output of Motion and can drag those files directly to your timeline you probably won’t need to put any output files from Motion in here. The main reason for keeping these separate is for archival purpose. If, in the off chance you REALLY need to save some disk space you could, in a pinch, delete the entire contents of this folder because all the files needed to recreate these movies are in the ANIM folder. (Provided of course everything is filed correctly.)
This is where all your compressed files would be stored. Web files, wmv’s, FLV’s small web sized QT files or specialty compressions for deliverables.
docs
This folder is where I put notes about the edit. Mostly it stores correspondence from a producer with notes about what has to be done still on the job. If I receive notes via email, I save the email of course but I’ll also copy the contents of that email into a text file and store it here. Often called “100308 Edit Notes” as I complete each of the requests I’ll mark them as completed, maybe by BOLDing it or something similar.
All the files needed to create a DVD deliverable are stored here. MPEG compressions, MENU files, BUILT folders (the file you’ll burn to the DVD). All stored in one place.
All your Final Cut Pro projects live here. The main project you are working on will be named logically so that it makes sense at a later date. Conspicuously missing will be version numbers. Many people make different version number on their Final Cut Pro project. What this ends up doing is creating many sub folders in your Capture Scratch Folder, which is just messy. Instead, a better practice is to periodically make copies of your project file and date and time stamp them and put them into a sub folder called “zzOLD”.
This practice is useful at the beginning of a day, the end of a day, when you are taking over for another editor and want to have a reference to refer back to, or if a client leaves you to work a lone for period of time. This way you can always have a copy of not only the timeline but the whole project, ‘at the point they left’. Great for blame assessment.
This is where you store all your vector based art work that you are working on. Do not put original art supplied by a client here… this is the versions you will work on, tear apart into layers, etc, however, the original file that the client sent you should stay in the “Original” folder below.
This is where you would store your non-timecoded media. Files from stock libraries or client supplied media. Even if you own the stock library, you should put a copy of the file in this folder. This allows you to back up and archive the entire project in one folder.
NOISE
Anything that makes noise. VO, Music, or Sound Effects. Don’t just leave this stuff in your iTunes Library. Again, this will make it easier to back up an entire project at once.
Orginal
As mentioned before, this is where you will store any client supplied logos and elements, this assures you have a copy that is absolutely untainted and can always be referenced in the event there is a confusion about what something was suppose to look like.
PCT
Flat still images go here. Pict, JPG, Targa, Tiff, PNG. They all go here. You also may consider having some standardized files that you use often in here so that you don’t have to go find them every time you start a project.
Layered Photoshop documents go in here.
This is a very controversial part of my system. Many trainers will tell you that you should never put your media or in this case your “Scratch Disk”, and your project file, in this case the contents of the “EDIT” folder, on the same drive. I understand that and yet, I have literally managed millions of dollars in projects with this method and never lost anything, ever. The upside of working this way is that again, with ONE FOLDER, the Job Folder, you can backup and/or archive this entire project.
When its time to deliver a project I always export a self contained movie of the current timeline. This file is then used to create all the deliverables. Whether its a DVD compression, a web compression, or an H264 deliverable, this file becomes the master that everything is made from.
Reader Comments (13)
Great talk tonight, Chris! My folder structure and project naming has evolved throughout the years, primarily driven by the client I have worked for. Having a universal system that we all could work from would save so much time and allow for an easier project sharing system. Kudos to you for tackling this!
please feel free to share what you do, i'm always curious to see what others are doing.
Your talk was amazing. Great work. Can we get the slides? Can you send me a zip of your new project template? And what were you using to do your slideshow? The iPhone as a projector remote?
the slides have a bunch of animation and I really don't want to share them BUT the info in them is revealed in this these two posts and I've created a link for the template project. yea the app i use for my phone to control my slide deck is http://itunes.apple.com/us/app/keynote-remote/id300719251?mt=8 works great until you get a phone call in the middle of a presso... so I actually use my 'retired' 1 Gen iPhone while my current 3GS is in silent in my pocket.
Great talk last night, regardless of the mic!
Can't wait for your archive and back-up session!
Loved your presentation at SF Cutters last week, Chris. I find good organization to be such a time-saver, and I'm always glad to hear about new ideas for making it even better. Looking forward to your next talk.
Your system is very close to my own, I use different names that harken back to the old linear days, like "roll ins" for pre-produced pieces that come into the edit, including animations and outboarded motion graphics; and "EDL" for the FCP project file backups. I'm superstitious about not keeping the FCP project files I'm editiing from on the media disks, but that is exactly where I put relevant milestone copies of the project for backup (in EDL). I also add a folder called Archive for archiving a project with handles, and add a "Window Dubs" subfolder under DVD. I call XPORTS "output" but it's the same sort of structure overall.
Wow, thanks for posting this, Chris! This will be extremely helpful.
So I just made the jump to Mac last year and was finally able to purchase FCP a little bit ago. Since I'm still new to FCP (and Mac for the most part) I can't figure out how to make your template for both this and the "bins" as the default. Could you walk me through it? It might sound like a novice request, but, well, that's b/c I'm a novice.... :)
Hi Chris, I've enjoyed both your sessions at the SF cutters meeting, March and May. I'm mostly a hobbyist at this point, and probably will continue to be, but I'm retired now and have time to devote to creating projects out of the nearly 200 DV tapes I've shot over the past 10 years! I think organization might be useful!!!
Anyway, I'm recreating the folder structure that you suggested, and I'm wondering if there's any significance to the use of UPPER, lower and mixed cases in the naming scheme. Every twitching fiber or my being wants to make them all Mixed case, or all UPPER, or all lower. Thought I'd ask!
Thanks for your fabulous presentations,
Bond
Chris, I enjoyed your talk. I have some concerns over performance, interested to know what you feel about it?
Primary issue is that --> with scratch disk and source media on same drive, if a person is doing many tracks of HD footage that could bog them down, no?
While you said your system was a RAID, not everyone uses RAIDS in smaller setups.
Opinions?
I do the same thing with my Scratch Disk. I've had a lot of people try to explain to me why I should use it otherwise, but I've had no problems with this method. I like the flexibility of archiving the entire folder and not worrying about missing assets.
Chris,
I've been editing video since the late 70's but always on somebody else's gear. Recently I invested in a pretty decent FCP system for myself. Thanks for taking the time to explain your organizational methods. I was trying various schemes myself but when I saw this post, I thought your method was brilliant but at the same time so common sense.
Several FCP pundits push keeping your scratch folder separate from the project folder. In your method I assume that every time you change over to a new or different project that you manually change your scratch folder in FCP system settings? Or have you found an automated solution?
Thanks for all the great info. I purchased Adobe's Production Bundle at the same time as FCP so I am trying to allocate time to getting comfortable with it as well. I needed After Effects and Photoshop anyways, so springing for the bundle made sense.
Lee
Hi Lee
I see you talked about keeping the scratch disk in a seperate folder. I think that's not a good idea. There is a valid reason to keep the scratch disk in the same project folder.
Freelancer like me will always have to move around my files to different computers to the client end. In that case rendering is a pain. Having everything in one project folder is very portable and i don't have to worry about re rendering or missing any files. It stays for years. Even if i reinstall my OS or whatever happens, i will have everything in one place. And it's very hard to overlook the scratch disk logs which will slow down the computer eventually if it is kept in a seperate folder altogether.
This is a great template and great info. I have just shared this on my twitter http://bit.ly/chrisfenwicks
Hariharan
www.ihariharan.com
virtual tour photographer: www.ihariharan.com/virtual_tour.php