[Andy Engelkemier]"Is anyone else quite unhappy with the direction this took? It seems like it's riddled with mistakes, and what's up with them removing features?"
It's frustrating isn't it? However, I'm not unhappy with it because I understand what they're doing. CC 2015 doesn't have "removed" features as much as it has "features that haven't been implemented yet". CC 2015 is kinda like an alpha release as the After Effects team is in the middle of completely re-writing the core code of the software. And, yes, it's got quite a few bugs, but this is a much bigger change than when they went from 32-bit to 64-bit in CS5. They aren't adapting the code this time; they're remaking it so that AE can finally be an actually multithreaded software. There are actually fewer problems then I thought there would be, to be honest!
CC 2015 actually gets me very excited because it shows the AE team is focusing now on useful changes to the program in the areas of performance, productivity, and usability instead of trying to introduce whizz-bang features nobody uses (ray-traced renderer, I'm looking at you). Take, for example, the changes they've made to how expressions are handled. If you have 40 layers that all reference one layer and then accidentally delete that one layer, in the past that would have meant clicking "OK" on an error box for every single broken expression. That means that if you only had one property linked, you have to click through 40 errors. Heaven help you if you'd linked several properties! And pressing "undo" wouldn't fix them all either. If you did Undo, you'd have to go back through and re-enable every expression! Now, you simply get a warning banner at the bottom of the comp window and pressing undo fixes all of the expressions. SO MUCH TIME SAVED!
That being said, Adobe shouldn't have marketed CC 2015 as a normal upgrade to AE. It's really more of a beta, teaser kind of release. And they CERTAINLY shouldn't have made the Creative Cloud software automatically remove older versions! The AE team was against that plan and tried to warn people about it...
One thing the AE team did very well to help this transition time is that CC 2014 and CC 2015 can both use the same project files. So you can work with the snappier interface in CC 2015 and then jump back to CC 2014 for any features that are missing (like, for example, multiprocessing).
- The Great Szalam
(The 'Great' stands for 'Not So Great, in fact, Extremely Humble')
No trees were harmed in the creation of this message, but several thousand electrons were mildly inconvenienced.
I agree. I like the direction they are trying to take, but it shouldn't be released like a beta is all. keep beta features beta, and only release things that work really well.
I just don't understand why they don't add some other things that have been around in other software for a Long time, like automatic background preview caching. Hey, I walked away from my computer. Oh look, my entire sequence can be played back without having to render the audio before preview, and the section that's crazy slow due to an expression can actually be played. That's when I'll be happy with "preview".
So the direction? Sure, that's fine. But I feel like they are releasing things just to try and justify the extra price everyone is paying now for CC. Are most people Really that much faster from CS5/6 to now? Maybe a tiny bit.