Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Motion 8 sec clip…12 minute render?!?!?

  • Devin Crane

    June 12, 2007 at 8:03 pm

    I’m having the same problem on a Quad 3ghz Mactel and a ATI 1900xt card. The motion files consist of a shape with a mask for the background and some text with text behaviors added to them.

  • Chris Borjis

    June 12, 2007 at 8:43 pm

    [Herb Sevush] “For the record I have a Dual 2.5 G5 with 5 gigs and a Radeon X800 XT – which means I’m NOT underpowered in any way. And yet …”

    my point exactly.

    This has absolutely nothing to do with openGL performance, its all about cpu cycles and there is definitely something wrong here that apple needs to address ASAP.

    One thing I have not tried, apparently you can import motion files as some kind of modifiable template (text) I am going to try that and see if that helps at all.

  • Tom Daigon

    June 13, 2007 at 1:28 am

    Everyone who has experienced this major issue, please document the problem
    with Apple at https://www.apple.com/feedback/ in the Final Cut Pro category.
    This will insure they are aware of the issue and our concerns.

  • Chris Borjis

    June 13, 2007 at 11:52 pm

    I submitted.

    Also just an fyi, the templates inside final cut pro that reference motion files has the EXACT same problem as using motion files imported.

    12 minutes to render an 8 second slate.

  • Tom Daigon

    June 14, 2007 at 1:00 am

    Yes Boris.I confirm your observation with my own experience.

  • Oliver Peters

    June 14, 2007 at 12:51 pm

    [Borjis] “the templates inside final cut pro that reference motion files has the EXACT same problem as using motion files imported.”

    Not what I’m seeing.

    The tests I ran were only slightly longer than rendering Animation in Motion3 versus rendering a Motion3 template in FCP6. Of course, if you add rendering the movie file in Animation codec again on the FCP6 timeline, the combined total would be about the same.

    Do you possibly have two instances of FCP or Motion installed (old and FCS2)?

    Sincerely,
    Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

  • Tom Daigon

    June 14, 2007 at 3:07 pm

    Not in my case. I did a erase and install of the newest Tiger before doing a full install of FCS2.

  • Dan Powers

    June 21, 2007 at 11:25 pm

    It’s not just motion. FCP 6 is much slower. I have been rendering clips all week long on the previous version 5, just compression exports and they were running 11 minutes. Now after upgrading they are 1 hour! This sucks bigtime. I have deadlines!
    I followed all the rules. First upgrade OS to latest version 10.4.10 from 10.4.5 also upgraded QT to latest version then did the upgrade to FC Studio 2. This is really a dog. I am on a Quad G5 2.5 with 4 gigs ram. It is rendering like a single G3!

  • Macdabby

    June 27, 2007 at 7:30 pm

    I think this is just a bug in the software on PPC systems. I have a project with a 10 second long motion file – it is basic text, a small image, and a little it of motion. Its a motion 3 file and FCP2. I put it into a FCP sequence, and tried to render it. On my dual G5 2ghz/4gig ram it takes 10 minues – on my less equiped quad 3ghz xeon with 2gig, it takes 10 seconds – granted the PPC is a faster machine, its not 60x faster and should not account for that much of a speed difference. Hopefully apple will fix this soon – i’ll report it on their bug page.

  • Tom Daigon

    June 28, 2007 at 1:23 am

    Well, it does my heart good to hear that on your Intel machine the very same file is very fast.
    I guess my plans for an 8 Core when Leopard comes out are still in my future. The dog slowness on my G5 dual made me doubt the wiseness of using this software for professional use with my clients…Im still waiting.

Page 4 of 4

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