bitflipper
bapu: the code's still 32-bit, just the registry keys have been corrected for 64-bit machines. It'll run on either platform.
 
However, your ISP kicked it back as a security risk. Sorry. After I've gotten some feedback from others who are trying it out, and I get some verification that it works on other computers than my own, I'll post it up on dropbox.

Thanks Dave.

I'll test it for you. It should go real quick. How hard can it be to find 7 vsts?

😃

mike_mccue
I'll test it for you. It should go real quick. How hard can it be to find 7 vsts?

😃

Depends.
 
Have they been ARC'd or drumagogged?
 
And if it's ARC 2 it could be more complicated.
 
HTH.

Nah, everybody knows ARC doesn't do anything.

Arc 1 was for animals, Arc 2 is for sound treatment. Please don't mix them up Bit.😜

I ran Dave's program on Win7 64/Office 2007 and worked like a charm. Thanks again!

Thanks for the feedback, Michael. After I've heard from a few others who are also trying it out, and assuming it works for everybody, I'll post it somewhere so anyone can download it.
 
In the meantime, I've emailed it to a dozen people but some of those emails were kicked back (all to gmail addresses, I think) as a "security risk". I was sending a zip file, not a naked exe, but those clever fellows at Google weren't fooled. They opened the zip file, found an executable and decided you weren't smart enough to decide whether you wanted it or not.
 
So apologies to anyone who asked for a copy and didn't get one.

Also got a reply from another person who said it worked OK and suggested adding a column to identify VST3 plugins. Thanks for that, Eurig.
 
Unfortunately, I don't know how to definitively identify a VST3 plugin because I don't have any. Yes, it's usually in the product or file name, but I can't assume that's always the case. So if anybody who's comfortable poking around the registry could have a look and see if there's maybe a registry key that flags VST3s, or check the DLL headers for identifiers, that would help.
 
Looking at the registry, I see a flaw in the program, which is that it assumes the data is under "SONAR Producer". I'm guessing the program fill fail if you're running a different edition. Maybe somebody who's running SONAR Studio could verify where the VST inventory resides for them. I'm guessing it's HKCU\Software\Cakewalk Music Software\SONAR Studio\Cakewalk VST\Inventory for 32-bit O/Ss and "Cakewalk VST x64" for 64-bit O/Ss. 
 
Once I know every possible path, I can just have the program check them all so it won't matter which version of SONAR you're running. Currently, it just checks the 32- and 64-bit paths for SONAR Producer. It's a 32-bit program so it'll run under any Windows version.
 
 

VST3 plug-ins have the extension .vst3 instead of .dll
The also must be installed in either "C:\Program Files\Common Files\VST3" or "C:\Program Files (x86)\Common Files\VST3"
 
To find all the inventory locations you are going to have to traverse "HKCU\Cakwalk Music Software" looking for "Cakewalk VST*" (if you follow my shorthand), using the position of  the "Cakewalk VST" or "Cakewalk VST X64" you have found as a guide. That way it will work for Music Creator too. Or you could just hard code it for the current release of SONAR, ignoring the name changes in the recent past like Essential.

bitflipper
Unfortunately, I don't know how to definitively identify a VST3 plugin because I don't have any. 

 
I'm not at my DAW right now but IIRC FabFilter installs VST3 versions, no?