With VV 3, I could use the Direct X audio plug-ins in Sonar and Cool Edit with no problem. Since installing VV 4, I get an error message when trying to use my Direct X plug-ins in Sonar and some of them appear as demos in Cool Edit Pro 2.0. what to do.
I already have the 2.2 upgrade, and like I said, the plug-ins worked fine with V V 3. Yesterday, I even tried system restore (I am using windows X P pro). With system restore I reverted back to V V 3 and once again my Direct X plug ins worked fine. Now this time I left version 3 on the hard drive and installed version 4 so that I have both of them now. Since reinstalling version 4 the Direct X problem has reemerged.
This is the error message that I get: an unknown error occurred during processing, possibly caused by an invalid parameter. It is likely that this effect is incompatible with sonar. Would you like to remove reverb from all menus in the future? So the problem has to be with the new Vegas video version.
I guess I will have to call Product support on Monday.
Thanks for your help.
I upgraded from Sonar V.2.1 to V.2.2 this morning, and all was well - I could still use SoFo plugins in Sonar just fine. (I also have SF6, Acid4 and VV3 installed on this machine.)
This afternoon I installed Vegas4 and now I'm getting the same problem as you've reported when I try to use SoFo plugins in Sonar 2.2.
Very annoying - it was all going very well until this.
That is interesting. I just tried the Parametric EQ and what I get is terrible distortion. The tempo doubles, then when I remove the plug in during playback, playback resumes normally.
It must have something to do with the fact that track automation was added in the new version. I think there is definitely a bug.