-
OTish: Adobe Release
-
[Walter Soyka] “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.”
It’s just too bad they decided to modernize by blowing up over half their customers business models.
I think this 2015 release confirms what those of us who’ve been asking for a buy-out option have been saying since day one. CC is CS with some optional online tools and an always-on internet dongle to force payment of rent. The only thing preventing sale of perpetual copies of CC desktop software is Adobe management and Wall Street stubbornness. We’re in year three of a long game. I don’t expect anything to change for another year or two, but I predict Adobe will eventually discover that the “Like it or leave” approach to customer relations is not sustainable.
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
https://lnkd.in/Cfz92F
facebook.com/dlawrence
twitter.com/dhl
vimeo.com/dlawrence/albums -
[David Lawrence] “It’s just too bad they decided to modernize by blowing up over half their customers business models.”
Touché. 😉
-
[Steve Connor] “LCS is very fast on my system, I don’t have Colorista so can’t compare, but I’m very impressed with LCS”
There’s good to hear as Colorista (like all Red Giant plugins I’ve used) is the opposite of fast. 😉
-
RE:vision was the first I saw… it’s not something they can fix apparently its Adobe that will fix it.
Hopefully, Adobe will tweak it before others report it…
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
-
I do think Simon, who has actually developed plug-ins, seemed to agree plug-in incompatibilities could be a real problem with constant new releases. I don’t think I was “predicting” it would happen, I just thought it could be an actual risk, and I think there was some agreement on that point.
Jim Wiseman
Sony PMW-EX1, Pana AJ-D810 DVCPro, DVX-100, Nikon D7000, Final Cut Pro X 10.2.1, Final Cut Studio 2 and 3, Media 100 Suite 2.1.6, Premiere Pro CS 5.5 and 6.0, AJA ioHD, AJA Kona LHi, Blackmagic Ultrastudio 4K, Blackmagic Teranex, Avid MC, 2013 Mac Pro Hexacore, 1TB SSD, 64GB RAM, 2-D500, Helios 2 w 2-960GB SSDs: 2012 Hexacore MacPro 3.33 Ghz, 24Gb RAM, GTX-680, 960GB SSD: Macbook Pro 17″ 2011 2.2 Ghz Quadcore i7 16GB RAM 250GB SSD -
[Andrew Kimery] “There’s good to hear as Colorista (like all Red Giant plugins I’ve used) is the opposite of fast”
All too true, however what’s even slower than Colorista’s keyer is the LCS having no keyer at all. No keyer, no secondaries, no eyedropper, no thank you.
Herb Sevush
Zebra Productions
—————————
nothin’ attached to nothin’
“Deciding the spine is the process of editing” F. Bieberkopf -
We’re going to keep chasing our tails here.
[Andrew Kimery] ” Of course that’s just a symptom of a greater problem with customers in general which is everybody wants something different and everybody is convinced they should be priority number one.
“You wouldn’t have had the announcements or suggestions, quite like the blog post you linked to (and I was actually thinking of the blog post that was linked in there, which has the feature requests going back to 2011) without CC because of SOX or whatever. The first feature request, of course in many facets, “make it faster”. Lots of work was done on tweaking the shit out of the cache. Tweaked and tweaked, great efforts, brilliant ideas, same cache. No GPU except for extrusion.
So with CC, and with these up front communications, and development being pegged as a priority, you’d think it would get better since 2011, or 2012. Don’t you? Almost every other app in the suite has gotten a ton of love, and some more have sprung up that no one I know uses, will use, or even downloads. So, am I wrong here? Adobe, themselves, not bloggers, not pundits, not me, have made up the fact that a lot of people have wanted Ae to go faster, and Adobe keeps pointing out they are working on it, for years.
[Andrew Kimery] “Right. Adobe said they can/will release feature upgrades at will, as opposed to only annually, and they have been doing that.”
Again, we are like this.
They release feature updates at will. Every year.
You seem to think that Adobe couldn’t release After Effects v2016 without Pr being updated with ALL the updates scheduled for Pr 2016. If Pr needs an update to maintain compatibility for dynamic link, or whatever, for Ae 2016, why not just push s small a little update the completes just that, just like Apple does with Motion and Compressor when X gets big updates? Nothing more, nothing less. They wait. They have a year, they make a list, and push out big yearly updates. “At will” is highly scheduled.
[Andrew Kimery] “It’s also part of the ‘problem’ of having a more mature, established app.”
Yeah yeah. All of the core apps in CC are old and established, it really is why Adobe could have done what they did with CC (just like Apple is the only company that could have done what they did with FCS). I know what Adobe is doing is hard work, but they’ve put in a lot of hard work on the cache and render, and literally, in a year, most of those options are deleted and undone. Literally, the years of work on the cache and render have vanished from the preferences.
-
[Herb Sevush] “All too true, however what’s even slower than Colorista’s keyer is the LCS having no keyer at all. No keyer, no secondaries, no eyedropper, no thank you.”
Also good to know. Sometimes a primary is all I need though. Looking forward to playing with things once my current gig wraps up.
-
[Jeremy Garchow] “We’re going to keep chasing our tails here. “
Yup. I think we’ve both throughly established our POVs.
Until the next thread!
-
[Jeremy Garchow] “The first feature request, of course in many facets, “make it faster”. Lots of work was done on tweaking the shit out of the cache. Tweaked and tweaked, great efforts, brilliant ideas, same cache. No GPU except for extrusion.”
In every previous version of After Effects, the UI and the renderer were linked. One working blocked the other. The bulk of the work evident in 13.5 is the separation of the UI and the renderer. I don’t think any other meaningful acceleration could have happened without taking this first major step — redesigning the fundamental After Effects architecture without breaking everything else.
[Jeremy Garchow] “I know what Adobe is doing is hard work, but they’ve put in a lot of hard work on the cache and render, and literally, in a year, most of those options are deleted and undone. Literally, the years of work on the cache and render have vanished from the preferences.”
If by “render” you mean multiprocessing, please understand that multiprocessing was horribly inefficient, in large part because it was a very old hack that lived on past its expiration date.
If by the cache being “deleted and undone” you are referring to the feature of caching in the background, see above — that feature depended on multiprocessing, and the entire point of this release is getting to a place where system resources can (finally) be efficiently used.
None of the hard work on the cache is gone.
See here for more:
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