Won't scan Scheps Omni Channel SOLVED (mostly)

When embedding an image in a post, use a link to the image and not a link to the page hosting the image. In this case, the post contains https://imgur.com/a/ylkurio as the image instead of https://i.imgur.com/UHgA04w.jpg the url for the image

The problems I see with these settings are the rescan options are enabled and there are duplicate scan paths.
 
Normally the two rescan options should be disabled.
 
having c:\program files (x86)\waves in the scan path will scan
c:\program files (x86)\waves\plug-ins v10
c:\program files (x86)\waves\plug-ins v10\scheps omni...
c:\program files (x86)\waves\plug-ins v9
twice.
 
At a minimum both the rescan settings should be disabled and the scan path should be cleaned up to insure plug-ins only get scanned one time. BTW, this may not address the OP but are definitely issues with the scanner setup.

Include the directory with the dll in the list of paths to scan.

You only need to scan the folders with the Waves Shell .DLL and .VST3 files.
 
64-bit VST3 file installs almost always default to: C:\Program Files\Common Files\VST3
 
I install all 64-bit VST2 files to: C:\Program Files\VSTPlugIns
 
You can almost always specify the VST2 install folder during installation. The only other folder I need to include in my scan list is the 64-bit Native Instruments VST2 folder. NI don't let you specify the install folder. Sigh.
 
C:\Program Files\Native Instruments\VSTPlugins 64 bit
 
Whenever I have a problem when adding new Waves plugins, I deleted the following folder and all of its contents. Waves rebuilds it the next time the shells are scanned.
 
C:\Users\Primary\AppData\Roaming\Waves Audio
 
Replace "Primary" in the URL above with your username.
 
The "Cache" subfolder is usually where the problem lies, but deleting the whole thing tends to solve a number of Waves plugin problems.
 
NOTE: You do NOT need to scan the Waves folder that holds the .BUNDLE files.

TheMaartian
You only need to scan the folders with the Waves Shell .DLL and .VST3 files.
 
64-bit VST3 file installs almost always default to: C:\Program Files\Common Files\VST3
 
I install all 64-bit VST2 files to: C:\Program Files\VSTPlugIns
 
You can almost always specify the VST2 install folder during installation. The only other folder I need to include in my scan list is the 64-bit Native Instruments VST2 folder. NI don't let you specify the install folder. Sigh.
 
C:\Program Files\Native Instruments\VSTPlugins 64 bit
 
Whenever I have a problem when adding new Waves plugins, I deleted the following folder and all of its contents. Waves rebuilds it the next time the shells are scanned.
 
C:\Users\Primary\AppData\Roaming\Waves Audio
 
Replace "Primary" in the URL above with your username.
 
The "Cache" subfolder is usually where the problem lies, but deleting the whole thing tends to solve a number of Waves plugin problems.
 
NOTE: You do NOT need to scan the Waves folder that holds the .BUNDLE files.

I've never had to remove anything when I get a new Waves plugin. And you're right - you only need to scan the folders with the Waves Shell .DLL and .VST3 files.
 
Scheps Omni Channel works fine for me.
 

dennish
Thanks for the reply
 
"You only need to scan the folders with the Waves Shell .DLL and .VST3 files."
"64-bit VST3 file installs almost always default to: C:\Program Files\Common Files\VST3" 
 
I have those in the scan path
 
"Whenever I have a problem when adding new Waves plugins, I deleted the following folder and all of its contents. Waves rebuilds it the next time the shells are scanned.
 C:\Users\Primary\AppData\Roaming\Waves Audio"
 
I tried that with no success.

Is there any chance you've put the path in twice? Not literally twice, but if you've got say the parent folder as well as the child folder, it may confuse the scanner?

Thanks for all your help- I am going to have to get back to the problem after the weekend when I return from a small trip. Hopefully I will be able to submit a "solved" post!
Much appreciation!