while this is a rather critical and large change to the way the application works and will take some time to be implemented, we’ll definitely put this under consideration.
There’s more than one solution to this problem, though.
A good short term opportunity is to use the parallel install feature in the creative cloud application. It should help to at least take away some of the issues working with people on a different version of the application.
Another thing worth keeping in mind is that you can install CC on two different machines (if you’re on an individual subscription). That gives you additional opportunity to keep different versions around for compatibility reasons.
I’ll update the status of this request as we move along.
If you have further thoughts on this matter, please keep them coming.
An error occurred while saving the commentAnonymous commented
that you have to make a big brake,
can be ok.
But then you have to do it clearly
and do not play around in a running version.
In addition, it should then,
apart from effects, etc. be possible the pure cut
from an existing version to a new version
and to be able to transport back.
Autodesk has at the change, a render engine, once over several versions
the possibility had to be new or old.
But what happened in the current CC2018 version,
is the culmination of bad software management.
In the ADOBE forum is to be read, which Apple announced in 2013,
Quicktime 7 will disappear.
And then suddenly you have to work on it in panic?
Why then you do not have the versions CC2017 and CC2018
of the software options just kept the same
with 2x different render machines?
And that also communicated to the tenants.
It's just silly that you always have to deliver new feature,
so that the tenants continue to rent.
Stability, structure and performance can also be part of long term rental clients.
But that's not what ADOBE managers think.