Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Using “7 to X” App migration question

  • Using “7 to X” App migration question

    Posted by Michael Kienitz on February 6, 2012 at 4:57 pm

    I’ve been using the “7 to X” App with great success with regard to migrating all my old FCP 7 projects to FCP X 10.0.3 except that it places my new Events “FCP 7 Sequences and Master Clips” on the boot drive instead of the drive I would normally be storing them on. What is the simplest way to migrate the files to
    the intended drive I would like them stored on. I was not able to find any options when using the “7 to X”
    App so I guess I need to migrate after they arrive on the boot drive.

    http://www.michaelkienitz.com
    5108 Tomahawk Trail
    Madison, WI

    Jeremy Garchow replied 14 years, 2 months ago 5 Members · 15 Replies
  • 15 Replies
  • Michael Garber

    February 6, 2012 at 5:26 pm

    I could be wrong on this one but I think all you have to do is have the drive you want the project to go into highlighted in FCPX just before you run 7toX.

  • Michael Kienitz

    February 6, 2012 at 5:55 pm

    Thanks for the suggestion it did not seem to work.

    http://www.michaelkienitz.com
    5108 Tomahawk Trail
    Madison, WI

  • Michael Kienitz

    February 6, 2012 at 6:04 pm

    Thanks for the suggestion that works. If I highlight the designated drive and then close
    FCP X it imports to the drive highlighted.

    http://www.michaelkienitz.com
    5108 Tomahawk Trail
    Madison, WI

  • Michael Garber

    February 6, 2012 at 6:29 pm

    Glad it worked! I had gotten it to work on my system, but couldn’t quite remember what I did. So I must have quit the program, as well.

  • Jeremy Garchow

    February 6, 2012 at 8:00 pm

    Also, instead of using the “Send to FCPX” option from Xto7, you can choose to save the XML.

    Then in FCPX import the FCPXML where you can specify which disk from a drop down:

    7tox.png

    Jeremy

  • Thomas Frank

    February 6, 2012 at 8:20 pm

    You could just drag or move the Event to the other drive within FCPX, no?

  • Jeremy Garchow

    February 6, 2012 at 8:35 pm

    [Thomas Frank] “You could just drag or move the Event to the other drive within FCPX, no?”

    Absolutely, but that would be a double copy.

    7toX will bring in the media to the Event, so if you have 500GBs of media, if will transfer in 500GBs to the selected drive. If you want to move it, then you have to move 500GBs again, so that would mean you just moved 1TB to move 500GBs.

    It’s possible, but you might not necessarily want to do it that way.

    Hope that makes sense,

    Jeremy

  • Thomas Frank

    February 6, 2012 at 8:38 pm

    Why a double copy if you are moving from a to b, but you could also do it Finder level.

  • Jeremy Garchow

    February 6, 2012 at 8:59 pm

    [Thomas Frank] “Why a double copy if you are moving from a to b, but you could also do it Finder level.”

    But if you brought it in to the wrong drive in the first place, you still have to move it.

    Even if the media is on the same drive, FCPX still copies the media in to the Event.

    So, if media is on Drive A (external), then you run 7toX and don’t set a drive, it will bring it in to your internal drive (Drive B). But to get that back to the external, you will still have to copy everything to Drive A. So you just went from A to B (500GBs) to A (another 500GBs for a total of 1TB).

    If you set a drive before you import the XML (or use the send to FCPX command) then you go from A to A (500GBs).

    Once you use 7toX, you’ll see what I mean.

    Jeremy

  • Thomas Frank

    February 6, 2012 at 9:05 pm

    I understand but why not move or copy and then delete the Event?
    If it can be done in 7toX in the first place then go for it but if you can’t copy – move – delete or just command move in Finder.
    😉

Page 1 of 2

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