Skip to main content
Participant
November 19, 2024
Question

Links to render files are lost AGAIN after Premiere Pro update

  • November 19, 2024
  • 4 replies
  • 2728 views

Upon updating to Pr Pro 2025 (both standard and beta versions), it has lost the connection to those 1200 render files in the Video Previews folder. It took nearly 10 hours to render my project timelines so I could work on my 4K edit without a lag (2019 Macbook Pro 2.4 GHz 8-Core Intel i9). Upon opening the Pr24 project file in Pr25, there is the standard requirement to save a new version, but there is never an option to reconnect to missing render files. Why should there be? Everything should point to the same place.

 

I had this issue when upgrading to Pr24, but temporarily moving the project (proj) file over to my desktop from my external editing drive fixed that. Subsequent projects retained links to render files, even if the .proj file was within the external drive's project folder with the Adobe files.

 

I've been on chat for nearly three hours now, walking two separate agents through the problem. Alas, just confusion and requests to access my computer which is just not an option after my last experience with that, plus being in violation of this client's NDA. They asked me to open an autosave file, resulting in Pr25 asking me to reconnect the render files. Perfect! But when the project fully opens, it's still a yellow bar. Maybe that will work for others.

 

I'm no software engineer, but an option in the Sequence menu to 'reconnect render files' would be mighty fine. I'm strongly considering moving over to Resolve for future projects. Time is money.

 

Anyone have a simple fix? Keep in mind that I'm not talking about thumbnail images. I'm talking about the rendered .mov files that magically turn that yellow timeline bar to green.

4 replies

Participant
December 12, 2024

Not all the time, but some of the time, it is possible to go back to the most recent autosaves when the render files were connected. 

MyerPj
Community Expert
Community Expert
December 12, 2024

Does the 'most recent autosave' have significantly more connected render files? What I've seen is it's not the same missing render files each time I load a project, it's more at random.

Participant
December 12, 2024

My experiences have been all or nothing.

Community Expert
November 19, 2024

It sounds like using proxies might be a better approach for your workflow compared to relying on preview render files.

Proxies are much more stable and can save time since you only need to create them once, regardless of updates or file relocations.

Proxies are low-resolution versions of your media that make editing faster and smoother, especially with high-resolution footage.

For more information on setting up a proxy workflow, check out Adobe’s guide here: https://helpx.adobe.com/au/premiere-pro

Participant
November 19, 2024

Will do, Paul. Probably time I started doing that. Thanks.

MyerPj
Community Expert
Community Expert
November 19, 2024

Here's another thread, it's got some upvotes already, but upvote both these, it's the big number up top left, near the thread title.

https://community.adobe.com/t5/premiere-pro-bugs/some-prores-422-video-preview-files-lost-on-closing-and-re-opening-project/idi-p/13978848

 

MyerPj
Community Expert
Community Expert
November 19, 2024

That would be a welcome feature to have a relink render files. Or even a try again to find them, if the first pass doesn't. 

What format are the render files in? There's another thread here that's been ongoing, dealing with ProRes files. Mostly it works for me, but there has been issues. PP wants to work on local drives, do you have drive letters mapped for your external drives? PC or Mac?

Participant
November 19, 2024

Mine are also ProRes 422 4K files. I do not have drive letters mapped -- at least I don't think so. Isn't that more of a Windows tactic? I'm on a Mac.

The other thread mentions render settings in Sequence Settings window. These are mine:

MyerPj
Community Expert
Community Expert
November 19, 2024

 I upvoted here, but suggest you put in a post over at  that thread, since @Kevin-Monahan has noted the bug report and is following it.