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.

Brit.bAuthor

Inspiring

Hi Brit

"I have seven partitions on 6 hard drives. The SD drive is divided into a C for applications (400GB), and D (600GB) for video previews and the media cache"

Can I make a workflow recommendation?

This is what my Scratch Disk drive looks like on all my Macs.

Try to keep your Scratch Disk completely separate from everything else. Partitioning doesn't mean it is physically separated as you know, Its just on a separate area of the drive, One of the most, if not the most important performance areas to take into consideration is your Scratch Disk where your Media Cache and database files are stored. This makes such a huge difference with the type of footage I see you are using you will not believe. So my recommendation is:

1. Use a fast SSD (like a Samsung Evo 860 or even a PCi-E drive (these are ridiculously expensive though. and aren't worth the money yet)...

2. Create your scratch folders as you can see in my pic for PP and do not partition, This disk must remain for just your cache files. Once you are done on a project "Collect: all files as per my first post. This will transfer all generated cache files into your chosen folder for storage and archiving. In the even you need to move to another machine everything will be neat and tidy in one central place.

3. Keep you OS on another SSD (away from anything related to cache files)

The reason for this is that you are reading and writing data at a tremendous rate while scrubbing/rendering. Should your scratch disk not be an independent one or one that is partition for even shared with your OS its longevity and speed WILL suffer.

The one and only time I make an exception on this is if I am using my MBP to lecture so the edits aren't of a critical nature. However this who only have laptops should also follow this workflow IMO and use a fast USB 3.0/Thunderbolt/USB C drive as the scratch area.

I use this on ALL my workflows, whether it's for a short doccie, music vid, vfx work or long form edits

Trust this helps

Mo

Thanks. I bought a large SSD 3 years ago for both my operating system and a separate partition for cache files and, thinking that it'd speed up my renderings... but it looks like that was a mistake? My video data files are kept on a separate dedicated HD SATA drive. I have since tried moving some of my timeline preview files to 2 spare internal SATA hard drives, but I have kept the media cache files on the partitioned SSD drive.

Perhaps I should move them to one of the spare internal drives a s well? How about all cache files on one drive and all timeline preview renderings and proxie files on the other SATA drive since the spare drives are not too large (one is 6 gigs, and the other is 3.5 gigs at 10k rpm)?

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