Stoobysnax Posted April 9 Share Posted April 9 I use plugin alliance SSL 9000J a lot in Logic. It comes with a long list of presets included. I want to delete these, so I'm going into their associated folder in Library / Audio / Presets / PA... etc.. .both User / Library and system Library. Delete the presets, and they are gone inside an open SSL plugin immediately. But when I open a new instance of the SSL plugin, they repopulate and put the presets back into those folders. Any way to have this not happen? Quote Link to comment Share on other sites More sharing options...
des99 Posted April 9 Share Posted April 9 Let me check here.. edit: Ok, yes, I see this behaviour here... weird! Quote Link to comment Share on other sites More sharing options...
Stoobysnax Posted April 9 Author Share Posted April 9 Right? Something when opening a new instance of the plugin automatically populates the presets again. Quote Link to comment Share on other sites More sharing options...
des99 Posted April 9 Share Posted April 9 I'll have a nose around and see what other PA plugins behave like this, and whether this is something the plugin is doing, or Logic etc... Quote Link to comment Share on other sites More sharing options...
Sir Hannes Posted April 10 Share Posted April 10 14 hours ago, Stoobysnax said: I use plugin alliance SSL 9000J a lot in Logic. It comes with a long list of presets included. I want to delete these, so I'm going into their associated folder in Library / Audio / Presets / PA... etc.. .both User / Library and system Library. Delete the presets, and they are gone inside an open SSL plugin immediately. But when I open a new instance of the SSL plugin, they repopulate and put the presets back into those folders. Any way to have this not happen? Unfortunately this is due to the code inside. You can't change this behavior, only the programmers might. I was in contact about this some time ago. What you might want to try is VST format. Quote Link to comment Share on other sites More sharing options...
polanoid Posted April 10 Share Posted April 10 5 hours ago, Sir Hannes said: Unfortunately this is due to the code inside. You can't change this behavior, only the programmers might. I was in contact about this some time ago. What you might want to try is VST format. Seems like those programmers really want you to use their factory presets 😉 1 1 Quote Link to comment Share on other sites More sharing options...
wonshu Posted April 10 Share Posted April 10 You could change the permissions on the preset folder to not allow any editing by anyone... That's how I used to prevent Google Chrome from updating automatically (many many years ago, I wouldn't do this today anymore)... Quote Link to comment Share on other sites More sharing options...
Stoobysnax Posted April 10 Author Share Posted April 10 1 minute ago, wonshu said: You could change the permissions on the preset folder to not allow any editing by anyone... That's how I used to prevent Google Chrome from updating automatically (many many years ago, I wouldn't do this today anymore)... Right, but then, am I not able to save my own presets in there? Quote Link to comment Share on other sites More sharing options...
wonshu Posted April 10 Share Posted April 10 Yes... so yeah... not a viable solution... Quote Link to comment Share on other sites More sharing options...
Stoobysnax Posted April 10 Author Share Posted April 10 Actually, I think the user presets are in a different folder so may work. How would I do this? 3 minutes ago, wonshu said: Yes... so yeah... not a viable solution... Quote Link to comment Share on other sites More sharing options...
wonshu Posted April 10 Share Posted April 10 CAUTION: This can seriously damage your system if you don't escape the spaces in the paths correctly!! If you don't understand this, please learn what all this means before trying it! I warned you. Please only do this if you are comfortable with the command line. Also: the plugin may crash if it is not allowed to write to that directory! First off: terminal must have full disk access for this to work (Security & Privacy control panel). Before doing this, navigate in the Terminal to the folder that contains the preset folder and do a "ls -la" - this will list everything in that directory and it will show you the current owner and group of those preset directories. Write them down somewhere so that you can revert back in case something goes wrong. So, make sure you have a Terminal window open and a Finder window open with the folder that contains the preset folder, align the windows so that you can drag the folder from the Finder over to the terminal. type (or copy paste) this into the terminal (there is a blank space after the word staff !!!): sudo chown root:staff Then drag the folder that you want to remove access to from the Finder window onto the terminal window. Hit return. Now the terminal will ask you for your computer password, type it in, the cursor will NOT move while typing. Press enter when done. If this doesn't work you could make it even more restrictive by using sudo chown root:wheel (drag the preset folder here) To revert this back to what it was use the owner and group values you wrote down earlier. sudo chown owner:group (drag the preset folder here) Quote Link to comment Share on other sites More sharing options...
polanoid Posted April 10 Share Posted April 10 4 minutes ago, wonshu said: sudo chown root:staff Wouldn't sudo chmod a-w work as well (no need to write anything down in that case)? Quote Link to comment Share on other sites More sharing options...
wonshu Posted April 10 Share Posted April 10 Yeah, absolutely maybe... 🙂 I had to go full blast back then to stop Google Keystone from removing and re-adding its folder... 1 Quote Link to comment Share on other sites More sharing options...
wonshu Posted April 10 Share Posted April 10 Now I remember - I think I had used sudo chown 000 back then... It adds such a nice "Do Not Enter" symbol to the folder... 🙂 Quote Link to comment Share on other sites More sharing options...
polanoid Posted April 10 Share Posted April 10 Indeed it does! Cool! 😉 1 Quote Link to comment Share on other sites More sharing options...
Sir Hannes Posted April 11 Share Posted April 11 (edited) What I am doing wrong if terminal has full disk access, the PlugInAlliance folder is set to drwxr-xr-x@ myusername staff, and the Alpha Compressor folder to -rw-r--r--@ myusername staff, but terminal says still zsh: permission denied. Edited April 11 by Sir Hannes Quote Link to comment Share on other sites More sharing options...
wonshu Posted April 11 Share Posted April 11 Go to System Settings -> privacy + Security -> Full Disk Access Click the + sign, enter your password. Press CMD+SHIFT+PERIOD(.) - this will show invisible files... Browse to Macintosh HD/bin/zsh Select it and click ok. Quote Link to comment Share on other sites More sharing options...
polanoid Posted April 11 Share Posted April 11 34 minutes ago, Sir Hannes said: and the Alpha Compressor folder to -rw-r--r--@ myusername staff If you want to navigate into a folder, its "executable" bit (x) needs to be set, so the mode must at least be drwxr--r-- (I wonder why there's no "d" at the start in your case as "d" means "directory" == folder). Quote Link to comment Share on other sites More sharing options...
Sir Hannes Posted April 12 Share Posted April 12 Thank you both! I will try it out as soon as possible. A neat hack, very useful 🙂 @polanoid The "d" is there on the folder, you quoted the AU file, which is no directory, no? Quote Link to comment Share on other sites More sharing options...
polanoid Posted April 12 Share Posted April 12 11 hours ago, Sir Hannes said: @polanoid The "d" is there on the folder, you quoted the AU file, which is no directory, no? You wrote "and the Alpha Compressor folder to -rw-r--r--@" so I assumed it was, well, a folder 😉 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.