Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Properly Archiving a P2 project

  • Properly Archiving a P2 project

    Posted by Matt Golin on September 28, 2010 at 4:29 pm

    Done with a 1 hour project I edited on Final Cut Pro, and am going to archive it properly to a 1TB Raid 0 Firewire Drive.

    I am trying to be very anal about this.
    So far, I have transferred to the drive:

    •The FCP project file
    •All original P2 camera files
    •All associated media (music,pix,GFX)
    •Final uncompressed QT of movie

    My question:

    Is it necessary to also archive the CAPTURE SCRATCH folders?

    I’m hoping not, as that is a whole lot more space I’ll need available.

    Matt Golin replied 15 years, 11 months ago 3 Members · 3 Replies
  • 3 Replies
  • Jeremy Garchow

    September 28, 2010 at 4:53 pm

    [Matt Golin] “Is it necessary to also archive the CAPTURE SCRATCH folders?”

    You don’t have to. You can easily relog and transfer the project by selecting the clips and choosing batch capture. FCP will then ask you to load the P2 folders it needs, and it will begin the transfer. Keeping the MXF files is crucial, though.

    Jeremy

  • Alex Elkins

    September 28, 2010 at 6:32 pm

    Hi Matt,

    Are you certain you’re archiving to a RAID 0? For added protection I would recommend RAID 1 if it’s an option. It means the two (or more) drives making up the RAID ‘mirror’ each other, so if one fails you still have the other as a backup – RAID 0 doesn’t give you that protection.

    Just a thought.

    Alex

    Salad Daze Films – Freshly Tossed
    Check out my latest addition to the Creative Cow Reels Section

  • Matt Golin

    September 28, 2010 at 6:49 pm

    Jeremy / Alex:

    Thanks Guys.
    You answered my question.
    Good to know I dont need to archive the Capture Scratch folder.

    I meant Raid 1.

    Thanks again.

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy