My feedback

  1. 225 votes
    Sign in Sign in with: Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    24 comments  ·  Premiere Pro » Adobe Interoperability  ·  Flag idea as inappropriate…  ·  Admin →

    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.


    Anonymous supported this idea  · 
    An error occurred while saving the comment
    Anonymous commented  · 

    @Patrick Palmer

    Is it actually the case that this is a critical and large change though? It's trivially easy to make a project backwards compatible by a very slight edit to the .prproj file (Premiere basically checks the version number of the .prproj, which can be changed using a text editor), and the only problem with this method is that newer effects and tools obviously aren't recognised.

    Wouldn't it be a reasonably straightforward coding job to instead make Premiere throw up a warning if the version check is failed, stating that it was created in a newer version of Premiere and hence some effects etc might be missing, and that it may be unstable? Rather than refusing to open it at all?

Feedback and Knowledge Base