Jump to content

hotkeyz

Member
  • Posts

    7
  • Joined

  • Last visited

hotkeyz's Achievements

Newbie

Newbie (1/14)

0

Reputation

1

Community Answers

  1. 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.
  2. 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 ...
  3. Read and write privileges are active on the both the 'Users' folder and my own user folder.
  4. 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."
  5. 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 ...
×
×
  • Create New...