I am really really tired of this issue.
24 cores workstation, dual Xeon v3, dual GTX 970 gpu, 64 GB system ram, 8GB video ram , 4k monitors, 6TB raid, ssd cache drive, and so on, awesome workstation for every 3D/2D software out there except Ae, Ae cc 2014 updated to last version and still mp not working how it should( waited 20 minutes to initialize 11 bg renderers with mp on, for god sake).
I use for years a workaround (from the time of cs3) for this, i lunch multiple(10-15) solo instances of single threaded AE with skip frame cheked,with the BG renderer script but that takes time also. Is really that hard after so many years to implement a dam out of the box multiprocessing working solution?
Another problem is that the raytracer is not working at all now-days and for every dam simple 3d shape i need to use 3D elements or cineware. Is ridiculous! Not to mention that dam cache is filling the ssd drive so fast and is not updating the cache how it should when i reload the updated 3D renderings. I must always manual empty cache from pref also.
Really really tired of this crap, sometimes i lose even 1 hour trying to render my scenes from Ae because of various problems while the clients are waiting for a preview render. Not to mention i cant show a dam rampreview when i want to my creative director bcz Ae mp is working only when he wants and without mp doing a ram cache is CRAZY slow in linear 32 bit float.
This software is becoming more and more ridiculous slow, and i am a user with over 12 years of Ae.
Current MP rendering is easily broken by codecs (not necessarily Adobe's problem) effects, certain types of footage, and other things. Expecting it to work on every project is overly optimistic. Fortunately the next release is right around the corner and it promises a complete rendering architecture rework.
I hope i see the day ae will properly use mp. I personally render only jpg or png sequences from Ae, effects are always the excuse in adobe's view but how are the effects affecting multiple instances of solo AE, they work this way, no need to be multi-threaded. Anyway, i will concentrate more on Nuke i think because even if i render animations in HD we use a lot of 4k material or 4K animations, or huge stock fotos and i don't wanna think how current iteration of Ae will work when 4k will be the standard for us (like next year probably).