Productions mode reverts the Auto-Save setting in Scratch Disk Setting for everyone on the team

[POwens]

Description:  I'm part of a team of editors working on a LucidLink hosted project - all media and project files live there.   I requested that each editor set their Auto Save location to a local drive so as to avoid a single point of failure, but everyone's Auto Save destinations are constantly reset to lie inside the root level of the Production.

Why is this a problem:  1) It's messy and unexpected.  2) It causes uneccessary traffic to and from the cloud filespace, which reduces streaming bandwidth.  3) Causes a single point of failure.   If our editors lose their internet connection, they not only lose their media, but their auto saved projects.  We do have automatic local backups of course but the autosave setting should not get changed.

To reproduce the problem:

1. Create a Production in a shared storage environment, in this case LucidLink

2. Set Auto Save destination to a local drive in Production > Scratch Disk Settings.

3. Quit and reopen app and Production.

4. Auto Save destination has now been reset to the root folder of the shared filespace Production.

Expected behaviour:   Once set, Auto Save location does not change for any user.

Actual behaviour:   Once set, Auto Save location changes for every user.

Media stored on LucidLink.   Premiere version 2025.1.   macOS 15.4.1 (though other editors may have other OS versions)

[mattchristensen]

@POwens Thanks for sharing the details of what you're seeing. This is not a bug, it is Productions working as designed. Scratch disk locations are part of Project settings, but in a Production they are part of the Production settings and applied to all projects in that Production. This is crucial for things like Video Previews, as it ensures that a sequence rendered by Editor A is also rendered for Editor B (because they both are guaranteed to be seeing the same scratch disk location, since it's in one place for the whole production).

I understand though that you'd like the Auto Save location to work differently. I'll make sure to share this with the team.

[POwens]

Matt,

Ah - OK, understood.  I guess this behaviour has changed since I last worked on a similar setup 18 months ago?    Yes, it's great that the renders etc are truly shared, but I do think there's an argument that AutoSaves should be able to be directed somewhere off-system or local by each editor, for the single point of failure reasons I mentioned, 

[jasmine_alexandra_8736]

Listen, I'm running into a scratched disc issue,  I'm trying to change the scratch disk location in Photoshop from Macintosh HD to my external SSD, but the option is locked and won't let me uncheck the Macintosh HD drive. How can I unlock this option and set my external SSD as the new scratch disk location? My SSD has terabytes on it that has more than enough space and I was able to change it on the other Adobe programs, but I can't seem to do it with photoshop. Why won't it let me add my SSD card and uncheck Macintosh HD? 

[MyerPj]

Confusing thread. The OP seemed to put in a quite clear question, about autosaves, but then the next post seemed to be about scratch disks. Then a question came in on Photoshop! So, I'm following this thread to see where it goes.

FWIW: I would think that putting something like c:\My-Autosaves should stick in Production settings and be placed in each persons c: drive? That's as much as I know from the one man shop I have here. Cheers!

🙂

[POwens]

@jasmine_alexandra_8736 Wrong forum, this is the Premiere forum, not Photoshop.