-
Why can’t scratch files follow project
As Apple has FCP set up, everytime you change projects or begin a new one, the scratch file stays wherever it was set for the last project. If you forget to go to system settings and change the location of the scratch file for the new project, your new project files go into whatever was used last time. We used to use Media 100 where the scratch files stayed with the project. So no matter what project you opened your the new files you generated went into the same files for that project. Is there anyway to get Final Cut to do the same thing? I’m pretty tired of chasing files all over my computer. Yeah, I know…I should set my scratch disks everytime I open up another project. But I’m a shooter not a computer geek. That is what a computer is for!
-
12 Replies
-
Some one just posted a very similar comment just recently. I think there was a script that was suggested that you could use to do what you want (or maybe just something similar.)
-Russ
Russell Lasson
Kaleidoscope Pictures
Provo, UT -
Clyde,
Trust me, you’re not the first to complain about this one by a long shot…
The soloution is Preference Manager from Digital Rebellion at https://www.digitalrebellion.com/pref_man.htm , which by the way is available at the very excellent price of exactly $0.00 retail.
David
David Roth Weiss
Director/Editor
David Weiss Productions, Inc.
Los AngelesPOST-PRODUCTION WITHOUT THE USUAL INSANITY ™
A forum host of Creative COW’s Apple Final Cut Pro, Business & Marketing, and Indie Film & Documentary forums.
-
I didn’t think so. This is such a simple concept. C’mon Apple make this happen!
Thanks for your help. I’ll try it immediately -
Yep…. as someone who knows a bit about software…. its not usually the maintenance and utility fixes that get teh attention these days….
Wouldn;t we all love to see a release,,, the 100 little things you’ve been asking for since v1 addressed…
sigh
Richard M. Harrington, PMP
Author: Photoshop for Video, Understanding Adobe Photoshop, and ATS:iWork
-
The one I want is the option to copy files to a local location when importing (to the Scratch files directory perhaps!) so that when I import from a network drive or external hard drive or something I don’t have to worry about things going away if that drive isn’t connected.
-
Unless you’re using different physical drives for each project, let FCP do the work for you.
For example, many people set up a folder on a drive for their project media called project A for example, and maybe another folder on that drive called Project B. Bad idea. Apple automatically creates project folders for you, so when you forget to change the scratch disk (notice it’s not called scratch folder) directory FCP starts creating a Project B folder within your Project A folder or vice versa.
The simplest thing to do if you use a raid or internal drives is to simply set the scratch disk to the raid and don’t mess with it. FCP will magically create a folder for each project and keep everything organized and neat and tidy. You’ll never have projects within projects again.
Even if you do swap out hard disks, it’s still best to just choose the disk and not a folder. That way, if you’re ever backing up you still won’t have projects within projects. They may accidentally get spread across drives but they’ll be organized on each drive.
Or, maybe Apple will get it’s lazy butt and fix this 2.0 issue. In version 1 FCP didn’t create any project folders for you. You had to make your own folders to keep things tidy. THEN, they changed it to the current method and all the folks that were creating their own folders started creating a mess. Myself included.
-
Bret,
I agree with you that directing FCP to the root directory and letting it do its thing is much better than creating another directory, etc…
However, if you haven’t tried Preference Manager yet, and I know its $0.00 pricetag is a little high for you, you really should. It lets you save prefs with all kinds of control over which ones get saved, and you can name them by project or by the codec or whatever. In fact, I’m so sure you’ll like it, I’ll pick it for you on my tab…
David
David Roth Weiss
Director/Editor
David Weiss Productions, Inc.
Los AngelesPOST-PRODUCTION WITHOUT THE USUAL INSANITY ™
A forum host of Creative COW’s Apple Final Cut Pro, Business & Marketing, and Indie Film & Documentary forums.
-
True. But I just have 2 media drives inside the MacPro and just keep them selected. Never even worry about scratch disks. Last time I had some fancy plugin in FCP it cost me a lot of time. It was those damn FX Factory things. If you upgraded to FCP 6, your system quietly lost the ability to import P2 footage. Didn’t even give you an error, just didn’t work. Who would’ve thought after the half a day I did figuring that one out that the culprit was a plugin? Could’ve bought lots of plugins for the time I lost.
-
[Bret Williams] “Last time I had some fancy plugin in FCP it cost me a lot of time. It was those damn FX Factory things.”
I agree with you again… FX Factory is not my fave, and its taking time to load at startup too and I don’t even use it. Its bugs me everytime I start FCP. Wonder if it can be uninstalled safely?
Preference Manager isn’t a plugin however… In my case, I have client drives with various projects as well as various hot swappable raid configurations, so its nice to have th ability to load different prefs that do go with each job.
David Roth Weiss
Director/Editor
David Weiss Productions, Inc.
Los AngelesPOST-PRODUCTION WITHOUT THE USUAL INSANITY ™
A forum host of Creative COW’s Apple Final Cut Pro, Business & Marketing, and Indie Film & Documentary forums.
-
What I have done since day one with this irritation, is
create a “temp” folder on my disk array.FCP is ALWAYS set for that temp folder, unless I’m capturing video, then its mapped to the client folder. When capturing is done, back to temp.
Thats what works best for my setup.
Reply to this Discussion! Login or Sign Up