Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Creative Community Conversations Premiere CS6 perfomance lacks behind on MBP

  • Premiere CS6 perfomance lacks behind on MBP

    Posted by Morten on April 18, 2013 at 9:51 pm

    I really hope Adobe has optimized CS7 for mobile computing. I’m on my MBP i7 with 8Gb Ram, MacOS 10.7.5 – and put together identical edits with H264 material from Panasonic AF101 on both FCPX 10.08 and Premiere CS6.04. Premiere stutters and looses frames, even at half res, and with no effects. FCPX just plays through it all, and I can apply numerous effects without loosing performance.

    – No Parking Production –

    2 x Finalcut Studio3, 2 x Prod. bundle CS6, 2 x MacPro, 2 x ioHD, Ethernet File Server w. X-Raid…. and FCPX on trial

    Dennis Radeke replied 13 years ago 16 Members · 31 Replies
  • 31 Replies
  • Derek Andonian

    April 18, 2013 at 10:24 pm

    Well, of course I can’t say for sure, but I can’t Imagine Adobe would let an entire upgrade cycle go by WITHOUT improving on the Mercury Engine… 🙂

    ______________________________________________
    “Up until here, we still have enough track to stop the locomotive before it plunges into the ravine… But after this windmill it’s the future or bust.”

  • Andy Field

    April 18, 2013 at 11:23 pm

    can’t say i’ve had that experience – works fine on a 2 year old MacBook Pro – and it ROCKS on my MBP Retina…..but then everything rocks on that machine – even FCP7

    Andy Field
    FieldVision Productions
    N. Bethesda, Maryland 20852

  • Joseph W. bourke

    April 18, 2013 at 11:43 pm

    You’re also aware that FCP dumbs down the preview rez?

    Joe Bourke
    Owner/Creative Director
    Bourke Media
    http://www.bourkemedia.com

  • Bill Davis

    April 19, 2013 at 12:10 am

    [Joseph W. Bourke] “You’re also aware that FCP dumbs down the preview rez?”

    Not sure if you’re talking about X, but if so, then I think that’s a pretty big oversimplification.

    X uses what I’ve come to think of as a “tier’d” preview strategy.

    On import, it creates and uses quick thumbnails in order to get you working fast. Then as the engine crunches them into higher rez versions it substitutes those dynamically throughout the interface. So you can be working with low rez thumbnails one second, then suddently, you’re working with higher rez proxys or even your full size files.

    The metadata construction means everything is just a pointer to a fundamental asset, so switching pointers is simple and seamless for the software to accomplish behind the scenes.

    So yeah, it “dumbs down the preview rez” for as long as your computer needs that to let you be productive, fast – but the software is also smart enough to know when it has a better source available and can link to that for higher quality screen representations automatically.

    FWIW.

    Know someone who teaches video editing in elementary school, high school or college? Tell them to check out http://www.StartEditingNow.com – video editing curriculum complete with licensed practice content.

  • Bret Williams

    April 19, 2013 at 1:29 am

    We’re talking about native playback of h264 aren’t we? Not thumbnails. X only plays back a lesser version if it is set to better performance.

  • David Cherniack

    April 19, 2013 at 2:58 am

    Just out of curiosity are you running Premiere with GPU acceleration set to ‘on’ – I would guess it’s OpenCL as it’s a MacBook with an ATI card, correct?

    David
    https://AllinOneFilms.com

  • Paul Jay

    April 19, 2013 at 7:08 am

    Add your 1gb or more videocard to the supported gpu list for mercury playback.
    This also will be a feature in next version.

  • Morten

    April 19, 2013 at 7:56 am

    Enabling GPU in Premiere does not make any difference (CS6.02). I have the beefed up MBP with maximum 512 Mb VideoRam.

    Sorry to say, I am not impressed with Premiere Pro. If the application cannot playback a simple stream of H264 on a powerful machine, I would suggest it is not optimized properly for Mac.

    – No Parking Production –

    2 x Finalcut Studio3, 2 x Prod. bundle CS6, 2 x MacPro, 2 x ioHD, Ethernet File Server w. X-Raid…. and FCPX on trial

  • David Lawrence

    April 19, 2013 at 8:42 am

    [Morten Ranmar] “Sorry to say, I am not impressed with Premiere Pro. If the application cannot playback a simple stream of H264 on a powerful machine, I would suggest it is not optimized properly for Mac.”

    Hmmm, something must be off with your set-up. I’m able to play 4K RED at 1/16 resolution on a late 2008 Macbook Pro without breaking a sweat. H264 cuts like butter.

    One thought –

    Are your h264 files wrapped as QuickTime .mov files? If so, try importing the raw h264 streams.

    I recently ran into difficulty with some AVCHD footage from a Panasonic HMC40. Mountain Lion wants to wrap them in QuickTime during import. These AVCHD QuickTime .mov files were unplayable in Premiere. They’d drop frames, and freeze.

    So I tried importing the raw AVCHD streams directly from a clone of the card. Premiere had no trouble with the raw streams at all. They play perfectly smooth.

    If your files are wrapped in QuickTime, that could be what’s messing you up.

    _______________________
    David Lawrence
    art~media~design~research
    propaganda.com
    publicmattersgroup.com
    facebook.com/dlawrence
    twitter.com/dhl

  • David Cherniack

    April 19, 2013 at 1:25 pm

    [Morten Ranmar] “Enabling GPU in Premiere does not make any difference (CS6.02). I have the beefed up MBP with maximum 512 Mb VideoRam.

    Sorry to say, I am not impressed with Premiere Pro. If the application cannot playback a simple stream of H264 on a powerful machine, I would suggest it is not optimized properly for Mac.”

    Well, sorry to say your “powerful machine” does not have the required amount of video ram to run with GPU acceleration. The specs for PrPro are 1GB – you have 512MB. You may want to always first check the operator before placing blame elsewhere.

    David
    https://AllinOneFilms.com

Page 1 of 4

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