Known Participant

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

Forum|Forum|1 year ago
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.

Fergus H

Community Manager

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

A

Adam5C21

Participating Frequently

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.

B

Ben Insler

Community Manager

Hi @Adam5C21 ,

Thanks for reporting this. This is unfortunately a known bug we are looking into where the Premiere Pro Production .prodset file loses track of the "Same as Production" scratch disk target, triggering a roll back to the "Same as Project" scratch disk target (even though your Premiere Pro scratch disk settings will still display "Same as Production," since "Same as Project" is not an available option in a Premiere Pro Production).

There is a quick way to repair this. Instead of using "Same as Production" in your scratch disk settings, set your scratch disk target locations to a specific location on disk using the "Browse" button. By choosing this path directly rather than using the "Same as Production" shortcut, Premiere Pro will write the updated custom path data to the .prodset file and repair the issue. You can set this location to be the exact same place where "Same as Production" would save your scratch disk content if you would like to do so - the issue is not with the location on disk, but with how Premiere Pro handles the "Same as Production" shortcut.

Note: The steps above will not remove any existing scratch disk folders that have populated throughout your production as a result of the bug. These will have to be cleaned up manually.

A

a_levenAuthor

Known Participant

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

Todd_Reeder

Community Manager

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

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