Go Back   Cockos Incorporated Forums > REAPER Forums > REAPER for macOS

Reply
 
Thread Tools Display Modes
Old 07-26-2016, 08:19 AM   #1
Stroudy
Human being with feelings
 
Stroudy's Avatar
 
Join Date: Jul 2014
Location: London
Posts: 733
Default Big help needed! Reaper is not writing to Application Support

Reaper is creating it's support files in /Applications ...not... ~/Library/Application Support

I think I managed to mess up my permissions (yes I've tried repair permissions). Or something, hell don't know.

Any thoughts are much appreciated
Stroudy is offline   Reply With Quote
Old 07-26-2016, 08:40 AM   #2
Stroudy
Human being with feelings
 
Stroudy's Avatar
 
Join Date: Jul 2014
Location: London
Posts: 733
Default

Seems to be working now.

I set permission to Application Support as Owner and Group to R/W/E

Not sure if that's the right way to do things
Stroudy is offline   Reply With Quote
Old 04-06-2022, 08:23 PM   #3
moon_meat
Human being with feelings
 
Join Date: Jan 2022
Posts: 3
Default

I had this exact problem today after running the app from command line with sudo.

In case anyone else runs into this problem in MacOS where REAPER starts ignoring the "~/Library/Application Support/REAPER" directory and instead writes to the "Application" folder...

This worked for me:

#Open a terminal

cd ~/Library/Application\ Support/REAPER
ls -ltr


#The owner of some files in this directory had become root, which didn't seem right.


chown -R yourusername:staff *


#Fixed!
moon_meat is offline   Reply With Quote
Old 05-04-2022, 08:44 AM   #4
cbg
Human being with feelings
 
Join Date: Oct 2019
Posts: 14
Default

Quote:
Originally Posted by moon_meat View Post
I had this exact problem today after running the app from command line with sudo.

In case anyone else runs into this problem in MacOS where REAPER starts ignoring the "~/Library/Application Support/REAPER" directory and instead writes to the "Application" folder...

This worked for me:

#Open a terminal

cd ~/Library/Application\ Support/REAPER
ls -ltr


#The owner of some files in this directory had become root, which didn't seem right.


chown -R yourusername:staff *


#Fixed!
Most of the issues on MacOs can be solved by restarting mac and load into recovery mode to start the harddisk utility and check filesystem.
It will correct the permissions and of course check the fs.
cbg is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 01:58 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.