[Brad Bussé]

So if you want to retain multi-core rendering as well as backward compatibility for safety on 2015 projects, I assume we should be retaining both CC 2014 as well as CC 2015 along with CC 2015.3?

[Brad Bussé]

Update: Fresh install fixed it.

[Brad Bussé]

Thanks for taking the time to document the details of your fix to share with the community!

[Brad Bussé]

Yes, the last thing my client says is rendering, then as soon as it says that it immediately switches into Idle mode.

I had another Mac client that worked for a couple weeks fine then stopped. I tried to fix that and add a different PC Client too, but with no luck. I just moved after a renovation at work so I have a new office with more network ports so I’m not running any routers this time and I was hoping that with a newer imaged PC would fix things.

I am generating GI for this scene, but not passing the GI cache along through the team render.

[Brad Bussé]

Not much at this point in the workflow (the character models are already reduced and using normal maps), but I’m 2/3 done now. I did find that in Element there is a checkbox for optimizing geometry which does some reduction, so I enabled that for all of my models.

[Brad Bussé]

I just noticed that if I use Expose to show all windows or the desktop, the white goes away, but comes back when I go back to working display mode. So it doesn’t appear to be monitor/cable related, but an abstraction layer issue or something.

[Brad Bussé]

Thanks, Walter. It would seem that Element would benefit from supporting multi-core just from the observation that it’s completely maxing out the single core during rendering.

Do you know if Element supports dual D700s? I’m wanting a utility that monitors the GPUs and VRAM so that I can see where bottlenecks are in my workflow.

[Brad Bussé]

Yeah, I have the latest update for 2015 (2015.0.2). I’ve run pram reset, permissions fix, maintenance cron jobs, file system check, deleted adobe preferences, etc. with no luck.

I know, I’m definitely waiting on El Capitan. I was hoping that shortly after it was released we’d have an update returning Multi-Processor support, and at least some support for the Metal API. Neither of those have come about yet, but I am dealing with these pleasant memory leaks.

[Brad Bussé]

I had 6 GB reserved for other apps, so 58 GB were available for Pr.

I started a new project today, and am having the same problem. Today when Premiere was paused by the OS, it was using 99.00 GB of memory and 92.33 GB of Compressed Memory.

I’ve just switched from Performance Mode to Memory Mode and allocated 14 GB of RAM to other apps leaving 50 GB for Pr. We’ll see if that helps, but I doubt it–it looks to me that Pr 2015 has a serious memory leak since I’ve worked with much more complicated projects in the past and never seen this kind of runaway memory usage.

[Brad Bussé]

The 6-core w/ Mountain Lion running CC 2014 is probably one of the most stable and best bang for the buck systems right now. I’d say you’d be fine upgrading your OS, but if you’re stable just wait. I’m on a 2013 8-core Mac w/ D700s on Yosemite. The first 6+ months were a nightmare–I couldn’t use Mercury acceleration at all (in this case it appears to have been Apple who dropped the ball with their implementation of OpenGL). I invested in the dual D-700 model because I knew that CPU tech is hitting a Moore’s law brick wall, and GPGPU is where the new gains are going to be realized.

Last year Adobe took a poll asking users if they wanted features or a massive increase in speed. They overwhelmingly received requests for speed increases. In CC 2015 Adobe made some major changes to the underpinnings of the core tech. in Ae but it’s only half-baked for what was expected by the community. For instance, in Ae 2015, Multi-Core support is removed to make way for the new tech which isn’t yet implemented. Which means that you need to retain Ae 2014 to handle the multi-core rendering of 2015 projects (to Adobe’s credit they did make the bridge for this to work with compatibility, but they didn’t make it clear to users that this was the path to the interim workflow).

Adobe demonstrated massive speed increases to Illustrator and a couple of select plugins in Ae using Apple’s new Metal API in El Capitan at the last WWDC, and stated that they were committed to fully supporting Metal in all Adobe apps. They recently backtracked, even though they had said at the WWDC event that the Metal implementation was extremely quick and easy to implement. It doesn’t appear that GPGPU support will be fully realized until at least CC 2016.

Premiere doesn’t work with El Capitan yet. I’ve had some serious issues crop up with my current project on Yosemite the past couple of days–app crashes, system freezes due to app crash, and for the first time ever I got an OS popup saying that my system was completely maxed out on RAM and couldn’t continue until I cleared up some memory space. In Activity Monitor it showed on my 64 GB system only running Premiere (with one Ps file in the project) that I had a couple dozen GB of compressed RAM (virtual), and it showed 26 GB of active RAM dedicated to Photoshop Server. I can only think that there’s a memory leak in Adobe’s code creating this.

I’d say, wait at least another month until there is official and user verified stable support for CC 2015 with El Capitan. Then backup all user and project and media data. Format your boot drive and do a clean install of the OS and Adobe apps.