Home | Workflow | Particular

Particular

Most experienced users will tell you that setting scratch disks appropriately is one of the keys to having a successful and productive relationship with Final Cut Pro. This importance is compounded if you introduce Xsan into the equation. If you’ve made the leap to working in a mult-user environment with shared network storage, you will want to take note of Apple’s recent KB document, “Final Cut Pro: Notes for setting Scratch Disk on Xsan”, which includes two general rules for how to properly configure things, as well as a quick tip for how to make adjustments should a mistake have been made. The main points to take away from the article are that you should never set a scratch disk on the root level of an Xsan volume and you shouldn’t share scratch disks between users.

1 Comments

matt said:

I have to say that is disappointing to see and read. When working on a large scale production, I can easily see multiple assistants needing to be dumping footage into the same place at the same time. And I’d rather sort my Scratch disk by production not by user. Obviously you can add to part of your workflow to have someone later dump the material to the centralized production folder, but its a step you shouldn’t have to do imo.

Anyway, at least Apple is putting this out there so users know to work around the deficiency. I just hope Apple will add that to its list of XSan development itmes. I do like the XSan, in theory, but its ‘clearly still in development’ reality is simply a frustration.

cheers.

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

© 2005-2009 Jonathan Eric Tyrrell, Creative Commons License.

VFCPUG Online is an independent web site and, unless explicitly stated, has not been authorized, sponsored, or otherwise approved by any of the companies mentioned herein, including Apple Inc.. All company and product names may be trademarks of their respective owners.