Plugin Examination/Scan - Exclude Folder Location

[Pablo13]

I had to perform a clean installation of my MacOS and therefore re-install Performer Lite (11). Prior to doing this, I moved all my plugins onto an external SSD as part of my backup routine. I have yet to put them back onto my Macbook Pro as I had previously experienced an issue where an unidentified plugin was causing Performer Lite to permanently freeze after opening a project which contained the offending plugin(s). When this happened I always had to force PL to quit. I was never able to open/access the project.

So I would like to know if it is possible to copy the plugins back onto my Macbook into a folder which I can exclude from the examination/scan PL carries out when the application is opened?

Over time, I would then move each required plugin into a folder location that would be included in the examination/scan process and would then be able to identify which plugin had been causing the project freezing issue.

I appreciate I could do this by reintroducing each plugin by moving it directly from the SSD into a folder location that would be examined/scanned but in workflow terms, this requires the SSD to be inserted/removed over and over. I'm just wondering if I can make this task slightly less onerous if possible.

Or maybe there's another way to achieve what I want to do that I'm not aware of?

[bayswater]

The first thing that occurs to me is that if you did a new macOS installation, you would have removed files that plugins use. Rather than just move the plugins back into their original folders, you’d have to reinstall many of them.

Figuring our which plugin causes your problem: make a folder called something like “unused”, after the plugins are properly installed. Drag half of your plugins into that. See if your project works. If not, you know the problem is in the half that is left in place. Drag half of the plugins remaining in the unused folder, and try again. Repeat this a few times and you’ll have narrowed it down to one of two plugins (e.g. 8 steps will test 512 plugins).

[mikehalloran]

The basic answer to your question is No. Plug-ins must be in the correct folders for any app to access them. Being in the correct location triggers the verification process. There is no workaround.

You can re-run the installers as Bays suggests or install them manually. Since you have an unknown problem, I recommend using the installers —quite likely that, if the plugin is obsolete, so is the installer.

Otherwise, if copying manually, use the old 50/50 method. Copy half. If the project doesn't open, delete 50% of what you installed and try again and so on. If the project does open, try the other half and go from there.

Another way is to install everything. From the Startup screen, go to Settings and de-select the plug-ins you suspect (or all). After the [roject is open, you can re-enable them individually or in groups. After doing this, you will have the option of re-verifying immediately or the next time that PL starts.

[mikehalloran]

The puzzling thing is when a plug passes Verification but causes a project to freeze. That is unusual but can happen..

To see if the issue is a plug-in problem, start PL in Safe Mode by holding the Option key, then selecting Safe. When the project opens, select OK. This will disable all plug-ins. If the project still freezes, the issue is something else.

Screenshot 2024-02-07 at 10.30.54 AM.png (1.15 MiB) Viewed 558 times

Screenshot 2024-02-07 at 10.31.40 AM.png (117.89 KiB) Viewed 558 times

Quit without Save and restart PL. If you can now get the project open, you can right-click on individual plug-ins in the Mixer or Track windows and select None to disable them. If you do not Save before closing, everything will revert.

PL Mixer.png (189.52 KiB) Viewed 558 times

[Pablo13]

Thank you both, I'll give your suggestions a go. Your advice and detailed guidance is very much appreciated.

[mikehalloran]

Let me correct an oversight. While you can copy the plugs into their correct folders—and they will go through verification—this does not affect licensing.

The installers will install the support files in Library/Application Support that the licenses need for the plug-ins to work. Run those installers.

[Pablo13]

Let me correct an oversight. While you can copy the plugs into their correct folders—and they will go through verification—this does not affect licensing.

The installers will install the support files in Library/Application Support that the licenses need for the plug-ins to work. Run those installers.

Sure, thanks for that.

[Michael Canavan]

To add to this, the solution I've used forever backed up by other users etc. is to create new folders directly in your root/Library/Plug-Ins folder labeled Components (Disabled), VST (Disabled) etc. These folders can be used to drag plugins into from your VST, AU, VST 3 folders etc. and your DAW will not see them.

I have a copy of AudioFinder and they do this automaitcally, but in general I've done this for decades now as a way to troubleshoot which plugin is crashing DP etc. using the 50% method Mike mentioned.

[James Steele]

To add to this, the solution I've used forever backed up by other users etc. is to create new folders directly in your root/Library/Plug-Ins folder labeled Components (Disabled), VST (Disabled) etc. These folders can be used to drag plugins into from your VST, AU, VST 3 folders etc. and your DAW will not see them.

+1

[Pablo13]

To add to this, the solution I've used forever backed up by other users etc. is to create new folders directly in your root/Library/Plug-Ins folder labeled Components (Disabled), VST (Disabled) etc. These folders can be used to drag plugins into from your VST, AU, VST 3 folders etc. and your DAW will not see them.

I have a copy of AudioFinder and they do this automaitcally, but in general I've done this for decades now as a way to troubleshoot which plugin is crashing DP etc. using the 50% method Mike mentioned.

Thank you, this is very much what I was looking for in my OP.

All the responses have been helpful and informative for someone (like me) who is still on a learning curve. Thanks again for your input.