Run FCP X on 2009 MBP? sloooowwwww

Discussion in 'Digital Video' started by Magrathea, Jun 28, 2011.

  1. Magrathea macrumors regular

    Aug 21, 2008
    I'm wondering if anyone has figured out how to run FCP X on an older MBP without it bogging down with maxed out CPU usage and stuttering playback? I've got a 2009, 2.4Ghz MBP with 8 gigs of Ram and a 9600m Gt card / 256mb.

    Stuff I've tried:
    Turn off the auto render: helps a ton and I had 3 streams of 1080p 30 video playing on top of each other all with color correction on them
    Just edit the Pro Res proxy: not sure how I can tell if I'm using the proxy of full ProRes422 codec when I edit.

    The more I look at FCP X the more I see that it's got a huge amount of new stuff and the more I realize I have no idea how to use it. Putting the obvious omission aside (multi-cam, tape stuff) I think the problem folks are having is that it's so different and so new that the frustration comes from not know how the hell to use all the new features.
  2. Chaos123x macrumors 68000

    Jul 8, 2008
    Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_3_3 like Mac OS X; en-us) AppleWebKit/533.17.9 (KHTML, like Gecko) Version/5.0.2 Mobile/8J2 Safari/6533.18.5)

    Use prores files on a external FireWire 800 or esata drive.
  3. cgbier macrumors 6502a

    Jun 6, 2011
    Sounds like you're running native AVCHD. Even in Windows you'd need a very fast 4core system to handle 3 streams.
  4. Magrathea thread starter macrumors regular

    Aug 21, 2008

    1st: impossible to edit native Avchd, we've not got a mercury playback engine lads, FCP X has to transcode it into something.

    2nd I am transcoding to Prores, proxy and regular 422.

    I did try an external Esata drive connected via an expresscard adaptor and it did seem to help quite a bit but when I get he machine that I really need for this program: quad core i7 then I can kiss the esata good buy but then perhaps we'll have some more thunderbolt enclosures to choose from.
  5. CaptainChunk macrumors 68020


    Apr 16, 2008
    Phoenix, AZ
    And I think a lot of that can be attributed to the fact that FCP-X has very poor documentation. It's nowhere near as refined as the manuals for FCS.

    From what I understand, it's possible to cut AVCHD "natively" if you turn off ProRes transcoding in the Preferences, but it HAS to transcode on export.
  6. Magrathea thread starter macrumors regular

    Aug 21, 2008
    Native AVCHD

    Yes you can edit native AVCHD but all machines but the latest quad core i7s will grind to a halt when you do this, hell, they can barely handle ProRes now it seems. INstalled FCP x on a newer lappy, an i7 dual core with a 330m card and 512mb of memory and it seems just as laggy as my late 2008 MBP!
  7. cgbier macrumors 6502a

    Jun 6, 2011
    Do you bringing in your footage via a single F/W drive? That might be the bottleneck with 3 streams.
  8. Magrathea thread starter macrumors regular

    Aug 21, 2008
    Figured it out - AVCHD workflow

    I wonder why I'm the only person who is running into this??? Does eveyone have a brand new 8 core MacPro or a i7 guess so ....... :) Is anyone actually using this program .... :)

    Native is a no go , definitely not for anything but a 2011 MBP i7.
    Make sure you are using a Fw800 or esata external drive.
    Lots of memory helps I'm sure - I have 8 gigs on my old lappy
    Finally - Make sure you have:

    • Final cut pro> Preferences > Playback > check--> Use proxy media
    • Final cut pro> Preferences > Import > check --> Create optimized media (this creates Prores 422) & create proxy media (this creates Prores 422 proxy that is a mere 9mbps bandwidth)
    Strange, if I playback the proxy media FCP X creates in quicktime NOT in FCP x my computer uses a lot less CPU cycles than if I play it back in FCP X (media that has zero color correction etc applied to it in FCP X)
  9. THX1139 macrumors 68000


    Mar 4, 2006
    Because you are the only one using the program. Well, you and maybe 2 other people. :D
  10. Magrathea thread starter macrumors regular

    Aug 21, 2008
    Cheeky Bastard!

    No, me and the other poor pisser who've been running FCP X have finally figured it out!

    Hint> Don't use 1080p !!! and for the love of Dog use Proxy will ya. Will post an article on my blog.
  11. mBox macrumors 68020

    Jun 26, 2002
    Running it on a late 2008 Uni 15" and early 2009 Uni 17".
    My first project was GoProHD clips and that was easy as pie.
    About 60 clips in the event and most are maxed out in length.
    Final output was only 5 min but still run great on the above.
    Recent was 26 R3D clips exported from RCX using ProRes (HQ) and so far so good. I do have the video card on both systems running high and Im using a GTech mini 1TB with esata.
  12. Burger Thing macrumors 6502a

    Burger Thing

    Jan 7, 2009
    Around the World
    Make sure you are running your computer in 64 Bit mode. You can check that in the About this Mac - Software menu. If not, restart it and hold the 6 and the 4 button at the beginning.

    Not sure if it helps in your particular case but maybe it will speed up your workflow a big :)
  13. Nostromo macrumors 65816


    Dec 26, 2009
    Deep Space
    Coming up in autumn:

    about organizing media in FCP X, already available:
  14. cgbier macrumors 6502a

    Jun 6, 2011
    LOL, Peachpit Press has been the "official" supplier of Pro-Trainigs books for years. ;)
  15. Magrathea thread starter macrumors regular

    Aug 21, 2008
    Remember if you are a pro you'll be transcoding and it'll take 2x anyway cos it has to create ProRes 422 standard and the proxy.

    So my 2 hour shoot took 4+ hours just to transcode. If you add color correction to proxy it takes 5x on 1080p and but just 3.5x on an i7 machine. Using 720p took 1.5x and on an i7 should be less than real time.

    In my case I shot in 1080p, god know why so if I were clever I'd change the timeline to 720p, do all my corrections etc then change it back in the end. Look there are reason no pro is doing full on edits on a 2008 laptop 4 cores and an big graphics card are a minimum and let's hope Mr Lion brings us some performance enhancements?

    Guys if you just fannying about with home movies and filming your cat ignore my post but if you know what I'm talking about I hope this helps. No one edits native H.264 / Avchd not even in Premiere Pro 5.5 - you will ALWAYS transcode to do all the fancy color correction 7 layers of video etc.
  16. acearchie macrumors 68040


    Jan 15, 2006
    This is exactly why I think that it is stupid that people were complaining that Premiere had native h.264 editing and FCP7 didn't. I wonder how many people actually tried to use it.

    One thing you might have wanted to do to speed up your workflow is to only create Proxy files and then reconnect it to the original media after you have finished your edit.

    I had some stuttering when I was using FCP X on my laptop but on my Mac Pro it was fine but I put this down to the fact that I was using a separate drive as my scratch on the Mac Pro. What drive are you using as as some people have said that maybe a bottleneck if you have 3 1080p streams on the go!

Share This Page