STOP BREAKING PRPROJ Files.
STOP BREAKING SUPPORT EACH VERSION FOR PRPROJ FILES. STOP. STOP. STOP. There is no reason each update should require prproj files to ONLY work in the new version.
This is ridiculous, I like to update my premiere to the latest update as software usually speeds up but in the case of premiere each update breaks your files, slows down, had new featured FORCED in, let us move our files back to older versions and interoperate THIS WAY.
This is maddening.
Anonymous
shared this idea
4 comments
-
R. Neil Haugen
commented
Reg, is there a way to have features not in an older version auto-disable or something? Or a warning, "this project uses X, Y, and R tools which are not present in the older version" ... something to that effect?
So often, it's only going back one version that's needed, and there may be not a lot changed.
-
Steinar
commented
I agree wholeheartedly! I can understand that it needs to happen once in a while, but now it's practically every month. WHY???
-
There are a couple of possible options that we are looking into and discussing with editors both shorter and also longer term that pose unique challenges:
1) Keep the project file compatible across a version so that, for example, version 19 won't have project changes for the entirety of that version. That will allow for compatibility for that version regardless of which version of 19.x you own. Of course this would limit the work we can do that impact project files until the next major version
2) Create a feature that allows for an XML level export with support for a baseline of edits and effects only that would be backwards compatible moving forward.
-
Jim Simon
commented
The issue here is that older version of the software often don't offer the same features, so adding backwards compatibility for projects presents certain technical challenges.
