There are free vst and aax (Pro Tools) plugins installed as part of 360 Spatial Workstation. These are greyed-out (as if requiring a license), or invisible (VSTs e.g. in Ableton Live). If you login as an administrator they appear with no issues.
This is not acceptable, because in a large music studio, we naturally do not let guests, artists, students, and so on, install programs or other admin tasks.
The program should have all the permissions necessary, to change almost any system component, and not require system-level restrictions in the actual plugins.
So the other parts of "360 Spatial Workstation" also known as FB360 now in collaboration with a team at Facebook work fine, just not the plugins in DAW programs.
It seems if you are not the administrator while wanting to use any of the Digital Audio Workstation compents of this program, the DAW cannot find the plug-ins on the system, and refues to acknowledge the "free" license (for example the Pro Tools .aax plugins).
The systems are OSX 10.11, facing the same issue with all non-admin users whether local or ldap users.
I am used to solving minor problems in similar programs with relatively-simple ****Bash* scripts or by tweaking unix-style config files or plists in
~/Library/Application Support/$Application as well as
~/Library/Preferences and the local, system-wide files***, similarly, but there are no files here to modify.
I've tried to post questions at The developers' help desk but can't seem to login or create an account.
I have also tried opening the permissions wide to 0777 on all of the components inside the Applications package, as well as the individual plugins. I also wanted to force the components to run suid as an administrator, but so far this has not worked, but this is the basis of tricks for unix & linux (on ***osx*, here)** that I am hoping to most get some tips on. It seems like the way Pro Tools plug-ins--but also the VST plugins--are implemented, contain within their packages also levels of access restriction, which is not normal for these plug-ins in my experience.
I also tried using the
sudo system to allow specific users to access the plugins, and this made no difference.