Piano One SE Plugin saying unvalidated in Gig Performer

Plugins
1

Hello, I just downloaded a trial version of Gig Performer and I am having issues with one of the free VST plugins I downloaded. It is the Piano One SE plugin found here:

I downloaded the 64 bit version and have it added to my VST folder but when Gig Performer scans for plugins that is the only one that fails. If I double click on the plugin in GP, it says “GP can’t load an unvalidated plugin.” I used the search function and found a couple threads related to this particular plugin but I didn’t see where it was mentioned as having issues validating in GP. Any ideas? Thanks.

2

When you delete the red entry for this plugin in the plugin manager window and do a rescan, what happens?

3

Is it possible you had previously downloaded the 32 bit version?

For what it’s worth, I thought I’d check it out so

  1. The installer is not code signed – so be very installing this in the first place :slight_smile:

    screenshot_649
    screenshot_649499×430 57.3 KB

  2. I did install it - however I did not specifically add it to an explicit folder. I ran GP and it scanned and picked it up

    screenshot_650
    screenshot_650484×514 56.1 KB

  3. I then inserted it and double-clicked to open the editor and it popped up with no problem.

    screenshot_651
    screenshot_6511309×801 206 KB

This is on a Windows 10 VM. So from GP’s side, there is no issue with this plugin.

4

Thank you very much for the response. I deleted it and tried re-installing it and for whatever reason it still fails for me when trying to load it in GP. During installation it is adding the .dll file to my VSTPlugins folder by default. I also tried adding it to a folder on my desktop and manually telling GP to scan that folder but it fails from there also. I’m using Windows 11 so not sure if it has to do with the OS as I see you were on Windows 10. I’ll keep playing around with it and see if I can get it to work somehow.

5

No problems installing, scanning, or loading the plugin here on Win 11.

89
89944×870 322 KB

6

Hmm. :thinking: When you ran the 64 bit installer did you just let it install the .dll to your VSTPlugins folder? Besides running the installer, did you take any other steps?

7

Nothing special, just installed to the default location, scanned and voila.
I’d say delete the vst file , re-download it, and try again. Make sure you remove it from the red list in GP before you re-install.

8

Yep, same here, nothing special.

I assume you have been able to download and install other plugins with no issues?

Do you have any kind of anti-virus program running that might be getting in the way?

9

Bruise, could you describe your computer? (Make/specs/etc.)

I had, what sounds like, a very similar issue with this (synth bagpipe) plugin on my two (I have a backup) Lenovo Thinkpad P16 Gen 2s, even though I was able to get working on the Dell Laptop:

10

Yes all the other plugins I have installed so far have worked with no issue (Arturia, Spitfire Labs, Valhalla Supermassive). Besides Windows Defender I don’t have any anti-virus. I went through the Windows Optimization guide before getting started and only use this laptop for GigPerformer.

11

I am using a Dell Latitude 5401, 512 GB SSD, Intel Core i7-9850H, 16 GB RAM, WIN 11 PRO.

12

Very strange - but given that all your other plugins are working and given that others here who have tried that plugin have it working as well, it is most likely something to do with your environment, thought what that might be, I don’t know.

Maybe one of the files just got corrupted

13

Maybe you can use the plugin checker in GP. It’s official use is for determining whether a dll/vst is 64 bit or 32 bit, but maybe it also shows other errors, like missing runtime libraries for visual c++ or something like that.

Another way to accomplish this check could be c:\windows\system32\regsvr32.exe <path to the dll/vst>. If it just reports that an entry point is missing (you can ignore this error), then Windows is capable of loading the dll, so probably no runtime libraries are missing.

(The entry-point error comes from the fact that regsvr32 is normally used for registering com-objects and vsts are no com-objects. In the test above, I’m just abusing regsvr32 to see if the dll itself loads properly.)

14

Thanks. I tried the regsvr32.exe process you mentioned and got the following message:

"The module “C\ProgramFiles\Vstplugins\Neo_Piano\Neo_Piano_x64.dll failed to load. Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent .DLL files. The specified module could not be found.”

I also found the following comment from a youtube video where someone also had an issue trying to load this plugin in their DAW:

The plugin was successfully installed on Windows 11 and my DAW. At first try, the DAW gave me an error when attempting to load the plugin: com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: VST plug-in plugins\Neo_Piano_x64.dll could not be loaded because a library it depends on is missing. The Neo_Piano_x64.dll plugin requires and old version of the Microsoft Visual C++ runtime library. Once installed, it worked ok

So I am guessing maybe I have a similar issue where it is missing an old version of C++ runtime library.

15

You can get them here:

16

You forgot the ‘:’ and a space (or it got lost in translation).

Try C:\Program Files\Vstplugins\Neo_Piano\Neo_Piano_x64.dll

That’s exactly what I think that’s happening.

17

Thanks! I will check later and see about downloading the versions I don’t have and see if that resolves the issue.

18

Yeah during my typing in my message I left out the “:”. But I did include it when running the cmd prompt. Thanks for the idea about the C++ runtime. I’m hoping that will be the ticket.

19

Thank you to everyone who replied and for your assistance! I turned out being the Microsoft C++ 2010 Redistributable that was needed to run this plugin. GP now loads it without issue.

1 Like
20

I wouldnt be surprised if that’s the same issue had with SIM-BP (electronic bagpipe) plugin