Honestly, that's not unusual for your laptop specs. Ultra Key and Lumetri are incredibly CPU intensive. Are you also doing an Advanced Spill Suppresion and Key Cleaner? You only have a Sandy Bridge Core i7 2720QM I'm assuming, based on a quick search I did for 2011 MacBook Pro specs. That's a 7 year old processor. I'm assuming you have discrete graphics via an AMD Radeon HD 6750M built into that as well. Do you have the option available to use your GPU to help render at least? If ME supports OpenCL on that card, it may help a bit. I believe some of those effects are GPU accelerated, but someone would have to confirm that as I'm not sure. I've done green screen renders with Ultra Key, Adv Spill Suppressor, Key Cleaner, and a little bit of Lumetri with a Sandy Bridge-E Core i7-3820, 32GB RAM, with a 4GB nVidia GTX 960 and with an hour of footage, it took 13 hours.  That's basically a 2012 spec system and it's a desktop, so it's going to perform better, but 13 hours is still a decent amount of time. Your results are rather normal. It's just a lot for the CPU to handle. Bill Kearney LightShiftVideo.com ... View more

Hi raulvieytes, Going back to ME 2017 actually IS a download option, thankfully, because you may need it to get through some of the encodes. You can find that in the Creative Cloud app. Select Media Encoder CC > Other Versions. From there, you'll have an option to drop to Media Encoder CC 2017. By the way, dropping to 15.0.1 in AE allowed me to solve most of my encoding problems that I had while round-tripping AE content in my Premiere Pro projects, while still being able to use the latest Media Encoder (most of the time.) The latest AE files (from 15.1) are still backwards-compatible with 15.0.1 since there must not have been a major change. The key change for me, of course, is that I get failed renders on AE content within PPro (on 15.1), but I pass completely with 15.0.1. Also, doing a direct export through Premiere Pro proves to give me better results than Media Encoder (generally); however, when I have 25 videos to batch up and render, doing EACH ONE individually in Premiere Pro is rough! Bill Kearney LightShift Video http://lightshiftvideo.com ... View more

Rolling back to 12.0 absolutely fixed my problem. I had a number of Premiere projects in the render queue that were consistently failing. They all shared one thing in common--they contained round-tripped AE clips in Premiere timeline. I was able to export and render all day with "Premiere only" timelines. With the latest AME version (12.1), a series of these Premiere projects (with AE elements) would consistently fail. Without deleting the Render Queue, I rolled back to 12.0, used the exact same render queue (just reset the status of the encoding), ran them again, and they all rendered flawlessly. ... View more