Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Advice on organising large FCP7 project in FCPX using 7toX

  • Advice on organising large FCP7 project in FCPX using 7toX

    Posted by James Bayliss-smith on February 8, 2012 at 2:08 am

    Hi there, I was about to try out 7toX but I’ve just read there is a bug with PAL material so I’m awaiting the imminent update from the guys over at 7toX. Apparently it’s already been submitted to the App Store.

    In the mean time I thought I’d post on here to ask for any advice from people who have already migrated projects over. I will be bringing in a documentary project with over 100 hours of footage. I have created many sequences and I have almost 50 bins with all my subclips organized in. I’m worried that once I bring it in to FCPX all I will have is a mass of clips and a mass of keywords and loads of compound clips. Before I get a change to play around with it and re-organise my project has any one got any tips on organising my project in FCPX. Or even if I should re-organise in FCP7 before I migrate over?

    At the moment everything is very visually well organized with regard to where everything is placed in Bins. I see the superiority of FCPX’s keywords but I’m kind of dreading the mess it may cause to my careful organization.

    Any ideas?

    James

    Jeremy Garchow replied 14 years, 2 months ago 3 Members · 5 Replies
  • 5 Replies
  • Jeremy Garchow

    February 8, 2012 at 3:48 am

    The good thing is, it’s super easy and fast to clean things up in X. You can manipulate large swaths of clips very easily and quickly in X.

    Every bin becomes a keyword collection.

    A bin within a bin will have clips in two keyword collections.

    A bin, within a bin, within a bin….you get it.

    In list view, you can see how many keyword collections are on each clip. It will then be up to you to figure out which keyword collections to keep/rename/delete.

    Every sequence comes in as a compound and are placed in a collection called fcp7 sequences. Very convenient, but they are all in that one collection. You can make folders in Event to further organize your compounds (or kw collections). Even some effects come over.

    All media gets imported in to the Event, so make sure you have the drive space.

    There will be some work to do, but I, personally, happen to like what 7toX does. With X’s powerful data handling, it’s a pretty good experience considering how different the NLEs are.

    This is worth the read: https://assistedediting.intelligentassistance.com/7toX/about.html

    Have you played with X much yet? Meaning, do you know how the keywords work?

  • James Bayliss-smith

    February 8, 2012 at 3:59 am

    Hey thanks for you reply. Yes I’ve played around a bit and I’m ready to take the plunge in transferring this project over. I’m just getting into the edit so my sequences are pretty short right now. I’m planning on getting a long rough cut done then getting an editor onboard to help me make a fine cut. I’m worried I may be limiting my options by using X as some editors may have not learnt it yet but I really want to use X as I like the magnetic timeline and especially the browser. Thanks for your comments

  • Jeremy Garchow

    February 8, 2012 at 4:14 am

    Have fun, and let us know how the transfer goes, good or bad.

    I’d suggest using the “save XML option” instead of the send to fcpx option in 7toX. That way you have a record of what was done.

    Also, give yourself some time as the import can take a little bit depending on the amount of footage. Even after the transfer, give it a minute to build waveforms and thumbnails.

    As far as the fine cut, there’s always xto7 if you need it. 🙂

    Jeremy

  • Ben Scott

    February 8, 2012 at 7:40 pm

    large projects need large amount of RAM
    8gb is bare minimum, 16gb is recomended
    fast storage helps if you arent working proxy from my experience with 10 hours plus of footage

    also its probably a good idea once the footage is across to X to ask it to make proxies and work with that workflow

    dont think the issue was with PAL on that software, it got fixed in 2st few days according to the authors

    as the clips come across with log notes and comments and these can refined using smart collections I would say thats a good way to tame the project, if you havent been using log notes then I reckon that the bins to keywords will work OK

    I would also make sure if there has been a lot of prior editing on FCP7 then look into where the software isnt able to work e.g. motion projects, freeze frames, generators, variable speed changes, codecs/file workflows yet to be supported e.g. red R3ds
    On those sections of the timelines I would mark them and add notes and then get fcp7 to export a batch list which you can import into excel or openoffice and print out a list of where the errors are going to occur
    then I would decide if they need an export of those sections of the timeline to get a better translation

    also it always good to have a guide quicktime, in fact essential for a reconform like this. that there is no way to gang your guide quicktime to the project in FCPX is a major flaw, only way I can think to check is set project to correct timecode, cut guide in correct place and then do a scale on that guide to use as a pseudo guide

    I would say for the Motion 4 projects I would try and get them across as fcpx effects/generators if this makes sense as you can then keep refining them in FCPX and motion 5

    let us know how you get on, be interesting for lots of people to know I think

    from ben

  • Jeremy Garchow

    February 16, 2012 at 6:21 pm

    Just to follow up with this.

    I heard from the 7toX team and if you save an FCPXML of the project (instead of sending) and choose to import the XML, FCPX will honor the import settings in the X prefs.

    This means that if you don’t have “Copy media to Event” checked to any of the transcode options, your media should come in aliased to the original media which will save you some copy time.

    Jeremy

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