Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy New MacBook Pro and Final Cut 2 (sucks?)

  • New MacBook Pro and Final Cut 2 (sucks?)

    Posted by Justin Mcclusky on October 28, 2008 at 4:31 am

    I just picked up the new (late 2008) MacBook Pro entry level option (2.4ghz). It’s replaced my entry level 1st Gen MBP (1.8ghz).

    After installing FCP right after opening the box, popping open a timeline I’ve already finished on the old machne and setting it up to export through compressor (fast DVD encode), it’s taking FOREVER. I’m talkin 16 hours for a 25 minute show that is SD.

    On my other machine it is taking about 5 hours to complete. So I really have no idea why this new machine is being such a dog.

    Can anyone help me out here or is this just a pitfall of the new MBPs?

    I really could use any help available.

    (Thanks everyone. This place has helped me enormously in the past)

    Steve Martin replied 17 years, 5 months ago 13 Members · 27 Replies
  • 27 Replies
  • Rafael Amador

    October 28, 2008 at 6:41 am

    Run DiskWarrior, TechTools or similar.
    rafael

    http://www.nagavideo.com

  • Andrew Commiskey

    October 28, 2008 at 2:10 pm

    Fix your permissions and do a “Safe Boot” (these are standard answers, I hope it does not suck)
    Best,
    Drew

    Chaos is the beginning of everything.

  • Jeremy Garchow

    October 28, 2008 at 3:02 pm

    THere’s obviously something wrong there. How did you export the movie?

  • Rafael Amador

    October 28, 2008 at 3:22 pm

    Sure start by repairing permissions.
    I’ve suggested DW because after a clean installation from scratches (System, QT and FC suit) repairing permissions after each installing, DW shows a “30 % of items out of order” in the directories. Impossible to work like that. When Mac OX says “Optimizing System” I don’t really know what kind of optimization does.
    rafael

    http://www.nagavideo.com

  • Chris Poisson

    October 28, 2008 at 3:28 pm

    Exporting through Compressor is completely unnecessary, and ALWAYS slow. Export a self-contained QT movie.

    I have the exact same machine and it rocks. Suggest you try some of the other good advice.

    Have a wonderful day.

  • Justin Mcclusky

    October 28, 2008 at 3:45 pm

    The original deliverables were given as straight up digital media:
    mp4
    960×544
    aac stereo
    average bitrate of 1866kbp/s

    What i’ve done is cut it in that, now I’m exporting to DV/DVCPro. Each time I try again, it spits out 32 Hours!

    So frustrating. I’ll try using diskwarrior and the like to see if that helps, then report back here with results. Thanks for that advice.

    Any other ideas?

  • Matt Gerard

    October 28, 2008 at 4:07 pm

    Also, check in compressor and see what the “Motion Estimation” drop menu is set to. There is a huge difference between Better and Best in terms of encoding time. You might have had it set at Better on your old machine, and might be set at Best on the new one.

    I’ve been buggered by this before.

    Cheers!

    Matt

    Its more fun to ride a slow motorcycle fast than a fast motorcycle slow…

  • Paulo Jan

    October 28, 2008 at 4:45 pm

    Since this is a laptop, check just in case whether some power-saving/sleep feature is enabled. Also, this sounds silly, since AFAIK Final Cut doesn’t use the GPU for rendering, but perhaps you could check whether it’s using the integrated GeForce graphics chip or the discrete one (the good one, but also the one that sucks more power). These are just shots in the dark, BTW; I don’t know whether they will help, but just in case…

  • Chris Borjis

    October 28, 2008 at 5:39 pm

    I bet its the power management causing this. notebooks are usually
    always set by default to have the cpu cycle down most of the time to
    conserve power. Even the tower macs do this and disabling it is
    one of the first items of order on an editing system.

    I export from fcp to compressor quite often but only on tv spots
    and short projects. long form definitely gets a self contained
    export then as it takes 3x less to do usually.

    check your motion estimation as someone pointed out. that alone
    could be killing it time wise.

  • Peter Wiggins

    October 28, 2008 at 6:18 pm

    FCP does use the graphics card for rendering, anything that uses FxPlug

    Peter

Page 1 of 3

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