scook

Keni

scook
when a log is requested at the end of the scan a message pops up with the path

Tried this, but got no toast with path...

If the message does not appear, it is likely the key sequence was not entered correctly. In Preferences > File > VST Settings hold down the SHIFT key and click the Scan button.

Thanks scook...
 
From this method, I got the path and looked at the log.
 
I see it scanned hybrid's dll, but it does not show in the registered plugins???
 
Any thoughts?
 

Did you check both Audio Effects and Instrument registered areas?

scook
Did you check both Audio Effects and Instrument registered areas?

Yup! Even looked in the dx areas, excluded, permanently excluded, as well as naming peculiarites...

No sign of the word hybrid...

...and i'm not using any custom menus, only the default which i expect to display all...?

I have no idea what name the plug-in uses. If it is a new VST2 plug-in it may be in the uncategorized folder in the browser plug-in list when using the "Sort By Category" layout.

Further investigation shows that the scanner decided it is not a vst plugin?
 
VSTSCAN: VST plugin previously scanned
VSTSCAN: WRITE VST DATA...
VSTSCAN: WRITE VST DATA - successfully updated VST plugin inventory record...
VSTSCAN: ---- 170: c:\program files\cakewalk\vstplugins\Hybrid_x64.dll ----
VSTSCAN: [ShortPath] c:\PROGRA~1\cakewalk\VSTPLU~1\HYBRID~1.DLL
VSTSCAN: [RegKey] Software\Cakewalk Music Software\Cakewalk\Cakewalk VST X64\Inventory\c:/program files/cakewalk/vstplugins/Hybrid_x64.dll
VSTSCAN: Previously scanned - NOT a VST plugin
VSTSCAN: WRITE VST DATA...
VSTSCAN: WRITE VST DATA - successfully updated VST plugin inventory record...
 
Ah! I don't know if it works yet, but I just changed the value of isvst in the registry from 0 to 1 and it is now in the registered list... gonna try running it now...
 
thanks!
 

Here area a few alternatives to directly messing with the VST inventory
1) in Preferences > File > VST Settings enable "Re-scan failed plug-ins" and run a manual scan. Deselect the rescan option after running the scan.
2) Move the hybrid.dll out of the scan path, run a manual scan, put the dll back into the scan path, run a manual scan
3) run a vst reset

scook
Here area a few alternatives to directly messing with the VST inventory
1) in Preferences > File > VST Settings enable "Re-scan failed plug-ins" and run a manual scan. Deselect the rescan option after running the scan.
2) Move the hybrid.dll out of the scan path, run a manual scan, put the dll back into the scan path, run a manual scan
3) run a vst reset

Thanks... I get the idea...
 
...but not necessary. Editing the registry did the trick... It is now working!
 
Thanks for sticking with me on this and leading me to the fix!
 

I'm glad it's working for you now.
There are some good air sounds.
I managed to buy a whole bunch of expansions for like a buck each.
Totally worth it.
I do hope Bandlab brings back Z3ta 2 or in the future Z3ta 3!!!

Daibhidh
I'm glad it's working for you now.
There are some good air sounds.
I managed to buy a whole bunch of expansions for like a buck each.
Totally worth it.
I do hope Bandlab brings back Z3ta 2 or in the future Z3ta 3!!!

Thanks!

First look/listen was positive... we'll see how useful it is over time.
I have both the z3ta and z3ta 2 and use them often...

>>VSTSCAN: Previously scanned - NOT a VST plugin


This means that during one of your scan's the plugin load itself failed. When that happens VstScan process flags the plugin as not a VST plugin. It does this so that we don't repeatedly waste time trying to scan DLL's in the scan path that aren't actual plugins. Most likely what happened is you had a bad install or plugin that was not yet authorized at one time. This is a common problem and the normal way to solve it is by setting the "rescan failed" flag in the vst preferences and rescanning to pick up the plugins.