Here’s something we encounter all the time, a major client with an insane deadline sends us a precious file of their motion picture to be laid off to BetaSP or Digibeta for use in a critical film festival screening where the audience includes top studio scouts and distributors.
At the screening, the lights dim, the projector fires up, and the film hits the silver screen with all its glory and charm. The distribution execs are cracking up at every joke and displaying the perfect body posture for the dramatic parts. The screening is going to be a hit… until… OH MY GOD! THERE’S SCRATCH DIALOGUE COMING FROM THE CHARACTERS’ MOUTHS! AND, WHERE DID THE MUSIC GO IN THAT SCENE? AAAAAK! A TEMP TITLE CARD THAT SAYS “SCENE MISSING”!
Poooof. There goes the distribution deal. There goes my life!! Anyone need a bartender out there?
But how could this have happened? The file was proofed and re-proofed and watched by several people. The film was perfect back in the online bay. And the file that was transferred for the screening was called “LOST IN PARADISE NEW FINAL VERSION REVISED”.
And therein lies the problem: The file name. The wrong file was used to make the transfer.
This is a dramatic illustration of the consequences of naming files without the use of a clear emnaming convention.
I don’t understand why so many actual professionals name there files things like:
My_Film_New_Master.mov
My_Film_New_New_Master.mov
My_Film_New_New_Final_Master.mov
My_Film_New_New_Final_Master_for_Sundance.mov
My_Film_New_New_Final_Master_for_Sundance2.mov
My_Film_New_New_Final_Master_for_Sundance2_Revised.mov
My_Film_New_New_Final_Master_for_Sundance2_Revised2.mov
My_Film_New_New_Final_Master_for_Sundance2_Corrected.mov
My_Film_New_New_Final_Master_for_Sundance2_Corrected_Final.mov
Now when there are a bunch of discs floating around the office with various versions of these “FINAL” masters, it is really easy to see how things could go terribly wrong at the dub house when the incorrect file shows up for transfer.
For that matter, with everyone working from servers and hard drives all over the world, it’s super easy to see that a mis-named file in a folder could be mistaken for the correct one. In fact, people accidentally delete critical files all the time on their very own computer for this exact same reason.
So the trick is, ALWAYS NAME EVERY SINGLE FILE WITH A VALID NAME. Here are some excellent ideas to include in your name:
1) The date the file was made. THIS IS ABSOLUTELY CRITICAL! If there is no other info in the file name, you must use a DATE. With the real date in the file name, it is almost impossible to grab the wrong one since an actual date is so easily cross-referenced by invoices, production schedules, and other records of processes. Also, make the date read in reverse European-style syntax: YEAR/MONTH/DAY/TIME (military). That way, the date will always sort in perfect order and it will be crystal clear which file is the latest one.
Example: 2008_12_31_1325
2) The project name or abbreviation. “Lost in Paradise” becomes ”LIP”.
3) The status of the project, such as “RuffCut_No_Music” or “ColorCorrected_Master”
So your wonderful new, final, final, really truly master corrected revised file will end up looking like this:
2008_12_31_1325_LIP_FOR_SLAMDANCE.mov
Ain’t it a a beautiful thing? And if that file name is too long for a given purpose, you can still get by with:
2008_12_31_LIP.mov
God, that’s clean. MMMMMmmm. It’s delicious to behold and to archive. Oh, and by the way, you will be able to actually keep your job if you name files like this.
Kirk