Hi,
I’m observing that my Cubase 12.0.7 (on Win 10) won’t find my plugin Forager_1.4.0.dll.
It finds Forager_1.2.0.dll, which is right next to it in the same location ( C:\Program Files\VSTPlugIns) just fine.
Does anyone know what could cause this?
Hi @sj11
Are you refering to this plugin (https://harvestplugins.com/forager/)?
Some relevant information from the manufacturer’s website (https://harvestplugins.com/support/):
Is Forager M1 Compatible?
As of right now, Forager is not natively compatible with M1. Although it is possible to run Forager on an M1 Mac, it requires a host DAW that itself is not M1 native, and is running in “Rosetta Mode”.
Is Forager VST2 or VST3?
Currently Forager is only available as VST2
Please check if the plug-in is on the blocklist on the VST Plug-in Manager Window:
Hi,
Cubase 12 supports VST 2.4 and newer 64-bit plug-ins only. Does the plug-in meet the requirements, please?
Hi.
It’s not on the blocklist, it’s not seen at all. That’s the mystery.
Hi again,
More information -
I redownloaded and installed the latest Forager (v1.4.0) from the Harvest Plugins site.
It installed to C:\Program Files\VSTPlugIns as Forager.dll.
This was recognized by Cubase 12. (Good!)
Since I had a previous version also installed and recognized (Forager_1.2.0.dll), I wanted to rename the latest to Forager_1.4.0.dll. So, I did so, and after that Cubase did not see it at all.
I renamed it back to simply Forager.dll.and now Cubase sees it again.
Why would the file name matter?
I thought Cubase would simply go thru the directory and recognize what’s there, whether renamed or not. (?)
P.S. Implicit in the above - yes, the plugin meets the requirements.
So the question now is about renaming a .dll file of an installed (and operating) 64-bit VST 2.4 plugin …
