Skip to main content
Known Participant
August 22, 2024

Adobe Production: Renders Removed when Sequence is moved to different project

  • August 22, 2024
  • 6 replies
  • 561 views

Steps to reproduce:
    1. Render a "red" section in a sequence
    2.  Section turns green, has been rendered, rendered media exists within the Production default location  

         (same as Production folder).

    3. Move sequence to a separate Project within the same Production

    4. Close both projects, hit save
Result: Open project with rendered sequence, render media is offline, deleted from default render location, needs to be re-rendered.
Expected: Renders to stick regardless of where a sequence lives.
 
System info
    Application: Premiere Pro (Beta) v24.5.0.48
    OS: macOS v14.6.0, RAM: 64.00 GB GB, CPUs (logical): 24

6 replies

a_levenAuthor
Known Participant
August 22, 2024

When I initally did this workaround, after I pointed the Scratch Disks directly to the Production folder and saw that it had stuck, I changed it back to "Same as Production" and everything was behaving as it should; all renders or captured media was being sent to the correct place.

Todd_Reeder
Inspiring
August 22, 2024

@a_leven  That was what I was thinking about...if you have already done that, and verified that the production settings are still poinging to a hard path and not same as project, then no need to reset.  The key is making sure your location has not changed

a_levenAuthor
Known Participant
August 22, 2024

Hey Todd,

Happy to give this a try once everyone in the Production has stopped working.  I will note that I did this once in the past to get around this bug:

 

https://community.adobe.com/t5/premiere-pro-beta-bugs/premiere-24-5-beta-scratch-disks-not-following-production-settings/idc-p/14689097#M3007

 

With this in mind, do you think the reset is still necessary?

 

Thank you!

Todd_Reeder
Inspiring
August 22, 2024

Hmmmm....thats interesting.  If you go to File menu/ production settings/scratch disks is Video Previews set to Same as Project, or does it have an actual path that you set?  If it is set to same as project, can you please try hitting browse and manually selecting where you want it to be and see if the issue still occurs?

Participating Frequently
August 22, 2024

I'm experiencing this in the public release as well. 

Participant
August 22, 2024

I've recently eperienced the same within a Production environment.  Please advise!