I am attempting to evaluate APL Virtuoso. I installed the program, which seemed to be straight forward. The VST3 plugin installed in the appropriate folder.
I opened Gig Performer and scanned for new plugins.
As you can see, the plugin failed. It uses iLok activation and it shows as activated in iLok. I removed the folder containing the plugin from its installed location and rescanned. All was good. I then copied the plugin back to Common Files and rescanned. Once again, the plugin failed in the scan.
I opened Studio One. The plugin scanned and was not blocked. I opened a project, inserted Virtuoso, and it opened correctly. Once again, it failed in Gig Performer.
I don’t think it is the type of plugin. Neumann RIME is also a multichannel headphone studio emulation plugin. It works correctly in Gig Performer.
Perhaps you can give me some advice as to how I might be able to use the plugin in your program. I will also be contacting APL and will forward any information which might be helpful.
We have seen issues in the last with iLok where the plugin needs to be authorized with iLok before it will validate but it sounds like you have already been able to authorize it and it is actually working (not just validated) in another host.
I don’t know any reason why it shouldn’t therefore validate with Gig Performer unless you tried to validate it BEFORE it was authorized.
If that’s the case, try just removing the entry from the GP Plugin Manager and then rescan
I removed the plugin from the Plugin Manager and rescanned. That didn’t work. Next, I removed the plugin from the Plugin Manager and the vst3 file from the default folder and rescanned. That was good. I put the plugin back in the default location, rescanned and it failed once again.
Is there a way to flush the Plugin Manager and try again or is that a waste of time?
Was able to get the plugin operational in Gig Performer. For future reference, first I rescanned everything. Virtuoso was still not recognized. I then removed the plugin folder from the Common Files > VST3 folder, copied the Virtuoso vst3 file (without the enclosing folder) to the VST3 folder and Gig Performer found it. Then moved the entire Virtuoso folder back VST3 folder and it was found and is functional.
FYI, the Virtuoso VST3 folder is called Virtuoso.vst3. The only other folder with .vst3 appended to the name is Neumann RIME, which is a similar product. Cheers
I recall that some VST3 plugins created with the Steinberg sdk create a ‘content’ folder which is actually a link/junction. Lots of plugin hosts (on Windows that is) do not handle that very well. You can also say that the Windows implementation of links/junctions leaves much to be desired.
The file path shown in the picture surely has the format that I associate with this issue.
Update: I installed it myself, but the file structure is just normal folders.
Another reason could be that the file itself was blocked (mark of the web) but the installer seems to take care of that.
Well, this probably isn’t the solution, but on my system, only Virtuoso and Neumann RIME files were enclosed in folders which were .vst3. Wonder if it is being seen as a faulty file. When I tried to copy the file itself into the VST3 folder, the system told me that there was already a file by that name. There was no file, but the folder with the same name as the file.
