Quote:
Originally Posted by tubbs
Reaper wasn't finding the Valhalla reverb plugin so i added the file where it's located (see attachment) to the Reaper VST search and now it's caught in an endless VST scanning process and i have to press "ok" for the "bad image" errors i'm getting innumerable times but it never finishes scanning so it never loads therefore i can't remove that file from the search.
i tried uninstalling and reinstalling but the new install remembered the file i had inputed and the problem began all over again.
please help.
|
Did you install it with the factory install .msi or .exe to one directory and then manually move it, suggesting a win reg error, as some plugins check to see if they have been activated or registered in win upon first access of the .dll file, or have you possibly installed via a cracked install package, just to try it out before you buy it, and have a buggy version?
Because the VST format is a Steinberg thing, alot of installers default to
c:\Program Files\Steinberg\VstPlugins\ (For x64)
c:\Program Files (x86)\Steinberg\VstPlugins\ (For x32)
....hence my 1st suggestion...I have had trouble with some plugins this way,
(Sylenth). If you still can't figure it out, try:
1. uninstalling via control panel / add/remove programs,
2. re-run the installer, making sure it points to your c:\VSTPlugins folder,
3. ONLY install the VST2. Then run REAPER.
If the problem persists, repeat steps 1 & 2 and then do step 3b:
3b: ONLY install the VST3 Then run REAPER.
If the problem still persists, repeat steps 1& 2 and then do step 3c:
3c: ONLY install VST3, but install it to the default folder:
c:\Users\XXXX\Program Files\Common Files\VST3\ (For x64)
c:\Users\XXXX\Program Files (x86)\Common Files\VST3\ (For x32)
Alternatively:
1. Check with Valhalla for an update or patch, (Sure you've done),
2. Check Google for an incompatibility issue with any newly installed software or hardware and the Valhalla plug.
3. If you are using the 32 bit ver, make sure you have plugin compatibility mode
set to automatic bridging. (Preferences>Plugins>)
4. You could try temporarily moving the .dll file out of the c:\VST folder,
running REAPER, then, under Preferences>Plugins>, make sure 'Terminate REAPER if plugin corrupts process heap', closing REAPER, moving the .dll back, running REAPER, and see if it recognizes it this time. If so, it may be buggy.
I think there is an option for a buggy plugin compatibility mode, (someone chime in).
Does the plugin give any other app trouble?
What machine/OS are you running?
Have you had a recent change of hardware or software?
Are you being super duper patient....like leaving the room for an hour lol...?
Have you tried a system restore point?
Are you using MAC, rendering pretty much all of the foregoing advice useless?
Am I forgetting three or four other ideas I had while typing?
Could you go back to the previous version of REAPER until Valhalla or Cockos fixes the issue?
To the last 2 questions, the answer is yes.
This is alot, but it is a virtually complete troubleshooting process in my opinion....
I am sure there are things I am not thinking of, and I wish you the best.
-Never
Edit: I see from the pic you are using Win, but I left the MAC question cuz it's funny.
new install of reaper is scanning VST's endlessly and will not load***************
Linear Mode
