A new problem started happening out of the blue.
 
1. I run both 32-bit and 64-bit versions of Sonar X1 Pro. Normally Sonar X1 32-bit loads up the GURU.dll just fine. It shows up in the browser list --> I can click on it and load an instance of this VST. I have hundreds of projects using this plugin. 32-bit is still working fine in Sonar X1 32-bit.
 
2. I can open up the projects that already contain a Guru 32-bit track instrument in Sonar X1 64-bit just fine. But the 32-bit instance of GURU will now only load if the project was saved via Sonar X1 32-bit prior. In the browser list (of Sonar X1 64-bit
) a GURU (32-bit) VST instance used to show up in Sonar X1, 64-bit, such that when I click on it I could also add new instances of Guru -32-bit to a Sonar X1 64-bit project, as it was naturally Bitbridged via Sonar internally.
 
However now in Sonar X1 64-bit, although GURU is still showing up in the browser, clicking on GURU VST does nothing. No error, no VST is spawned.. nothing. But I can still open previously saved projects that use GURU (where GURU loads up fine).
 
Via previously found forum links to possible solutions,  I've "Reset All Plugin VSTs" via preferences and have "Re-scanned existing Plugins". Although GURU is showing up in the vst browser in 64-bit Sonar, clicking it still does nothing. I can't load GURU. The Sonar 64-bit browser instance even changed the "GURU (32-bit)" naming convention to just "GURU" for some reason.
 
So then I tired jBridge the GURU.dll.  Still no success. The jbridged GURU.64.dll shows up in Sonar X1 64-bit browser, but clicking it does nothing.  ---> Nothing has changed on my system, other than the usual Windows updates that get pushed to my machine. 
 
Any ideas?  Fxpansion killed GURU and only produced a 32-bit version of this plugin. Don't know why I can't spawn new instances in Sonar X1 64-bit all of the sudden. I of course, could go back to the 32-bit version of Sonar to build the tracks and then re-open in Sonar X1-64bit, but this is a pain in the butt going back and forth. I eventually want to migrate completely to Sonar 64-bit.  Thanks in advance for feedback.
 
BTW: Windows 7 Pro; 64-bit; 32GB RAM; 8-core processor built by ADK so no performance issues never before.

Anyone?

Okay after investigating, I found this out. Does anyone have any ideas???
 
I usually use the graphical VST browser window in Sonar to load instruments. In Sonar X1, 64-bit, Guru and Guru.64 (my jBridged version) show up in the view. But double-clicking it does nothing.
 
But... on a hunch, I decided to go to an audio track, right click and try to insert the GURU plugin via right-clicking and using the "Soft synths" entry. But Guru nor Guru.64 show up in this list. I am using a custom layout. So I thought, "I'll go to the default plugin layout". It doesn't show up there either. As far as the custom layout, I am using the same custom layout in both the graphical VST plugin window as the one used when right clicking on the audio track to insert it that way. Shows up in one, but not the other view.  Thoughts????

Bump.  Nothing????

I have no idea and do not have GURU (jBridge or a 32bit version of SONAR installed) to play with but here is an idea. Try building a track template in 32bit SONAR and see if it will load in 64bit SONAR. IIRC, you can even load jBridged effects in 32bit SONAR so you might try building the template with GURU wrapped with jBridge. Or load up a project in 64bit SONAR that has a working instance of GURU and save the track(s) as a template.

I do not have those, and have no recollection of similar issues from any other plugin.
 
Got to ask - though I suspect the answer is no, have you done any maintenance whatsoever to these plugins?
 
I'll do some poking around and see if I can figure anything out to help you.  
 
Do you have a way to roll back the Windows maintenance to a point where things were working?
 
Bob Bone
 

By the way - I just moved from Gaithersburg to Laurel, and used to live in Ellicott City.
 
Small world.
 
Bob Bone
 
 

That sounds like a BRILLIANT idea!  I mean it just might work, and I wouldn't even have to use jBridge. You see, I can open GURU natively in 32-bit Sonar. Once that happens, opening the project in Sonar X1 64-bit will also load the instance of GURU. Just cant add new instances of GURU in Sonar X1/64. 
 
So I could try your theory. I could, in essence, maybe create a template that has two or three GURUs in it from the get-go (I could always delete an instance after the fact, if I didn't need it). Since memory is not a problem on my machine (32GB).

With one working track template, you can insert as many instances in a project as you wish.

robert_e_bone
I do not have those, and have no recollection of similar issues from any other plugin.
 
Got to ask - though I suspect the answer is no, have you done any maintenance whatsoever to these plugins?
 
I'll do some poking around and see if I can figure anything out to help you.  
 
Do you have a way to roll back the Windows maintenance to a point where things were working?
 
Bob Bone
 

No. I typically don't do Windows systems poking around on my PC. Just installs. No tweaking done to Guru.