-
Assigning Scratch Disks
DAMMIT!! I’m tired of looking to the heavens and angrily exclaiming this to the Apple gods… so I’ll release it to the Cow and be forevermore at peace!
Having been a Media 100 guy for the first 7 or so years of the nonlinear revolution I got very used to assigning my drive destinations when I first started the project, and then NEVER needing to worry about it (unless I WANTED to reassign them). Media 100 always linked whatever project I was on to the drive destinations I assigned at the beginning of the project. Even if I changed drives and booted up that drive’s project.
But having been with FCP for the last 3-4 years I just can’t get used to the fact that I have to keep on top of the scratch disks. Not so bad when you change drives, as FCP gives you the box saying it can’t find the correct scratch disks, do you want to reassign? But when working on several projects on one drive, any one of which (or all of which) can be called up on a given day, it can be maddening. Especially when you suddenly remember it an hour later and the last 10 GB of renders went to another project’s scratch disks! It’s not about proper habits. I, as well as most FCP editors, have developed obsessive workflow habits in regard to this. But sometimes you get slammed, and it would be nice if Apple made it so that this was one less thing editors had to think about.
Apple, you have the ability to do this so just do it!!
There…I feel much better. Nothing like an angry dissertation to set an editor straight! Namaste…Bugsy