Activity › Forums › Creative Community Conversations › OTish: Adobe Release
-
Jeremy Garchow
June 17, 2015 at 2:02 am[Andrew Kimery] “Here were are and Adobe releases feature upgrades throughout the year as well as full version releases. New version releases were always going to happen and Adobe said as much. It doesn’t function like Google Docs (where it’s just ‘Google Docs’) and Adobe never said it would. When you have as many apps that talk to each other as Adobe does it makes since to have all the major releases happen at once, but that’s only superficially like the CS days. New features (typically more minor features) can be added any time (not just with major version releases) and things like AE getting a massive, under-the-hood overhaul are possible.”
I just want a faster Ae, is that so wrong? 🙂
I don’t know bud. It seems like it’s a major yearly release, something that was looking like they wanted to get away from. I see “CC 2015” right next to “CC 2014”, I see the big marketing blitz, I see the some of the features touted months ago, and……..yeah.
https://forums.creativecow.net/readpost/378/1282
-
Andrew Kimery
June 17, 2015 at 3:56 am[Jeremy Garchow] “I just want a faster Ae, is that so wrong? :)”
No, that’s probably one of the few things pretty much everyone can agree on!
[Jeremy Garchow] “I don’t know bud. It seems like it’s a major yearly release, something that was looking like they wanted to get away from. I see “CC 2015” right next to “CC 2014″, I see the big marketing blitz, I see the some of the features touted months ago, and……..yeah.”
CS = All apps updated at the same time, be there or be square. Got something that’s ready 6 moths before the next CS launch? Shelve it for now. Got something that’s not quite ready for prime time? Release it underdone or shelve it until next year.
CC= All major updates happen at the same time (which makes sense from a cross-app integration standpoint). Minor feature upgrades can happen whenever. For clarity, “major” and “minor” are my terms, not official language from Adobe. Major releases happening under a single banner (CC2014, CC2015, etc.,) also makes it easer for users to know/talk about what version of the software they are using. For example, I have no idea what official version number PS, Muse, Illustartor, etc., are up to now, but If I say I’m running CS6 or CC2014 people will know what I’m talking about.
The suits at Adobe are freed from the feast or famine revenue cycle of the CS days and the internal dev teams are no longer under so much pressure to focus on new bells and whistles that ‘demo well’ so users will be enticed to upgrade to the latest version every 12 months. People from Adobe like Todd Kopriva, Steve Forde, Dennis, etc., have all commented on the positive changes made possible by the CC model and I see no reason to doubt their sincerity, but everyone has to make up their own mind as to whether or not to believe them.
The thread you linked to is a perfect example of the misinformation I’m talking about. The OP thought Adobe users would have no control over updating their software and Jim was ‘predicting’ how utterly horrible the plugin experience on CC was sure to become.
And I’m not saying anyone has to like CC or that there aren’t things to gripe about (and there are things to gripe about) but, IMO, Adobe has been pretty clear and consistent with the moves they’ve been making.
-
Steve Connor
June 17, 2015 at 6:58 am[Andrew Kimery] “How is the performance of LCS compared to Colorista? Colorista has always been a performance hog for me so if LCS can do the same things I usually Colorista for (which is nothing fancy) but with less of a performance hit I’ll probably shelve Colorista again.”
LCS is very fast on my system, I don’t have Colorista so can’t compare, but I’m very impressed with LCS
-
Jeremy Garchow
June 17, 2015 at 12:44 pmI should be clear, im not taking about plugins breaking, or needing constant internet connecting, Adobe engineers have proven that they can maintain compatibility through the malaise. I’m taking about how it’s done, and what I see from a subscriber to CC. I linked to the response specially, not to the other fears. CC 2015 seems like it should be a big deal, and while rewriting code is of course, a huge task, I just don’t see the reason to version it yearly.
I see the suite getting updated on a very similar schedule (albeit the amount of updates accelerated) to CS, and I think some of the benefits have been overstated.
I just want Adobe to get better. They are working hard at it, I know, its just seems odd that CC is really like CS, and not that much different, except for the cost structure.
It’s the same interface, same approach, same clickity click click on 4 different panels on a 8 buttons, wait for a preview.
Although the Lumetei Panel is pretty cool in Pr, and finally, there’s usable scopes.
-
Oliver Peters
June 17, 2015 at 12:50 pm[Andrew Kimery] “CC2015 uninstalling old apps by default is new though and a rather unwelcome, IMO, default behavior. Having the option is nice, but the default should be to leave everything in place.”
I was doing some testing with co-installed preview versions for a review and quite frankly had some issues. These were all cleaned up when I did the release install and got rid of the CC2014 versions. So I’m happy to see it that way.
I work in a few shops that are running several copies simultaneously and it’s a huge PITA. You’re always having to check what a project was cut in to stay compatible. Part of their reason for doing that was installation issue on a few machines. They have a corporate Enterprise account, which is managed by the corporate engineering department in another city. Quite a pain.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
Walter Soyka
June 17, 2015 at 1:37 pm[Jeremy Garchow] “CC 2015 seems like it should be a big deal, and while rewriting code is of course, a huge task, I just don’t see the reason to version it yearly.”
What would you propose instead?
[Jeremy Garchow] “I see the suite getting updated on a very similar schedule (albeit the amount of updates accelerated) to CS, and I think some of the benefits have been overstated. “
I get that. I interpreted comments like that to mean no more big annual release, too. I don’t know if something changed or if I misunderstood, but there is definitely still a big annual release. That said…
The DVA “suite” is being updated with features on the same schedule a couple times a year, but that makes sense as they are deeply linked. FCPX and Motion updates go together, too, right? If you look at the release schedules of non-DVA apps like Ps, Il, Id, etc. you’ll see they get feature updates on different schedules throughout the year.
Taken all together, this does actually sound “exactly” like “when an app is ready to get an update it will get that update instead of having to wait around for one specific, arbitrary time in the future when all the apps are forced to update at the same time.”
[Jeremy Garchow] “I just want Adobe to get better. They are working hard at it, I know, its just seems odd that CC is really like CS, and not that much different, except for the cost structure. “
We would have said the same thing about CS compared to the individual apps, too. Cross-product integration took a while to get going, and it couldn’t really start until the suite came together. CS was a development strategy as well as a marketing/sales strategy, and CC is the same.
The change is probably least evident right now in video, but things are definitely different than the were. We’re seeing the first roll-outs of mobile apps like Shape [link] and Hue [link]. We’re seeing new services like TypeKit [link] and Stock [link]. We’re seeing new cloud-based collaboration features like Libraries [link].
[Jeremy Garchow] “It’s the same interface, same approach, same clickity click click on 4 different panels on a 8 buttons, wait for a preview. “
Apps like Photoshop and After Effects would probably look a lot different than they do if you were designing them from blank paper today, instead of carrying their 20+ years of tradition/legacy/bloat/feature-set/workarounds/refinement/ecosystem with them. But I shudder to think of what my job would be like if all that infrastructure were dynamited and replaced, X-style, overnight.
I like that Adobe is trying to modernize without blowing up everyone’s workflow. I don’t want to manage an X-style transition on one app or another that I use every couple years.
Walter Soyka
Designer & Mad Scientist at Keen Live [link]
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
@keenlive | RenderBreak [blog] | Profile [LinkedIn] -
Mitch Ives
June 17, 2015 at 2:27 pmThis was an interesting phenomenon.
Before I even heard from Adobe about this release, a plugin manufacturer emailed me first warning me not to remove the old version, since there was a bug in the new release that disabled certain plugins Adobe had acknowledged it and was working on it. Haven’t seen that before…
Also, is it true that “remove all previous versions” is the default and that you have to go search for that setting so you can uncheck it before you install in order to avoid disappointment? If so, that’s lame…
Mitch Ives
Insight Productions Corp.“Criticism may not be agreeable, but it is necessary. It fulfills the same function as pain in the human body. It calls attention to an unhealthy state of things.” – Winston Churchill
-
Jeremy Garchow
June 17, 2015 at 4:10 pm[Mitch Ives] “Also, is it true that “remove all previous versions” is the default and that you have to go search for that setting so you can uncheck it before you install in order to avoid disappointment? If so, that’s lame…
“You have to click Advanced Settings after you click “Update All” and find the checkbox to keep older versions.
-
Jeremy Garchow
June 17, 2015 at 4:37 pm[Walter Soyka] “What would you propose instead?”
Release it when it’s ready like they claim.
Instead they seems to bundle it all up and release it. They wait for a yearly release and development wise, they seem to need to be released on a yearly schedule so much so that it’s dated.
[Walter Soyka] “Taken all together, this does actually sound “exactly” like “when an app is ready to get an update it will get that update instead of having to wait around for one specific, arbitrary time in the future when all the apps are forced to update at the same time.””
Except when that time is about a year later and the whole suite gets an update, for three years in a row. And by the way, we will delete all you older versions for the first time ever.
FCP, Motion, and Compressor get updates at the same time yes, but sometimes, especially with Compressor and Motion, that update is just to maintain structural integrity.
It seems like I’m on a witch hunt, I’m not. I just want a faster After Effects, and I had high hopes for this latest version. CC 2017 is going to be great!
[Walter Soyka] “The change is probably least evident right now in video, but things are definitely different than the were. We’re seeing the first roll-outs of mobile apps like Shape [link] and Hue [link]. We’re seeing new services like TypeKit [link] and Stock [link]. We’re seeing new cloud-based collaboration features like Libraries [link].
“LIBRARIES? WHY CHANGE THE TERM?
I kid, I kid.
I know, Adobe is working hard. They are building a one stop shop on the Cloud, available for anyone with $50/mo, they are fundamentally changing how Ae works, they are adding elements of Speedgrade to Pr, and doing it by not alienating long long long (25 years of photoshop!) standing habits and maintaining a certain amount of legacy compatibility. None of that is easy. Credit where credit’s due, etc.
I can’t stop paying Adobe. I HAVE to have it to maintain current working relationships. I just want a better experience, I don’t need another app, service, or stock agency. I need to be able to playback 4k files in Ae.
[Walter Soyka] “Apps like Photoshop and After Effects would probably look a lot different than they do if you were designing them from blank paper today, instead of carrying their 20+ years of tradition/legacy/bloat/feature-set/workarounds/refinement/ecosystem with them. But I shudder to think of what my job would be like if all that infrastructure were dynamited and replaced, X-style, overnight.”
You know this, but X is hardly an overnight transition. A lot of us managed to do it. Final Cut Legend still works to this day without an update since Feb 2010 across a few OS (and architecture) changes, and many hardware changes. I know these applications would operate differently if designed from the ground up, and I know there’s a client responsibility has to maintain, and that is a blessing and curse. It’s just that I feel I don’t have a choice with Adobe. I either learn to like it and live with the 25 year old architecture and philosophy, or lose opportunity.
-
Walter Soyka
June 17, 2015 at 5:05 pm[Jeremy Garchow] “Release it when it’s ready like they claim. Instead they seems to bundle it all up and release it. They wait for a yearly release and development wise, they seem to need to be released on a yearly schedule so much so that it’s dated.”
There is a big annual release, yes. The date is in the name, yes.
But new features also come out throughout the year, at different times for different apps, instead of having to wait for the next annual release.
Still having a big annual release is not what a lot of us expected, but it’s not inconsistent with products not having to wait for that big annual release to update, either. Under the old scheme, the feature releases in October, December, January and February (depending on which apps we’re discussing) would have been held and rolled into the June release.
[Jeremy Garchow] “And by the way, we will delete all you older versions for the first time ever.”
Yes, I think it’s a poor default, but maybe there are reasonable reasons [link] for uninstalling older versions, too.
[Jeremy Garchow] “It seems like I’m on a witch hunt, I’m not. I just want a faster After Effects, and I had high hopes for this latest version. CC 2017 is going to be great!”
You and me both, brother!
[Jeremy Garchow] “I just want a better experience, I don’t need another app, service, or stock agency. I need to be able to playback 4k files in Ae.”
Everybody has their own one thing they need more than everybody else’s one thing.
(But we do have the same one.)
Walter Soyka
Designer & Mad Scientist at Keen Live [link]
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
@keenlive | RenderBreak [blog] | Profile [LinkedIn]
Reply to this Discussion! Login or Sign Up