Downgrade newer project
When someone saves a .prproj in a newer Premiere and your current app cannot open it, drop the project file onto the slot or click the slot to pick it. LmBox Bridge rewrites a copy to the version of your currently saved project, then imports it into the Project panel. If the source version is already no higher than the current one, it imports as-is without changing the stamp.
What you will learn
- Drag "Downgrade newer project" into an empty Toolkit slot
- In connected Premiere CEP, save the current project first, then pick or drop
.prprojfiles - Tell "Downgraded and added to the Project panel" apart from "Imported; no downgrade needed"
Where to find it
- Open in the sidebar
- Drag Downgrade newer project into an empty slot
- Click the slot: a multi-select file dialog opens (
.prprojonly) - Floating toolbar: you can also drop
.prprojfiles into the left drop slot first, then click this slot (drop-slot linking is supported)
Works with Premiere CEP only (CEP_PPRO). Open and save the current project first, then connect the extension. Premiere UXP, DaVinci Resolve and others do not use this tool.
How a run finishes
- In Premiere, open the project you are working in and save it to disk (the current project path and version must be readable)
- Click the slot, or drop one or more
.prprojfiles into the floating toolbar's left slot first, then click - LmBox Bridge reads the root project
Versionof the current project, and for each source file:- Source version higher than current → writes a sibling copy (file name marked with the current app version), sets the root project Version to the current value, then imports into the Project panel → footer "Downgraded and added to the Project panel"
- Source version not higher than current → no stamp change, import directly → "Imported; no downgrade needed"
- When you pick several at once: all success shows the import count; partial failure reports success / failure counts
The original file is never overwritten; the downgraded result is a sibling copy that is then imported.
Common failures
| Footer tip | Meaning |
|---|---|
| Connect Premiere first | Extension not connected, or the host is not Premiere CEP |
| Save the current project first | Current project path cannot be read (unsaved / metadata failure) |
| Choose a different project file | The selected path is the project that is already open (same_file) |
| Choose a Premiere project | Source path is invalid |
| That drop is not a project. Choose again | The drop slot has no usable .prproj; the file picker opens instead |
| Could not change the project version / Could not import the project | Read/rewrite or import failed |
Notes
- Only the Version number on the root
<Project ObjectID="1">is changed, so the current app can read the project into the Project panel; it does not guarantee that features unique to a newer Premiere work fully in an older one. - The current project must be saved to disk; without a save there is no target version.
- In a batch, a single failure is counted and the rest continue; when only one file fails, the matching reason is shown directly.
Further reading
Release notes
3.1.0New: "Downgrade newer project". In Premiere CEP, stamp a newer.prprojto the current project's Version and import it into the Project panel; supports multi-select and floating-toolbar drop; if the source is already no higher than current, imports as-is.