Inspiring

Question

Is there any way to retain rendering files from the previous version?

Forum|Forum|7 years ago
November 11, 2018
6 replies
5101 views

Is there any way to retain rendering files from Premiere Pro CC 2018 timelines when upgrading to the new Premiere 2019? Mine just automatically upgraded …along with Premiere CC 2018 (...why do they both update?).

I opened a project today after upgrading and all the render files went missing. Now my computer is taking hours for a single timeline to render. It will likely many days to re-render all the files from recent projects. (Is it worth it?)

And it is incredibly sloooow with the high bitrate 4 k files on 1080 timeline! (I have a reasonably fast PC with 32 gigs a fast processor and new fast graphic card.) Any suggestions?

This topic has been closed for replies.

Mo Moolla

Legend

Mo Moolla

Legend

Hi Brit

Have a look at this post. I am sure it will be of use to you

Moving Premiere project to new PC inc. cache files (.cfa, .pek, etc.)

Mo

Brit.bAuthor

Inspiring

Thanks. It looks like a complicated work around but I'll try it tomorrow.

R Neil Haugen

Legend

This takes hours to re-render all my relevant sequences ...every few months that Premiere upgrades. I'd really prefer to keep my old render files than have my computer stuck rendering for hours on end every time that there is an upgrade. I' haven't had a chance to try the Moving Premiere project to new PC inc. cache files (.cfa, .pek, etc.) , but do i need to make all new locations?

There are parts to having a stable working process that so may find inconvenient. Budgeting time to test new versions before committing major projects to them is an obvious thing to me but one so many skip ... then come here or elsewhere complaining their projects are broken by the new version and they can't go back, for example.

I *test* before committing projects to new versions. Therefore I never have trouble reverting to a previous version to keep the work going while waiting for an update to the new version that will work for me. I learned to do that the hard way of course, then realized how stupid I'd been not to assume that process was needed.

That goes back to the old comment wondering if you don't have time to do it right, where will you find the time to do it over.

Editing and editing apps and workflows are very complex with variables beyond thought. And the hardware is also a huge and complex eternally shifting aspect of the business. Oe version may work better ... or not ... with any specific media/effects/hardware combination.

Whether we want it to or not, all those variables affect our work and many are not under the control of someone writing code.

Using the cache files, previews and such created by one code version in another is simply adding risk and potential sources of instability to the process.

I've learned that minimizing risk is both necessary and wise, as over time, it SAVES a massive amount of time and heartache.

Neil

Everyone's mileage always varies ...

C

Carlos Ziade

Community Expert

To add to Grigor's message, try also to import your latest project created on the previous version into an empty

project started on the new version

Grigor Poghosyan

Participating Frequently

try opening project from the last autosave file of previous version.

Brit.bAuthor

Inspiring

try opening project from the last autosave file of previous version.

Wow! That solves the "reveal in project" glitch. Thanks! But it doesn't help with the missing renderings, though at this point I've re -rendered most recent projects. Actually perhaps a simple rebooting of the computer may have solved the the "reveal in project" glitch..? It seems to work in other non auto-saved files as well for now. I'll keep you posted

E

excited_Genie16B8

Legend

Opening older projects in a new version of the software will normally carry the Cache and Scratch files with it. Not sure why that didn't happen in this case, but I'm not aware of any way to force PP to relink the previews.

Brit.bAuthor

Inspiring

I just updated my video card NVIDIA software (for a GTX 1660 6 gb card) and now the Mercury engine is on.

But I opened a new project and now also have the same problem as the last project - no renderings attached (....how does one tell is if the media caches ate still attached?). I am rendering 6 minutes of various bit rate 4K footage on a 1080p timeline, and its taking over 2 hours! There are a few short bits where the timeline is using the optical flow on slo mo, but this speed is ridiculous. It used to take 15 minutes. It is not worth it upgrading to the new Premiere 2019 at this cost...or is it? Any suggestions?

Brit.bAuthor

Inspiring

BTW, I discovered that the Adobe help line is useless. I waited 1.5 hours on the phone and chat lines ..twice. Time to find another product?

E

excited_Genie16B8

Legend

Mine just automatically upgraded

That's actually not possible. To get updates and upgrades for Premiere Pro, someone has to push that blue Update button.

Brit.bAuthor

Inspiring

Sorry, you are correct. The CC cloud box kept automatically popping up suggesting upgrades, so I finally did. Why do they always ask to upgrade 2 versions of the software? ...perhaps in order to wait to see if the bugs have been removed on one's computer configuration for the latest version, so if there are problems then one can return to the old one without a hitch? In that case, I think I'll have to do that since 2019 is not working for me wit these renderings...but I haven't given up yet. .

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded