Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Media Encoder Background Rendering – what a dissapointment

  • Media Encoder Background Rendering – what a dissapointment

    Posted by Simon Reichel on October 29, 2014 at 12:37 pm

    Hey all,

    so I now updated to the snazzy CC 14 release and here I am thinking, let’s rock and roll.

    So I’m sitting on a Macbook Retina 15 and I’ve cut a lousy 2 minute edit with RED 5K footy on a HD timeline and I’m sending that to the Encoder to render a H264 and even with OpenCL Mercury the encoder predicts a ridiculous 1 hour 30 minutes for rendering. joking?!

    nevermind I think, I’ll just work on the next edit, another 2 minute with RED footage for HD export. So I fire up the other project back in Premiere and i’m starting to cut and being very positively surprised at how nicely and smoothly Premiere is handling the RED footy even with the Encoder rendering in the background. That joy lasted for exactly 5 minutes which is when the dreaded spinning rainbow umbrella of death popped up and my two and a half grand laptop froze up like a little worthless piece of sh…enanigans. Needless to say I gave it a couple more tries, always the same. Within varying amounts of short time (anywhere from 1 to 5 minutes) the whole system froze and I was forced to kill the computer. So I’m thinking. If not even I, on an overpriced next-gen laptop, can properly use these features, then who the hell is this made for? Same thing for the neverending AE to PP dynamic link joke. Incredible sounding features that end up being inusable system-killing glitchfarms.

    This is bumming me out big time which is why I’ll have to apologize for the snotty tone of this post. I can’t be the only one shedding hot tears of rage over this though. Or am I missing some vital settings adjustment that would make the whole affair stable? And please let’s trust each other not to be absolute bumbling fools and start suggesting stuff like “have you turned other programs off?”…

    Barry O’brien replied 11 years, 6 months ago 8 Members · 19 Replies
  • 19 Replies
  • Tero Ahlfors

    October 29, 2014 at 2:12 pm

    [Simon Reichel] ” “have you turned other programs off?””

    Well let’s start with “could you give us the exact export settings?” and “have you tried turning the GPU acceleration off?”.

  • Dennis Radeke

    October 29, 2014 at 2:46 pm

    …and how much RAM and the system specs. Any 64-bit application’s performance is only good as the sum of the parts given to it.

    You did say RED 5K and laptop right?

  • Ericbowen

    October 29, 2014 at 3:15 pm

    I hate to break it to you but 5K R3D on a laptop especially one using Open CL instead of Cuda is going to be a poor experience regardless of whether Mac or PC. 5K R3D media can push even a 6 Core X99 workstation with 64GB of ram depending on what the project complexity is like when trying to render and work simultaneously. That workstation has 2 or 3 times the processing and ram performance capability of the MacBook Pro. The MacBook Pro is an underpowered Imac basically as far as performance comparison goes. Along with that Open CL has allot of evolving to do with Adobe and is far from ram efficient which is what your running into now after a few minutes of rendering. I would suggest moving the renders to a desktop or workstation if you can. If not then render and walk away. MacBook Pros or any other laptop out currently don’t have the spec capability to render and work 5K media at the same time.

    Eric-ADK
    Tech Manager
    support@adkvideoediting.com

  • Simon Reichel

    October 29, 2014 at 3:27 pm

    Hi Tero, Hi Dennis,

    I almost exclusively work on RED footage, it always worked quite smoothly on CS6 and I feel like it also exported quicker there.
    Regardless, even if my machine is underpowered, that’s no reason it should just violently crash. I would understand lagging and getting slow and stuff. but full-on freeze-ups, i’m not used to that on macs and it is quite upsetting I must say.

    It’s h264 vimeo 1080p HD preset for export and a roughly cinemascope 1920×810 avchd project. again, have worked this way for a while now, it never felt slow or faulty in terms of performance.

    Cheers,
    Simon

  • Dennis Radeke

    October 29, 2014 at 4:07 pm

    If you’re having big issues, then the first line of defense is to trash your preferences and/or clean your media cache. If for some reason you’re still having an issue, then either you have a corrupt project or corrupt media in the project OR you should try a reinstall of the system.

    To deal with the first, create a new project and import a sequence of the old project and render out. How does it do? If better, then a corrupt project.

    If you need to do the last option, here’s where you go for that: https://helpx.adobe.com/creative-suite/kb/cs5-cleaner-tool-installation-problems.html

    Hope this helps,
    Dennis

  • Ericbowen

    October 29, 2014 at 4:14 pm

    CS6 didn’t have the GPU accelerated debayering for R3D. CC2014 does. Completely different requirements for that ie allot more ram usage.

    Eric-ADK
    Tech Manager
    support@adkvideoediting.com

  • Simon Reichel

    October 29, 2014 at 4:24 pm

    so what you’re saying is they made an update that makes R3D basically unworkable for 90% of editors out there that don’t happen to sit on absolute beasts of render-machines? nice one.

  • Simon Reichel

    October 29, 2014 at 4:31 pm

    Hi Dennis,

    thanks for your efforts but I wanna make clear that I’m not looking for technical troubleshooting. I know for a fact that neither my system nor that project are compromised. Been editing for a while and on R3D footage almost since it came out, so it really isn’t lack of expertise here. It’s just absolute rage at the face that CC 14 is apparently in a very arrogant fashion designed to run on either the strongest machine ever or kill your computer. I keep praying for a viable open source alternative to come along and give the snobbish creative suite a thorough and much needed dusting up. helped quite a bit in the 3D scene.

  • Ericbowen

    October 29, 2014 at 4:36 pm

    If you want GPU accelerated debayering then that is the trade off. GPU acceleration never lowered the spec requirements of a system. Actually it raised them. So yes they made it so a system has to have more processing power and ram to use those features as they were intended.

    Eric-ADK
    Tech Manager
    support@adkvideoediting.com

  • Grzegorz Kwiatkowski

    October 30, 2014 at 6:28 am

    I deliver 23 minute episodes for broadcast. What I noticed rendering in Media Encoder from CC 2014 (built 81) takes 3 times longer. What’s more it sometimes stops at the end of rendering. I wouldn’t use Media Encoder for rendering, just do it within NLE. And I won’t write about other bugs that make working with CC 2014 a nightmare. Guys… stop adding more features. Fix the bugs or people will just leave this ship soon.

Page 1 of 2

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