mettelus
Is it possible one machine used VST3 and the other does not have them (but does have VST2 versions)? The only time I saw this was testing a project (created in Splat with VST3 migration on) and opening it in X2. The VST2 plugs were there but the project referenced the VST3s it could not use.

I have since shut VST3 migration off in preferences so both versions remain exposed.

We usually only install the 64bit vers of vst3's for all newer plug ins. We asked the other studio and they confirmed the same I will have to do some more digging it s possible they are mistaken and have vst2 installed or 32bit versions. I will report back once we get this resolved I am contacting Slate support thanks for the ideas guys 

I ran into trouble on the "same" system when Waves dropped DX in favor of VST. The VST plug-ins are the same as their deprecated DX counterparts, but not recognized. I wish CW would prompt me to select (at my own risk) a replacement plug-in and then remember the mapping. As it is now, I have had to resort to exporting presets and importing them, a royal pain.

eric_peterson
I ran into trouble on the "same" system when Waves dropped DX in favor of VST. The VST plug-ins are the same as their deprecated DX counterparts, but not recognized. I wish CW would prompt me to select (at my own risk) a replacement plug-in and then remember the mapping. As it is now, I have had to resort to exporting presets and importing them, a royal pain.

Agreed, There should definitely be a "browse to" or search function allowing the user to re associate the plug ins  

eric_peterson
The VST plug-ins are the same as their deprecated DX counterparts, but not recognized.

I'm not sure they really are the same. They're registered differently in Windows, and VST plug-ins have specific IDs that DX plug-ins don't have. If SONAR is used to recognizing a certain type of plug-in, probably the only valid way to associate with a new version would be by comparing the spelling of the plug-in's name. 

Right, they are DLL's registered uniquely, I didn't mean to infer that they were identical.  But, ultimately, they are functionally the same from the user perspective of a black box that has ins, outs, and configuration parameters.  
 
A migration path should be possible in the host. The host could even do the export of the old parameters (it has them), ask you for the new replacement plug-in, then do the import of what it exported, and if there are no errors then remember those steps for future use un-prompted where it just converts automatically.
 
Yes, and they could do all this just to make the center of the known universe happy ... Ha ha ... ;-) 
 
 

eric_peterson
A migration path should be possible in the host. The host could even do the export of the old parameters (it has them), ask you for the new replacement plug-in, then do the import of what it exported, and if there are no errors then remember those steps for future use un-prompted where it just converts automatically.

 
Yes, that would be cool. I don't think it's something that could happen automatically, though. I think you would have to invoke it on a case-by-case basis. Maybe there would be some way to build it into the plug-in manager...
 

eric_peterson
Right, they are DLL's registered uniquely, I didn't mean to infer that they were identical.  But, ultimately, they are functionally the same from the user perspective of a black box that has ins, outs, and configuration parameters.  
 
A migration path should be possible in the host. The host could even do the export of the old parameters (it has them), ask you for the new replacement plug-in, then do the import of what it exported, and if there are no errors then remember those steps for future use un-prompted where it just converts automatically.
 
Yes, and they could do all this just to make the center of the known universe happy ... Ha ha ... ;-) 
 
 

Very similar to the functionality of Adobe products namely premiere pro. If a file associated with a project is not found it directs you to the last known directory or file location and you have the option to search for it and re associate the link I suppose the same exists currently in Sonar when a project file is missing