{"id":6423,"date":"2012-04-10T15:39:25","date_gmt":"2012-04-10T20:39:25","guid":{"rendered":"http:\/\/mediastorm.com\/blog\/?p=6423"},"modified":"2012-05-16T14:24:19","modified_gmt":"2012-05-16T19:24:19","slug":"mediastorm-guide-to-archiving-a-final-cut-7-project","status":"publish","type":"post","link":"https:\/\/www.mediastorm.com\/blog\/2012\/04\/10\/mediastorm-guide-to-archiving-a-final-cut-7-project\/","title":{"rendered":"MediaStorm Guide to Archiving a Final Cut 7 Project"},"content":{"rendered":"

Note:<\/strong> This workflow follows the guidelines for setting up Final Cut Pro 7 found in Tips from the MediaStorm Final Cut Pro Workflow<\/a> (see: Preliminary Setup, page 2 and Additional System Settings, page 11)<\/p>\n

After your project is complete and your output has been encoded, the next step is to archive your project.<\/p>\n

MediaStorm uses Mac Pro computers with four internal drives: one for the system software, one for project media, and one backup of each. When a project is complete, we remove the media drives and prepare them for archiving.<\/p>\n

Copying Your Files<\/strong>
\nCopy your entire project folder to an external drive. (If you are already using an external drive that you intend to archive you can skip this step.)<\/p>\n

Make sure to include all of your media. The reason MediaStorm copies all files is, in part, because Final Cut Pro\u2019s Media Manager<\/strong> is\u00a0simply undependable.<\/p>\n

The other reason is safety. You never know when you might suddenly need to alter a project. With the proliferation of inexpensive drives, it\u2019s good practice to keep all of your source material.<\/p>\n

In addition to the project folder–which should include all graphics, audio, and video associated with the project–copy<\/strong> any fonts<\/strong> you used to the Graphics folder<\/strong> of your archive drive. This way, your fonts will be available for installation on other computers.<\/p>\n

Fonts are generally installed in your user name<\/em>\/Library\/Fonts<\/strong> folder.<\/p>\n

Testing the Archive Drive<\/strong>
\nBefore deleting your project from the original drive, you\u2019ll first need to test your archive,\u00a0and then make a backup.<\/p>\n

Connect your archive backup to a different computer. This way you can ensure that your project is referencing only assets on the drive.<\/p>\n

Install any necessary fonts from your graphics folder and open your project file.<\/p>\n

Final Cut will notify you if any files are offline. Frequently, you\u2019ll receive a warning that files are missing.<\/p>\n

\"\"<\/a><\/p>\n

This is because FCP is still referring to the original folder structure.<\/p>\n

Select Reconnect\u2026<\/strong> and in the following menu, choose Locate\u2026<\/strong> to find your missing files.<\/p>\n

\"\"<\/a><\/p>\n

If you\u2019ve followed Tips from the MediaStorm Final Cut Pro Workflow<\/a> your render files will be stored in a folder named z_render<\/strong> at the root of your media drive. These files are not copied to the archive drive.\u00a0Therefore, you may need to render (option-R)<\/strong> before you can play your archived project. (See page 11, Additional Systems Settings from Tips from the MediaStorm Final Cut Pro Workflow<\/a> for more information on setting up your render folder.)<\/p>\n

Finally, after your fonts are installed, your media is reconnected, and you\u2019ve rendered, view your final project in its entirety.<\/p>\n

Once you\u2019ve confirmed that your archived version is accurate, copy it to a second backup drive<\/strong>. It\u2019s imperative to have at least one backup of every drive. It\u2019s an old saying, but should be repeated: there are two kinds of computer users, those who\u2019ve experienced a hard drive crash and those who will.<\/p>\n

For more information on duplicating drives, see MediaStorm\u2019s Guide to Backing Up<\/a>.<\/p>\n

Deleting Your Project<\/strong>
\nWhen your two external backups are complete, it\u2019s safe to delete<\/strong> your project folder<\/strong> from the original drive(s). Simply drag your project folder to the trash or select it and press command-delete key<\/strong>.<\/p>\n

Next, delete the project\u2019s render files in the z_render<\/strong> folder from your original drives. Use Tools>Render Manger<\/strong>.<\/p>\n

Place a check mark in the Remove<\/strong> category adjacent to the files associated with your deleted project.<\/p>\n

\"\"<\/a><\/p>\n

If your archive contains numerous drives, make sure to clearly label each. MediaStorm also uses a Google Doc<\/a> spreadsheet to keep track of projects, file sizes, and drive locations.<\/p>\n

Learn more about our approach to producing multimedia by purchasing MediaStorm’s Post-production Workflow<\/a>. Spanning more than 200 steps, the workflow covers every phase of editing, from organizing and editing assets in Final Cut Pro 7<\/strong> through backing up and archiving your project. The workflow includes exclusive access to our Aperture Workflow<\/strong> and our Final Cut Asset Parser<\/strong>. Learn more about MediaStorm’s Post-production Workflow<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

Note: This workflow follows the guidelines for setting up Final Cut Pro 7 found in Tips from the MediaStorm Final Cut Pro Workflow (see: Preliminary Setup, page 2 and Additional System Settings, page 11) After your project is complete and your output has been encoded, the next step is to archive your project. MediaStorm uses […]<\/p>\n","protected":false},"author":9,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[748],"tags":[],"class_list":["post-6423","post","type-post","status-publish","format-standard","hentry","category-tutorials","entry"],"_links":{"self":[{"href":"https:\/\/www.mediastorm.com\/blog\/wp-json\/wp\/v2\/posts\/6423","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.mediastorm.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.mediastorm.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.mediastorm.com\/blog\/wp-json\/wp\/v2\/users\/9"}],"replies":[{"embeddable":true,"href":"https:\/\/www.mediastorm.com\/blog\/wp-json\/wp\/v2\/comments?post=6423"}],"version-history":[{"count":0,"href":"https:\/\/www.mediastorm.com\/blog\/wp-json\/wp\/v2\/posts\/6423\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.mediastorm.com\/blog\/wp-json\/wp\/v2\/media?parent=6423"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.mediastorm.com\/blog\/wp-json\/wp\/v2\/categories?post=6423"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.mediastorm.com\/blog\/wp-json\/wp\/v2\/tags?post=6423"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}