hotkeyz Posted October 14, 2021 Share Posted October 14, 2021 I've just tried using Logic Pro for the first time since the upgrade to Mac OS Big Sur. I'm running Logic Pro 10.6.3 on an iMac running Big Sur 11.6. When I made some adjustments in a project and tried to save, a window popped up saying "The document "Ra Ra Ra" could not be saved. You don't have permission." However, the file already has 'read & write permissions (I am the administrator) - so I don't understand why there is an issue. Can anyone suggest the cause? And a solution? Thanks ... Quote Link to comment Share on other sites More sharing options...
triplets Posted October 14, 2021 Share Posted October 14, 2021 Where is that project saved? Quote Link to comment Share on other sites More sharing options...
fisherking Posted October 14, 2021 Share Posted October 14, 2021 security! gets more complicated all the time (sadly, it needs to). check system preferences>security & privacy>privacy. make sure logic is checked under 'files & folders'; should show desktop, documents, etc (you'll need to unlock this window first, lower left, with your mac password)... Quote Link to comment Share on other sites More sharing options...
hotkeyz Posted October 15, 2021 Author Share Posted October 15, 2021 Where is that project saved? Macintosh HD > Users > User Folder > > > etc Quote Link to comment Share on other sites More sharing options...
hotkeyz Posted October 15, 2021 Author Share Posted October 15, 2021 security! gets more complicated all the time (sadly, it needs to). check system preferences>security & privacy>privacy. make sure logic is checked under 'files & folders'; should show desktop, documents, etc (you'll need to unlock this window first, lower left, with your mac password)... Yes. All of the options under 'Files and Folders' are selected. However, there is an option above 'Files and Folders' called 'Full Disk Access'. Should I select Logic Pro and the Native Instrument apps? It does say "allow the apps below to access ... certain administrative settings for all users on this Mac." Quote Link to comment Share on other sites More sharing options...
marcperi Posted October 15, 2021 Share Posted October 15, 2021 Have you tried to select your project in finder, hit Command+I and add a full permission in read and write to all users? Quote Link to comment Share on other sites More sharing options...
fisherking Posted October 15, 2021 Share Posted October 15, 2021 make sure your "User Folder" has (command-I) 'read and write' privileges for you (the user)... Quote Link to comment Share on other sites More sharing options...
hotkeyz Posted October 16, 2021 Author Share Posted October 16, 2021 Have you tried to select your project in finder, hit Command+I and add a full permission in read and write to all users? Yes. And restarted the Mac afterwards. Quote Link to comment Share on other sites More sharing options...
hotkeyz Posted October 16, 2021 Author Share Posted October 16, 2021 make sure your "User Folder" has (command-I) 'read and write' privileges for you (the user)... Read and write privileges are active on the both the 'Users' folder and my own user folder. Quote Link to comment Share on other sites More sharing options...
hotkeyz Posted October 16, 2021 Author Share Posted October 16, 2021 I've just completed a series of tests as follows - 1. I created a new project from my orchestration master, copied something across from the original project, and saved successfully. I closed and reopened the test, and made another edit successfully before saving and closing. 2. With the original project, I made an edit and selected 'save as' rather than 'save.' This saved successfully, and I was able to reopen, edit, and save normally. I was also able to do this using the 'save a copy as' option as well. I'm not an expert on Logic or Mac OS, but it leaves me thinking the problem is with the original project files. Perhaps a backwards compatibility issue. The original project was created in June 2017 ... Quote Link to comment Share on other sites More sharing options...
fisherking Posted October 16, 2021 Share Posted October 16, 2021 I've just completed a series of tests as follows - 1. I created a new project from my orchestration master, copied something across from the original project, and saved successfully. I closed and reopened the test, and made another edit successfully before saving and closing. 2. With the original project, I made an edit and selected 'save as' rather than 'save.' This saved successfully, and I was able to reopen, edit, and save normally. I was also able to do this using the 'save a copy as' option as well. I'm not an expert on Logic or Mac OS, but it leaves me thinking the problem is with the original project files. Perhaps a backwards compatibility issue. The original project was created in June 2017 ... probably the project. 2017 files should not be a problem in general. anyway, glad you have it sorted! Quote Link to comment Share on other sites More sharing options...
Solution hotkeyz Posted October 16, 2021 Author Solution Share Posted October 16, 2021 I've just completed a series of tests as follows - 1. I created a new project from my orchestration master, copied something across from the original project, and saved successfully. I closed and reopened the test, and made another edit successfully before saving and closing. 2. With the original project, I made an edit and selected 'save as' rather than 'save.' This saved successfully, and I was able to reopen, edit, and save normally. I was also able to do this using the 'save a copy as' option as well. I'm not an expert on Logic or Mac OS, but it leaves me thinking the problem is with the original project files. Perhaps a backwards compatibility issue. The original project was created in June 2017 ... probably the project. 2017 files should not be a problem in general. anyway, glad you have it sorted! So it seems ... but I'd rather not have to do that with every logic project I have. Quote Link to comment Share on other sites More sharing options...
fisherking Posted October 16, 2021 Share Posted October 16, 2021 probably the project. 2017 files should not be a problem in general. anyway, glad you have it sorted! So it seems ... but I'd rather not have to do that with every logic project I have. depending on what version of logic you did those projects in, you may have to save in the newer logic format; otherwise, are you having the issue with other projects? or just the one? seriously, if it's a problem with multiple files.. cross that bridge when you come to it. ie, if you open one of those projects, save it, then continue to work (and save). no need to open all of them and resave all of them 'at once'... Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.