Please stop making it so difficult to work with different Premiere-versions!
It is really annoying to work with Premiere pro, dealing with clients who doesn't always have the newest Version. The changes you make with the upgrades are not that huge, so I don't See the reason to make it impossible to work with a slightly older Version, importier a file from a neuer one. I appreciate the whole adobe suite very much but this is really a pain, since the updates are coming more frequently
Florian Schurz
shared this idea
Hi Florian,
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.
Thanks
Patrick
24 comments
-
Trevor Asquerthian
commented
I've had to 'downgrade' projects in the past - and have done so by opening the project in a text editor and adjusting the 'version number'. Caveat emptor - I'm sure there's something it will break - but it hasn't been a problem for me.
-
[Deleted User]
commented
*************,
when our customers start projects in the newest version
and then handing over these projects, we are also forced to
so that we can open your projects.
Partly you could not open between different CC18 projects.In addition, you can find in the network to get around your lock,
that's not nice,
that's not practical if you're a company and not a single fighter,
but it works and if you try it, it works very well.
In reality, that was just an ADOBE way of forcing customers to update.
Is this still necessary in times of software rental at ADOBE?The biggest ADOBE problem is that you do not understand your customers
Greetings
-
Alan
commented
What about a save in compatibility mode option where you can choose to strip the project file of features newer than a year or two?? Would you go for that?
-
TaranVH
commented
I have to side with Adobe on this one.
Certain bug fixes, feature changes/additions, and changes to underlying foundational code, simply must sacrifice backwards compatibility. You CAN work hard to maintain it, but then your code gets even more complicated, and therefore buggier. You've got all this obsolete legacy nonsense that you have to support for no reason...It can be done, but especially with all the normal bugs that adobe still has to deal with, I woudln't want to add this onto the pile of things making it more difficult for them.
My solution is to always have the most recent version of Premiere on my laptop. Then I can at least open the project and see what's inside, and I can export a cineform clip of the whole timeline if need be. Our main desktops have the most recent STABLE version of premiere. (Currently 2017.1.2 is the most recently stable, but we are unfortunately on 12.0.1.)
One thing you can try is to export to XML. Then import that XML into your older version of Premiere. Mooooost things should remain the same in the project. Some stuff could be missing completely, though. I think I've had trouble with clip speed not being retained, for example.
If worst comes to worst, you can always export a whole sequence with certain layers made to be invisible, and then do another export where other layers are visible/invisible... And then recombine them into a new .prproj.
More on-the-mark than your suggestion, would be this one: https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/33843463-slower-release-schedule-with-more-stable-software
Not great, but we're working with what we have, not with what we wish we have.