autosave doesn't seem to be working when set to an exfat drive

Report · Aug 12, 2023

Just noticed this... Just prepping a project for a client and the media drive she'd purchased was formatted exfat... I set up projects to save to a folder on my startup drive (macstudio ventura Premiere 2023) in a folder automatically mirrored on dropbox and my autosave folder is on the exfat drive... I'm about to return the drive to the client and went to check that the latest project file was saved in the autosave folder on the media drive and there was no autosave folder. Doublechecked other projects I've been working on with media drives formatted macosextended and autosave is working as expected...

I doublechecked the project settings: scratch disks and the autosave location is on the exfat drive in a folder called "Premiere stuff" which is the default location I use on all my media drives...

Gotta say I've had a few issues with exfat formatted drives so I usually avoid it... I'll make sure we have everything backed up, and then reformat the drive if it's necessary... Just wondering if there's something else that's causing the issue.

Thanks as always

Report · Aug 13, 2023

I presume you have tried chaning the scratch autosave to another drive and changing it back again?
I presume there are no dodgy characters in path? In project name? MacOSExtended lets you create folders with slashes "/" in them for example, which wouldn't work in exFAT.

Report · Aug 13, 2023

there are no dodgy characters anywhere in my professional life.... Years ago I learned using "reserved" characters in a folder or file name was a recipe for disaster...

Will try changing the autosave to another location and back... just tried it and... just tried resetting the autosave folder to a apfs ssd drive... and still no autosave folder... So must be an issue with the project... Will try copying everything to a new project and post back... Thanks Mike...

Report · Aug 13, 2023

Auto-save is not working on my system with Premiere 23.5. Not working for new projects and for preexisting projects. Logged in as a different user on my macstudio. I have never launched Premiere 23 with this user so I don't think this could be an issue with corrupted preferences, but when I have some time, I'll dig in to this further... I suggest everyone check to make sure your autosaves are working. When I have a few minutes I'll revert to 23.4 and if it's working there, I'll try resetting preferences and if that doesn't help, I'll post a bug report. Just checked a project I've been working on almost every day, and the autosaves had stopped on August 7th, but they resumed today..... Weird. Will double check the project with the exfat media drive right now and post back...

Report · Aug 13, 2023

so still no luck with the exfat project. when I go to check permissions on the drive using get info there's no way to adjust "sharing and permissions." just see a message that I have "custom access."

Gonna revert to Premiere 23.4 later today after a zoom with a client. It's Sunday and there's no rest for the weary or the wicked... Not sure which category I belong in...

Report · Aug 13, 2023

Updated to Premire 23.6 (cause, why not?). there's definitely something weird going on... Autosave was not working, so I created a new project, imported the old project and autosave does now seem to be working properly and autosaves are appearing on the folder on the exfat media drive. However, previously when I quite premiere, the saved project would appear in the autosave folder as well as where I was saving it on a folder on my startup drive which is automatically mirrored on my dropbox. Now, that's not happening... I do have "Auto Save also saves the current project (s)" enabled in the preferences: autosave... Not a big deal, but I did like the fact that if I took my media drive, it automatically had the latest version of the project saved to it... If anyone understands what's going on, would appreciate the insight, but can't emphasize enough that it's crucial to check your autosave folder regularly to make sure the autosave function is behaving properly...