Principal Product Manager

Premiere projects saved in v25.6.0 cannot be opened in other v25.x versions

Forum|Forum|2 years ago
September 5, 2023
171 replies
16161 views

We are aware that customers who saved projects in Premiere v25.6.0 may find that those files now open only in v26 (beta) and cannot be opened in v25 versions. We know this is disruptive, and we’re working on a fix.

What you need to know:

Projects saved in v25.6.0 save in the v26 version format.

Because of this, they can’t be opened in earlier versions, including v25.6.1 (even though it is the current generally available release)

We’re developing a tool that will let you convert affected projects back to a v25-compatible file.

Our Solution

We’re building a small app that will convert a v25.6.0-saved project back to the v25 format. We’ll share more information, including availability and instructions, as soon as the tool is ready in the coming days.

We know that there is nothing more important than the reliability of a project file, so we’re working with urgency to get this downgrade tool in your hands as quickly as possible.

We know there are a number of downgrading apps available online, but we strongly recommend utilizing our tool when it becomes available. Non-Adobe apps and scripts are often outdated and may cause crashes and data loss.

Further Details

A bug caused Premiere v25.6.0 to prompt customers to enable Object Masking even though it is not yet in full release. Object Masking (and our yearly major version update) changes the Premiere project file structure such that it can only be opened in v26, which is only available in public beta. Turning this on caused projects to save in the newer v26 project format, even though users were still technically on the v25 release line.

Opening an older project in v25.6.0 triggered a prompt to save a copy of the project with “_1” appended. We know that many customers upgraded the project and continued working in the new copy, potentially also deleting the original. This means the only active version became the file saved in v26 format.

Premiere 25.6.0 was only available briefly before being replaced by 25.6.1 and is no longer available to reinstall. This means impacted users who auto updated to 25.6.1 cannot open v26 formatted projects.

Show previous replies

T

Tarveil

Participant

I made a post about this : https://community.adobe.com/t5/premiere-pro-bugs/i-cannot-open-my-v25-6-project/idi-p/15589804#M57798

As I mentionned,v verything was fine but this morning, after an handling error or something, my Premiere Pro has reverted to an earlier version in v25.5.

But I worked on a project for multiple hours in v25.6 and now I cannot open it. How can I do ?

T

Tarveil

Participant

Earlier this week, I updated to v25.6 and I work multiples hours on a project.

Everything was fine but this morning, after an handling error or something, my Premiere Pro has reverted to an earlier version in v25.5.

After a few research I saw this post in Reddit: https://www.reddit.com/r/premiere/comments/1ovbctq/premiere_256_update_bug_and_status/

Now I cannot go back to v25.6 and I cannot open the project I worked multiples hours on.

Please, I need help quick because I have deadlines...

Thank you

jamieclarke

Community Manager

Hi @Tarveil - Did you follow the instructions from this post? Let us know if you need help and what you are seeing.

Francis-Crossman17221443

Author

Principal Product Manager

If you did not see the dialogue to enable masking and/or you did not accept it, it's safe to continue using 25.6 but it is recommended to update as soon as we have a new version out.

Ron Rigler

Community Manager

Are seeing a prompt to enable the new masking feature when you launch?

S

Sherex

Inspiring

My 25.6 is working properly, should I leave it like this? until new release?

Many thanks!

crabspanner

Known Participant

ProRes 4444 exports are always entirely black for sequences sent from Premeire 25.6. This was not a problem in 25.5.

Tried downgrading Media Encoder to 25.5 but the problem persists and seems to be caused by Premiere.

Swtiching the export setting to ProRes 422 or other codecs seems to work fine. Happens with any sequence anmd any source media I've tried.

Anyone else seeing this?

MacOS 15.6.1
MacStudio M3 Ultra

128GB RAM

jamieclarke

Community Manager

Hi @crabspanner - Thanks for submitting your bug report. We need a few more details to try to help with the issue.

If you make a new project and import one piece of media in 25.5 do you still have the same issue?

Can you try and hold down "SHIFT" while launching Premiere and check the boxes
"Reset app preferences" (Backup Preferences first)
"Clear media cache files"
"Reset plugin loading cache"

Sorry for the frustration.

T

tonywithasony

Participant

Just updated to 25.6 and now when I start PP, it shows me a dialog box titled, "Try the new AI-powered object masking." On that dialog box is a button "Enable new masking." If I click that, PP crashes and restarts, showing me that dialog all over again. If I click "skip," I can use PP as normal, it seems.

OS is macOS 15.7.1 on an M1 Max MPB.

I tried clearing my media cache and restarting but that didn't help.

jamieclarke

Community Manager

Hi @tonywithasony -

We are sorry for the troubles you are encountering. We understand where our oversight lies and apologize to the users encountering this frustrating scenario. Rest assured that we are preparing a patch for 25.6 and will release it as soon as possible.In the meantime, we recommend uninstalling 25.6 and reverting to the stable 25.5 release.

In the Creative Cloud Desktop app, click the Apps tab in the sidebar.
Locate the Premiere Pro box, then click the three dots in the lower left corner of the panel.
Select Other versions, and from the list, choose Premiere Pro (25.5).

If you’ve enabled the masking feature in 25.6, you’ll also need to clear out some preference data before reinstalling:Remove the 25.0 Preferences Folder

Windows: C:\Users\<YourUserName>\AppData\Roaming\<AppName>\Preferences\25.0
macOS: ~/Library/Preferences/<AppName>/25.0

You can safely delete the entire 25.0 folder.

Please note that deleting the preference folder will reset all your preferences.

We will update you as soon as the fix becomes available

R Neil Haugen

Legend

I just upgraded my released version from 25.5 to 25.6 ... and now on launch, Premiere says my 25.5 Production projects "were created in a previous version and must be updated" ... ?

What the hay?

@Kevin-Monahan or someone ... ?

Everyone's mileage always varies ...

jamieclarke

Community Manager

Hi @R Neil - the team is aware of the issue please uninstall 25.6 and continue to use 25.5

In the Creative Cloud Desktop app, click the Apps tab in the sidebar.
Locate the Premiere Pro box, then click the three dots in the lower left corner of the panel.
Select Other versions, and from the list, choose Premiere Pro (25.5).

If you’ve enabled the masking feature in 25.6, you’ll also need to clear out some preference data before reinstalling:Remove the 25.0 Preferences Folder

Windows: C:\Users\<YourUserName>\AppData\Roaming\Adobe\Premiere Pro\25.0
macOS: ~/Library/Preferences/Adobe/Premiere Pro/25.0

You can safely delete the entire 25.0 folder.

Please note that deleting the preference folder will reset all your preferences.

We will update you as soon as the fix becomes available

R Neil Haugen

Legend

Thanks for the quick reply, Jamie!

Everyone's mileage always varies ...

X

Xhr1stt

Participant

When I try to send clips from Premiere Pro to After Effects using “Replace with After Effects Composition”, After Effects opens but doesn’t import the selected footage — I just get an empty composition. The dynamic link between the two apps still works, but the clips themselves never appears in After Effects.