Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro MOVE event copies media?

  • MOVE event copies media?

    Posted by Bret Williams on November 22, 2011 at 6:12 pm

    So, I’m digging into the trial version thought I’d post my first real question.

    I created an event on my main hard drive. The even is a collection of my master files on an external raid, so it’s a good size collection of ProRes 422 and DVCProHD files, so I left the media in place.

    But now I’ve decided I’m going to put all my events and projects on a different drive. Moving the projects is easy. Highlight the project and it asks if you want to copy referenced media. Nope. It simply moves the project and it’s render files to another drive and completely deletes the old one. Great. So, in doing the same with the event, it moves the project and deletes the old one, right? Wrong. Open the background tasks window and it’s going going going… So I look at the event on the drive and slowly but surely all the reference files are being copied over as actual files! Yeah, I don’t need it to eat up an extra half a terabyte. There is no preference that I can find to have it not do this on a move event command. Surely I’m missing something. I just want the event to exist on the external drive with all it’s nice reference files still referencing. Maybe (probably) I can just do this at the finder level, but I’m trying real hard to work within the paradigm. I’m still 10.0.1 since it’s a trial version Maybe .0.2 fixed this or gave an option checkbox or something?

    Jeremy Garchow replied 14 years, 4 months ago 4 Members · 6 Replies
  • 6 Replies
  • Jeremy Garchow

    November 22, 2011 at 8:47 pm

    I think the easiest way to do this is to use the Finder.

    QUit FCP and simply drag the whole folder that is named after the event to the new drive. The new Drive should have a “Final Cut Events” folder on the root level.

  • Bret Williams

    November 23, 2011 at 6:03 am

    I think I’ll try that next. But copying aliases? I wonder if that breaks their relationship. I guess not.

    You know how FCP X won’t even let to cancel or quit a background task like moving an event? Definitely to avoid problems like mine. I couldn’t quit or cancel. But if I let it continue the old event would be deleted, and I’d be looking at a whole new event with duplicates of maybe half a terabyte of media. I had to force quit. About 10 clips had been copied so I had to manually recreate the aliases in the finder and put them there. One of the files was mid copy and trying to launch FCPX with that file like that would result in an crash. Odd that it would delete the original event before the copying of all the media was completed.

  • Andy Neil

    November 23, 2011 at 6:52 am

    You can usually quit a background task by clicking the background task monitor (the round icon in the middle beside the timecode display). That will open a HUD with all the current background processes which you can pause or cancel outright.

    Andy

    https://www.timesavertutorials.com

  • Jeremy Garchow

    November 23, 2011 at 4:52 pm

    [Bret Williams] “I think I’ll try that next. But copying aliases? I wonder if that breaks their relationship. I guess not.”

    It doesn’t. You simply Quit FCPX, move the Encompassing folder from the “Final Cut Events Folder” to the “FInal Cut Events Folder” on the destination drive and reopen FCPX.

    [Bret Williams] ” Odd that it would delete the original event before the copying of all the media was completed.”

    It moves the Event first, this means you can keep working while everything transfers in the background.

    When you look at it that way, it’s kinda slick.

    There’s some weird and different things going on with media in FCPX. I see what they are trying to do, but sometimes it’s a little funky. It’s just something else to learn is all. It does point to bigger things in the future if you ask me, but that’s not a very popular sentiment around here.

    Jeremy

  • Lynette Chiang

    December 31, 2011 at 6:27 pm

    I *think* I found a bug in the wording of the FCPX help for this action. I wanted to move some clips from one event to the other. I noticed that it COPIED the original files to the new event (with all the time suck that involves), when I just wanted to retain the reference like it did in the first event. To do this you have to do COMMAND-drag.

    The Help says …

    “If both Events are on the same hard disk: Drag the clips from one Event to the other.” –> Both my events were on the same external FW drive (as is the entire project) but it still copied the original file

    “If the Events are on separate hard disks: Command-drag the clips from one Event to the other.” —> seems like you have to do this always.

    Words + Video + Intent
    galfromdownunder.com

  • Jeremy Garchow

    December 31, 2011 at 8:09 pm

    Lynette, we’re you using the Finder? Those appear to be Finder instructions.

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