Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy FCP renders on 12-core MAC

  • FCP renders on 12-core MAC

    Posted by Dolps Fernando on November 8, 2010 at 2:55 am

    Hi guys, I jst got my 12core mac and as I do some test, I notice that I wasn’t able to utillize/maxed up my processing power as I render my sequences. I notice that the CPU is just running barely at 5 percent. I just want to know if there is an option like multiprocessing like what after effects had developed. Thanks guys!

    Wayne Dupuis replied 15 years, 5 months ago 11 Members · 19 Replies
  • 19 Replies
  • Jeremy Garchow

    November 8, 2010 at 3:11 am

    Not in FCP, nope.

  • Michael Gissing

    November 8, 2010 at 3:48 am

    At the moment FCP is only awesome enough to use 2 cores, but buckle up your other 10 for the next release. (sorry for the cynical ‘Jobs speak’)

    At least Compressor (with qmaster) can utilise more cores.

  • Don Walker

    November 8, 2010 at 4:21 am

    Is there an Editing application out there that actually uses all available cores? Just curious.
    don walker
    Texarkana, Texas

    John 3:16

  • Michael Gissing

    November 8, 2010 at 5:52 am

    The new CS5 possibly?

  • Dennis Radeke

    November 8, 2010 at 10:02 am

    Premiere Pro CS5 is 64-bit native and will use all 12 of your cores and all of your available memory. It even has FCP 7 shortcuts if you’re comfortable with those. It will also send to Adobe Media Encoder (also 64-bit) and render in the background, so you can edit and render at the same time.

  • Federico Urdaneta

    November 8, 2010 at 10:51 am

    sorry to hijack this thread a bit, but i just keep hearing good things about the new premiere. whats the downside? if it’s so dreamy, why aren’t we all flocking to adobe right now? is it just to keep standards / compatibility?

  • Dennis Radeke

    November 8, 2010 at 12:48 pm

    Simply put, if you know FCP, it takes time and ‘relearning’ to change your established workflows to a new editing platform. I think a lot of people would rather edit than invest some time in determining whether their work could be better served by another vendor like Adobe.

    However, some people are changing. One longtime editor Chris Fenwick is chronicling his journey to Premiere Pro. You can check it out at https://www.chrisfenwick.com/

    In the end, you have to make the determination yourself through research whether Adobe, Apple, Avid, etc is right for you. I think for most people, a combination of tools is the most reasonable approach.

    Some pros for Premiere Pro:

    64-bit native application (so is AE and Adobe Media Encoder)
    Uses all of your cores
    Uses all of your memory
    Opportunity for GPU hardware acceleration
    Native editing (never transcode or rewrap unless YOU want to)
    Best DSLR workflow (best file based workflow period)
    Native RED workflow
    Integration with the rest of the Adobe suite

    Disclaimer – I am an Adobe person…hopefully most people already know that by now… 😉

    Dennis

  • Mark Petereit

    November 8, 2010 at 1:22 pm

    Because most of us have invested all of our time into learning Final Cut Pro, adapting our workflows accordingly, and we’re getting stuff done and delivered. We’re not going to stop and play “my dad can beat up your dad.” There are still people editing with FCP on Mac G4’s and making money.

    When it becomes impossible to make money editing in FCP, we will have already switched to something else.

  • Federico Urdaneta

    November 8, 2010 at 1:35 pm

    i hear you guys.

    i’ll wait for the revolutionary new FCP that the company famous for making phones will dish out sometime soon

  • Mark Petereit

    November 8, 2010 at 1:43 pm

    But if it doesn’t let me edit and color-grade 4K feature-length films on my iPhone 3GS, then it will just suck.

Page 1 of 2

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