Just looking for your helpful strategies to deal with all the now defunct 32 bit DX plugs and Synths lost in the move to 64 bit land.
I found that many of my projects referenced 32bit DX versions of Dim Pro, Z3ta, Tassman, Soundforge effects plugs, etc, and quite a few Cakewalk effects, man I used the Timeworks Comp on everything!
    I can substitute the Effects stuff (wish I didn't have to..) but find the following process necessary for Synth replacement...
1. Use "Replace Synth" to choose Newer VST version.
2. "Connect Synth"
3.  Smack myself in head repeatedly for NOT noting the specific patch used in the project Clip info. Ugh. Please take note of this failing on my part and save yourselves! Really, this should be standard production housekeeping that I became lax with and now suffer with...just because I would "get to it later".. what an Ultra Maroon..
4.  Go back to the 32 bit Sonar project and Find the patch name. ...and so forth.
This is tiring...but the only way? Tried a DX shell but found that just flooded my plugins list with dupes. 
And if any of youse smart folks found a patch search function on Dim Pro I will personally travel to your house and give you a bottle of Jameson...
Thanks folks.      

I think I can help you with the Patch Names. Go to where Dim data is installed (not the Mutli-Sample data which is elsewhere), I'm going to assume C: (until CW fixes the errors of their ways). I've got a 'Dim LE' folder as well. It's kind of documented if you can find the right thread. For me on 64b SPro with manually installed versions of DimPro and DimLE. this is:
C:\ProgramData\Cakewalk\Dimension Pro\Programs
 
If you load the Programs.lst file into say Notepad++ (not MS NotePad), you can search the file for patch names and the appropriate path in the Dim file selector to you patch is revealed. It's difficult to believe that CW continues to refuse to use a simple txt file, much less even an xml file for this type of data, but oh well. Nobody would update anyway.
 
Of  course, if you know the patch name and I've given you a folder path, just use MS file browser search it will show where it's hiding. I believe but haven't checked lately, that the 64b and 32b VSTis both use the same 'Progam Data' folder for patch lists.
 
Now I'm a bit curious about if RapturePro improved patch searches. Z3ta2 was a nice move in that direction.
 
I also have come to the conclusion that attempting bridging is a waste of time for those not really, really, really desperate.
 
I take my whiskey neat.
 

Why don't you load your old projects in the 32-bit version.  Bounce all the tracks with 32-bit DX effects to a new track.  Mute or archive the original track.  If you ever decide to replace those old FX with new ones, then mute or archive the bounced track and apply a new FX to the original tracks.
 
Then you have all your old projects sounding the way they always did, but you can revisit them with new FX in future if you need/want to.

The problem with bouncing from 32b project to audio to get to 64b Sonar is that a working Sonar-32b installation is needed and C3 doesn't do this. Manual setup and maintenance are required! After several months trying to sort this out, I've ended up with a 32b install of S-X1d for older projects in addition to my SPro, and then still have to deal with getting SonarPro working well enough to import the audio. If I have to go to audio to transfer a midi track using a 32b VST, I take the audio into FL Studio, not Sonar.
 
And one needs to keep track of the 'new' features/FX,etc not available in the 'obsolete 32b' version of the song when editing it for export.
 
I haven't had much success with bridging to date and have stopped even trying.
 
Maybe someone knows a better way?
 
 
 

One more note. I did this because I did try to have both the 64b and 32b SPro installed at the same time (32b manually naturally), but they share a bunch of locations in the Cakewalk Projects and Content dirs which was problematic for me. Apparently, they can't be configured separately, though I tried by manually adjusting the config in the Preferences for each. Didn't work, don't have time to try again.
 
CW's position is to go 64b, and abandon all hope for one's 'ye old stuff'.
 
 

m.letcher@q.com
 
Maybe someone knows a better way?

Since the 32bit projects were made before the new SONAR, install a different 32bit version. There is no need to use new features for old projects. An older version will have a completely separate install unless you choose to share plug-ins which I would recommend avoiding.

vuzz14
Just looking for your helpful strategies to deal with all the now defunct 32 bit DX plugs and Synths lost in the move to 64 bit land.
I found that many of my projects referenced 32bit DX versions of Dim Pro, Z3ta, Tassman, Soundforge effects plugs, etc, and quite a few Cakewalk effects, man I used the Timeworks Comp on everything!
    I can substitute the Effects stuff (wish I didn't have to..) but find the following process necessary for Synth replacement...
1. Use "Replace Synth" to choose Newer VST version.
2. "Connect Synth"
3.  Smack myself in head repeatedly for NOT noting the specific patch used in the project Clip info. Ugh. Please take note of this failing on my part and save yourselves! Really, this should be standard production housekeeping that I became lax with and now suffer with...just because I would "get to it later".. what an Ultra Maroon..
4.  Go back to the 32 bit Sonar project and Find the patch name. ...and so forth.
This is tiring...but the only way? Tried a DX shell but found that just flooded my plugins list with dupes. 
And if any of youse smart folks found a patch search function on Dim Pro I will personally travel to your house and give you a bottle of Jameson...
Thanks folks.      

One of our members has a utility called ProjectScope that finds .cwp projects queries them and lists the audio files, plugins and this is the bit for you, maybe the preset used. I'm not sure but for a few minutes effort it could help you out. In any case it's a must for organisation anyway.

The link in my signature goes to the sticky thread in the Software forum where there a list of Utilties made by some of our cleverer members for our use exclusively with Sonar. You'll find all ththe necessary love nks there. All the best.

I have not used ProjectScope but did read the write-up. I could not see where it lists presets. There rest of the info while useful w/o the presets, you are still stuck opening projects in a 32bit host.

I haven't had any problems finding a Dim Patch using MS Search if I can find the dir (or at least the drv). 
Again, another reason I feel obligated to mention that mklink data is stored on the C: drv in the reg. If I'm about to install a new HDD data drv (as I am), I'm pretty sure that I'll break every mklink connection by reinstalling a 3 month old BU. I'm not bored enough to do that experiment. 
 
The good news is that I did just do a search in the HIDDEN "Program Data" on the C: drv (though I suspect that I might have already relocated that one as well as my Docs onto a HDD from C:) for the patch name "Lo-fi Ritual.prog" and located a half dozen "ritual's". The Lo-fi is in C:\ProgramData\Cakewalk\Dimension Pro\Programs\Digital Sound Factory Planet Earth\Effects.
 
You are welcome, sir.

scook
I have not used ProjectScope but did read the write-up. I could not see where it lists presets. There rest of the info while useful w/o the presets, you are still stuck opening projects in a 32bit host.

That's why I wrote "maybe the preset used. I'm not sure". I used it only to test it for basic stability. As I was hosting it on my Onedrive, I wanted to at least assure potential users that I've checked it out and it runs on my system and doesn't break anything obvious.