Cubase Write Permission Error After Mac Migration

Cubase
1

Hello everyone,

I’ve recently migrated my Cubase files to a new Mac and am encountering a persistent and critical write permission error whenever I try to create or save a project (or even select tracks), which prevents the auto-save folder from being created.

The exact error message is:

“Auto save folder cannot be created. There might be a problem of write permission.”

I have exhausted the standard fixes, and the issue remains. I need help finding a less common solution, possibly related to user profiles or specific OS configuration.

:white_check_mark: What I Have Tried (All Failed):

  1. Terminal Fix (Recursive Ownership):

    • I ran sudo chown -R $(whoami) /path/to/project/folder on the entire project drive/folder to ensure my current user owns all files.

    • I also ran the aggressive sudo chown -R $(id -u) /path/to/project/folder using my explicit User ID.

  2. Full Disk Access:

    • I confirmed that Cubase has been granted Full Disk Access under macOS Privacy & Security settings.

  3. Cubase Preferences Reset:

    • I launched Cubase in Safe Mode and Deleted program preferences.

  4. Standard Permissions Check:

    • I checked the permissions via Get Info for the project folder; my user account has “Read & Write” permissions.

:red_question_mark: My Questions

Any advanced troubleshooting steps or insight into why the auto-save creation is failing after these comprehensive fixes would be greatly appreciated

Thank you!

2

Is this on an external drive or the internal one? And is your account an Admin account?

You could try creating a new admin user.

3

Hello,
Creating a new user can’t resolve the issue.
YEP, it’s an external drive.
thanks

4

In the Finder, select the icon for the drive, click Get info, click on the padlock, enter your admin password, and make sure that “Ignore ownership on this volume” is checked.

I would then select your user, select “read & write” and then click on the circle down arrow and select “apply enclosed to enclosed items”

1 Like
5

It worked!
I already did all the steps mentioned above, with the exception of
“Then click on the circle down arrow and select ‘apply enclosed to enclosed items’.”

It seems the chmod command line hasn’t handled the recursive ownership change for all subfolders…

Nevertheless, thank you so much; it was truly driving me crazy.

1 Like