Hello all, new to gig performer and loving it so far.
Has anyone had any issues with the Orilriver vst and vst3 plugins? They keep coming up in my failed to scan (red) plugin window, and I have removed them several times and tried rescanning to no avail. They are 64 bit to my knowledge.
The EZ drummer demo and Vital also won’t scan for some reason - everything else is fine. I’m on a macbookpro with m2 processor 32 gig of ram.
Any suggestions ?
Thank you all.
Jef
Do they all work correctly in a DAW? Orilriver hasn’t been updated in 8 years (from what I can see).
Hello rank13, I’m not sure, to be honest - I only have my MacBook with me and had downloaded Gig Performer and wanted to try out some things, so I downloaded some free software to start building some racks and familiarize myself. My music desktop is a PC, and I haven’t had an opportunity to try loading it (Orilriver). I mostly use Cubase as my main DAW, and I will try that tomorrow when I get home. I hadn’t noticed the software hadn’t been updated in some time. That may be the issue, but it probably wouldn’t explain why Vital or EZ Drummer also is not loading. ?
Oril River worked OK for me.
It was also used as an example for this chapter in the user manual: How to control multiple parameters with a single widget?
Two things to consider:
Once in the Plugin Manager, you can check whether it is 64-bit on right-click on Windows.
EDIT:
You are on a Mac? Not sure if there are recent builds for a Mac. The plugin has not been updated for years.
Thanks for the reply, npudar - I appreciate you checking in and offering advice. I double-checked the path on my MacBook, and it is correct. I’m not quite sure how to check for 64bit on the macbook.
Im also having some issues with EZ Drummer Demo, Vital, and Zampler Rx not being recognized. Which is odd because Surge, and a few of the free U-he synths installed and GP scanned them no problem, as well as some other effects plugins.
I’ll double check the installs - I would love to have Vital working, but if not possible, I’ll live. 
thank you again
As far as I can see searching the forum it works OK.
What is the version of your macOS?
I’ll try Vital during the day on my macOS.
The Mac OS is Sequoia 15.5.
Vital works in standalone, and I can see it is in the library/plugins folders in both VST and VST3 subfolders - it shows up in the plugin manager in Gig Performer as a red failed plugin at the bottom in both instances (vst, vst3). ? I tried removing and rescanning. I must be doing something wrong. In any event, I’m loving GP - it IS THE SOLUTION I was looking for regarding soft synths and playback under one hood without loading a DAW.
I’m using Gig Performer on the latest macOS Tahoe.
Vital is working normally.
–
Oril River does not work. I suspect because it doesn’t have an Apple Silicon build (and I don’t want to use Rosetta).
Anyway, there are lots of great free reverbs, you’ll definitely find something to your liking.
Thanks for checking npudar and getting back to me. Maybe I should update to Tahoe and try that.
If you go to the actual location of that’s plugin library (typically under the plugin name / Contents/MacOs
using a terminal window, you can then type
file filename (replace filename with the actual name of that plugin) and it will tell you what kind of library it is
For example, if I do this for one of my plugins (Korg Wavestation) I get this where it shows that the library supports both Intel and ARM but 64-bit only
dhj@Office-Mac VST3 % file WAVESTATION.vst3/Contents/MacOS/WAVESTATION
WAVESTATION.vst3/Contents/MacOS/WAVESTATION: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit bundle x86_64] [arm64:Mach-O 64-bit bundle arm64]
WAVESTATION.vst3/Contents/MacOS/WAVESTATION (for architecture x86_64): Mach-O 64-bit bundle x86_64
WAVESTATION.vst3/Contents/MacOS/WAVESTATION (for architecture arm64): Mach-O 64-bit bundle arm64
Be careful. I use Tahoe to test GP.
But I wouldn’t use it in a live situation
Good advice - let me ask you, in your case is GP loading an AU version of teh plugin or the vst version ? I noticed that when I scanned - another app “zampler” was loaded in an au version and works fine but the vst version did not load and was flagged as a failed plugin. On Vital, I can see there is only a VST version on my machine in and not an AU version … I am wondering if that may be the issue ?
Per my screenshot, you can see VST and VST3 versions.
I don’t use AU versions, as VST versions are tested against many DAWs.
Ah yes, sorry I overlooked that. Yeah not quite sure Vital isnt coming up in GP here then.
You did all the necessary steps, right?
Created an account at the developer, downloaded the installer, etc. ?
Yes, I even uninstalled Vital, deleted the standalone, and the plugins in the vst folders - then reinstalled it. GP still wont scan it for some reason. It keeps coming up as a red failed plugin. Very odd.
OK … I had tried closing and re-opening GP, thinking it might rescan the plugs - it did, but Vital was still flagged. I rescanned the failed plugins after I had reinstalled Vital… and now it works! That is great - Thank you npudar and everyone else for offering solid advice to help out - it just took a bit of patience on my end. Thanks - I appreciate it.
Very cool!
