When loading a project from another system Sonar complains about missing plug-ins

When loading a Sonar project from another system Sonar complains about missing plug-ins despite the plug-ins being installed 
 
Anybody have a fix for this ? As there is no feature to search or browse to missing plug-ins, how is one supposed to load a project from another studios system ? Or are we expected to all use the same plug-in folder/naming conventions ? We've had this issue in the past when upgrading a system etc and are usually forced to re install plugins but have not had to deal with the issue in regards to opening a file from another studios session. 
I have been a long time Sonar user and supporter but man is it getting hard to keep that game up.
 
We submitted more than a few bug reports years ago when this cropped up and still no fix ?
 
 
 
 
 

More data, please...are you talking about plug-ins that come with SONAR, or plug-ins from other manufacturers?

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.

related to the old 8.3 filename format maybe?

I have many third-party plug-ins installed on my laptop and desktop. They have different install paths; the laptop is a to-the-letter Cakewalk installation and the desktop is highly customized, but I have not experienced this problem so can't offer any suggestions on how to solve. IIRC Slate uses iLok, yes? Could there be some kind of secondary authorization, like being keyed to a specific hard drive or machine ID? 
 
Do Kylotan's suggestion first - make sure the plug-ins show up in the plug-in manager. But consider contacting Slate support. Perhaps they have encountered this issue before, and have a simple solution.
 
If all else fails, maybe you could obtain the presets used for the plug-ins in particular projects, load your plug-ins to replace the identical ones in the project, then load the presets. But it really seems that shouldn't be necessary. SONAR can load projects from collaborators where you have mutually owned plug-ins. The question is what about specific plug-ins complicates that process.

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 

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  

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
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