Premiere Pro slow, sluggish, rendering slow after changes in the timeline

Discussion has been branched.

Thanks,
Kevin

Hello RichardDaniel,

Sorry to hear of your recent troubles.

I then exported my project as it was into a file and reimported this new file into a new project. All works fine now. new software not being able to work successfully with a project put together in the previous software. Not very good at all from Adobe, I expect better... but my problem was solved.

A basic rule of thumb amongst editors is that you avoid updating a project file from one major version of the software to the next. I'm not sure if you've ever heard that one or not, but it's an important one to be aware of—otherwise you can corrupt your project file. Only update software for new project files.

The troubleshooting step of importing the old project (thereby updating its internal software structure of the project file) can work some of the time, but should not be counted on in a mission critical project. Better to avoid updating until the project is completed in that version of the software. Keep in mind that you can have multiple versions of Premiere Pro installed at the same time.

I write about this topic in depth in the following blog post: Updating and backing up project files: best practices

Please let us know if you have any questions around this issue.

Thanks,
Kevin

That worked for you, good. Most of the "usuals" around here do recommend importing a project to a newer version, rather than "opening" it in a newer version to have the new version do the conversion process.

The "importing" process is really quite simple ... make a new project in the new version, and from the Media browser panel, navigate to the previous project file and right-click "Import" that file, and it's associated assets.

While it's recommended to finish projects in the 'major build' series they were originally created in, if you do need to move a project forward, "importing" tends to work much better than having PrPro "convert" the project.

For information, the 2014 releases of PrPro were 8.x builds; the 2015.0/1/2 releases were 9.x builds; the (confusing!) 2015.3/4 releases were the 10.x builds; and the 2017 releases are 11.x builds. You can have one release of each build series installed at any one time. I've often had three builds "up", but I've completed all the 2014 builds, and my 9.x build projects all imported into 2017 just fine.

Many of my projects work in color correction in Lumetri/PrPro just fine, but not all. To use SpeedGrade in "Direct Link" type access still, I have SpeedGrade 2015.1 installed, and use Patrick Zadrobilek's little app to convert the one character of the header needed for Sg to "see" the file as one it can read. And to do the conversion back to a "proper 2017.x" file. Takes about five seconds longer per pass than using the menu selection "Send to SpeedGrade" took. There's a small fee ... but it saves a ton of time.

Discussed in this SpeedGrade forum thread:

Update: My little Speedgrade/Premiere Project Converter still works with 2017

Neil