Most music programs look in /usr/lib/vst3 first for a plugin. If the plugin isn't there, then the program will next look in your home folder's vst3 directory.
So, you can put the plugin in either location, and your programs wil find it.
But there are two things you should know:
First, if someone else has an account on your computer, and needs to use this plugin, then that someone won't be able to find the plugin if you put it in your own home folder. After all, that other user can't get access to anything in your home folder (unless you specifically change permissions to allow it). Both of you will be able to use the plugin only if you put it in /usr/lib/vst3.
Secondly, any program you run can modify that plugin unless you specifically change the permission to not allow yourself to modify (ie, write) that plugin. That's a security risk. Furthermore, lots of times when you zip and unzip downloaded plugins, the execute "flag" may get turned off. In this case, Linux will not allow your plugin to run. You will need to enable the execute flag. So, you need to be aware that just copying a file to your home's vst3 folder doesn't suffice.You need to change "file flags". Most desktops allow you to do this by clicking the right mouse button over the file's icon to present its pop-up menu. In that menu, you should see a "Properties" menu item. Selecting this should present a notebook dialog. On the Notebook's "Permissions" page, there should be settings for "Group", "Others", and your login name. You can set these to "read-only". There should also be a checkbox you can check for "execute".
So, you can put the plugin in either location, and your programs wil find it.
But there are two things you should know:
First, if someone else has an account on your computer, and needs to use this plugin, then that someone won't be able to find the plugin if you put it in your own home folder. After all, that other user can't get access to anything in your home folder (unless you specifically change permissions to allow it). Both of you will be able to use the plugin only if you put it in /usr/lib/vst3.
Secondly, any program you run can modify that plugin unless you specifically change the permission to not allow yourself to modify (ie, write) that plugin. That's a security risk. Furthermore, lots of times when you zip and unzip downloaded plugins, the execute "flag" may get turned off. In this case, Linux will not allow your plugin to run. You will need to enable the execute flag. So, you need to be aware that just copying a file to your home's vst3 folder doesn't suffice.You need to change "file flags". Most desktops allow you to do this by clicking the right mouse button over the file's icon to present its pop-up menu. In that menu, you should see a "Properties" menu item. Selecting this should present a notebook dialog. On the Notebook's "Permissions" page, there should be settings for "Group", "Others", and your login name. You can set these to "read-only". There should also be a checkbox you can check for "execute".
Statistics: Posted by j_e_g — Sun Aug 25, 2024 2:52 am