Hi all,
Until yesterday I had a bunch of Sonar (6.2.1 w/ XP) projects with instances of Helios working fine. After upgrading to 4.7.1 when I open these projects, I get an error message indicating Helios is missing.
I can still open a new instance of Helios so the plugin works. Problem is I have lost all the EQ settings I had previous to upgrading UAD software.
This doesn't seem to be a problem with other UAD plugs, only Helios. This is the error I got from Sonar:
The following plugins were missing from your project.
Plugin: UAD Helios 69(m)
NO MATCH
CLSID: 141AC902-4535-4155-5541-4448454C7E31
So perhaps the CLSID has changed in 4.7.1? I found this on the Sonar forum from the Cakewalk CTO. It seems to point the finger at the plugin vendor but it also refers to a CLSID error as Direct X where UAD is VST) --
Thanks, chrisL
Until yesterday I had a bunch of Sonar (6.2.1 w/ XP) projects with instances of Helios working fine. After upgrading to 4.7.1 when I open these projects, I get an error message indicating Helios is missing.
I can still open a new instance of Helios so the plugin works. Problem is I have lost all the EQ settings I had previous to upgrading UAD software.
This doesn't seem to be a problem with other UAD plugs, only Helios. This is the error I got from Sonar:
The following plugins were missing from your project.
Plugin: UAD Helios 69(m)
NO MATCH
CLSID: 141AC902-4535-4155-5541-4448454C7E31
So perhaps the CLSID has changed in 4.7.1? I found this on the Sonar forum from the Cakewalk CTO. It seems to point the finger at the plugin vendor but it also refers to a CLSID error as Direct X where UAD is VST) --
Any suggestions? I'm hoping this won't end up with UAD and Sonar people pointing to each other for the solution.This error can happen if the plugin installed on the machine is incompatible with the preset data that was saved with the project. This is normally indicative of a plugin which is no longer backwards compatible with its old presets. Its normally an error for a vendor to release a plugin version that is no longer backwards compatible.
For DirectX plugins, in such cases the CLSID needs to be revised if the plugin is not compatible. For VST's the VST ID should be changed. Failure to do either can result in this scenario where presets fail to load (or can even cause the plugin to crash)
Thanks, chrisL