Skip to main content
Known Participant
June 18, 2024

Premiere 24.5 (Beta) - Scratch Disks Not Following Production Settings

  • June 18, 2024
  • 4 replies
  • 506 views

Steps to reproduce:
    1. I render a sequence in a project that is within a Production.

    2. The Video Previews are sent to the folder where that Project exists within the Production and not to the root level of where the Production is located, as it is set in the Production settings.
 
Result: Video Previews, aka Media, exists within folders that is inside of the production
Expected: Video Previews should go to the root level wher the Production exists, as per the Production settings.


System info
    Application: Premiere Pro (Beta) v24.5.0.48
    OS: macOS v14.0.0, RAM: 64.00 GB GB, CPUs (logical): 24

 

This is happening across all scratch disks that are set to "Same As Production."  Meaning, Captured Audio, Audio Previews, etc.  Everything is being sent to the folder where that Project exists within the Production and because of this those folders are showing up within the Production.

4 replies

Fergus H
Community Manager
Community Manager
May 14, 2025

Hi all, 

 

This issue is fixed in v25.2 of Premiere Pro. If you're working on a project and would prefer not to upgrade immediately, Ben's recommendation (https://community.adobe.com/t5/premiere-pro-beta-bugs/premiere-24-5-beta-scratch-disks-not-following-production-settings/idc-p/14916574#M5709) is still valid. 

 

Regards,

Fergus

Participating Frequently
October 9, 2024

When using productions, The autosave is saved in the production folder heirachy even though its set totherwise in the preferences. This is causing Duplicate Project messages and is a mess. 

Dynamic_EclipseB837
Participant
October 13, 2024

Yes! Me too. But I'm not even on the beta. This is happening in the current release.

a_levenAuthor
Known Participant
June 18, 2024

Amazing, thanks so much.  Apologies for not checking the forums first!

Todd_Reeder
Community Manager
Community Manager
June 18, 2024

Hi @a_leven this sounds like the same case found over here:  https://community.adobe.com/t5/premiere-pro-bugs/scratch-disk-settings-in-production-set-to-quot-same-as-production-quot-but-not-actually-saving/idc-p/14675760#M28818

 

The current workaround is to set your Production Scratch Disks to a new custom location. This will re-save them correctly in the .prodset file, and you can return to using the "Same as Production" setting after that