[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?”
2014, 2015, and 2015.3 are all 13.x releases and all use the same project file format. We’ve moved piles of AEPs betwixt and between versions without issue, so I’m not worried about backward compatibility.
I would definitely recommend hanging onto the 2014 install for MP rendering, and I’d also suggest hanging onto the 2015 install until you have put 2015.3 through the paces and know it’s good for your workflow.
A couple known issues so far:
1) Live Templates with expressions don’t work correctly.
2) Audio may render incorrectly through Media Encoder if it has levels keyframes or audio effects applied in Ae.
There’s another issue to the percentage of us using Macs/Hackintoshes with certain NVidia cards. It’ll kernel panic when GPUsniffer runs (which is how it determines what your card is capable of). I’m on a thread where this has happened to someone with a Mac Pro using a non-standard NVidia card, and I have the same issue with Premiere. In his case, he can remove gpusniffer from the package contents and get it to run AE. Premiere won’t just shut my computer down if I remove it, but it won’t let me run the program because I then “don’t have a video card” according to Premiere.
So if you’ve got an NVidia card in your machine that didn’t come with it, you might want to be cautious about overwriting your programs. And I was so anxious to finally be able to edit my Raven footage in Premiere instead of Davinci on this machine. I haven’t tried on my MacBook Pro yet, but I assume that would work at least.