I open a bridged-32b DimPro VSTi (v1.5 from long ago and recently re-installed) into a 64b SPro Sonar (as required!). I get the Synth Prop page and a trk. So far, so good. I select the patch of my choice, it plays via echo, nice. Now, done with the patch selection, I check to see if I can dock that Synth Prop (SP) window. No joy. So, I minimize it, since I'll be back shortly. The Prop page window then disappears, never to be found again. Very repeatable!
 
This happens with SPro Full Scrn and Windowed. The DPro window is not on the desktop, the dock, the Sonar window or anywhere else. Even trying to open the SP from the browser does nothing. If the window gets closed, things are OK. If the window gets minimized it does not then re-appear from even a call on the browsers DPro SP item. Very bad!
 
My workaround is to close it in the browser, start over, and then just close the darned thing, rather than minimize. 
Another really annoying surprise.
 
It will be another couple weeks before I get time to do all the CW-Instrument updates to 64b (much less the other VST's). I don't think that bridging has anything to do with it, rather its a display status/update issue, but what do I know.

Plug-ins need a standard header to dock. To create the standard header for a 32bit plug-in hold the ALT key when opening the plug-in UI. The header opens in a second window usually behind the plug-in UI.

• I also observe this with Rapture (32b).

Running 32bit plug-ins when 64bit versions are available is not recommended. The projects should pick up the 64bit versions if they are available and replace the 32bit versions.

This is not how I'd scheduled my evening, but let's go. It took a couple try's to figure out that the Alt is when selecting OK on the SP page. (I might have to do that again to check). I hate all these hidden keystrokes (Ctrl-Shft in drum map port's??). Now I have a DPro1 BitBridge to toggle VST editor msg. I have no idea (or actually interest) in what this little msg is about. OK, figured it out, this window does have a dock option. Maybe, its just me, but I didn't stumble across this in the help file or tutorials, so far. 
 
It docked. I now have the Click to toggle msg in my dock. Should I click it? Do I need to save first? What the devil, I clicked the little 'error' type msg and DPro displays it's docked window. 
 
I'll try some more stuff with it now. 
Thanks
 

I hear your comment about 32b plugs! However, my plan had been to move onto 64b HW. Install the 32b stuff, check the other midi gear and drivers, etc worked 64b. Then bring up the 32b stuff that I know. But SPro only does the 32b install manually. I actually went through and installed the combo of SPro64(C:), SPro64(E:), SPro32(E:), X1Stud32, X1Stud64 to try and sort things out. For instance, I discovered that 32/64 bit installs share preferences (like the Folder locations), so those can't be separated, but X1 and Pro can. I've got like 100 32b vsts and 10 64 bit VSTs, which is why I intended to start with a 32b migration, but found that is no longer possible. And, its not just CW's 32b VSTs, its all the others that will need to get re-installed.
 
I agree that bridging is a real problem. That's why I was disappointed to see that C3 doesn't even have a 32b install option. I mean, its in the installer, how hard could that be?
 
 
OT: I have seen some positive comments about links/junctions to address some of the data locations issues. That's the sort of thing that C4  should do for us. Ask "Express/Advanced", set defaults where possible.
 
 
 

Opening with Alt doesn't really address the minimize 'shrink to death and never be seen again' window problem. I don't want to have to memorize any more 'magic' hidden keystrokes. A DAW should not be a puzzle.
 
But, the Alt open is a nice tip. (Aren't there context menus for that sort of thing?) I haven't found anything in the KBD help files, though I occasionally I stumble across similar 'magic' in the Ref manual.
 
 

There is nothing newer than the VST DPro v1.5 and Rapture v1.22. There is no reason to run the 32bit versions in 64bit SONAR. I doubt any effort at all was made to insure the 32bit versions work at all in BitBridge.
 
AFAIK, the few folder locations stored in ini files in the user directory do not need separate platform specific versions. Not sure which of the preferences are causing issues. Most people I have encountered performing a slow transition to 64bit do install both 32bit and 64bit versions. If the few shared preferences are an issue and you have an older version, it may be better to use the old version as the 32bit only platform and use Platinum as 64bit only. The best solution for 32bit plug-ins is to maintain a couple of folders, one for known good plug-ins which work well in 64bit SONAR and another for 32bit only.
 
I am moving this to the regular SONAR forum because this is more about 32/64bit transition than a specific problem report.

The path I've stumbled on is to try and support an 'external-static' X1d_Stud_32b and then just the C3 install and "hope" things work out. Naturally, my file system is already littered with bad experiments that I'm trying to clean up. But without logs of changes, this is pretty risky. 
 
Anything other than full system image BU of a CW system doesn't work. For me, that's already 3 drv's mandatory including the system drv. I have neither time nor interest in sorting out SPro BU issues, particularly with 'freebies', going I know not where!!
 
How many times will I pull this trigger and see what happens?

My concern with jumping into the 64b VSTs (CW and others) is ensuring I have a system stable enough to even run well. I know, time to put on the big boy pants and jump into the deep end. Abandon all previous work ye who enter.