Acid and Sonar -ACID Product Family - MAGIX Community Forums Archive

Subject:Acid and Sonar Posted by: waynegee Date:12/26/2002 1:38:54 AM Was the problem of Sonar NOT being able to use SoFo plugins or the loss of Sonar sessions using SoFo plug-ins after installing Acid update 4.0b addressed yet by SoFo? I might've missed it. Or has anyone come with a fix of some kind? Dood, this sucks.
Subject:RE: Acid and Sonar Reply by: Jessariah Date:12/26/2002 10:11:51 PM It's not that simple. The plugins that were not reading in Sonar for me were actually Sonic Timeworks, not SoFo. Also, for me, the bug surfaced BEFORE I went to 4b. ALSO...to further complicate things...not every Sonar file I had created prior to Acid 4 was effected. Seems it was only the files I created since 4.0 but before 4.0a. Sonar users-- try opening files you created before installing Acid 4. Maybe we can lock down "when" this plugin recognition bug occured.
Subject:RE: Acid and Sonar Reply by: billybk Date:12/27/2002 8:23:35 AM Hey guys, I believe this may be a Cakewalk problem. It seems, in the latest v2.1 update, and possibly since 2.0, that a restricted plugin limit bug has crept into SONAR. Cake support is aware of this and it will supposedly be fixed in the next 2.2 update, due to be released in late January ot early February. It might be a good idea to email Cake SONAR support indicating your desire to get this fixed asap. It just might speed up the process a little. It seems, once this plugin limit has been reached,(usually several hundred or so, which includes all types of plugins, DX,DXi,VST,VSTi,MFX and even excluded plugins)the first to disappear are the ones highest in the alphabet. Try this -- it worked for me: Using Sonar plugin manager, add a prefix like ZZZ (with a space after it) to all your excluded plugins to insure that they are last in the list alphabetically. When I did this, all my included plugins showed up like expected. Billy Buck
Subject:RE: Acid and Sonar Reply by: Dewaine Date:12/27/2002 10:35:30 PM I have 25 plugins and it happened to me. It IS and Acid problem, but many on this forum seem to be on the SOFO payroll or something and unable to admit the real issues Acid 4 has. Anyway, uninstall Acid 4.0b and go back to Acid 4.0a and the problems will go away.
Subject:RE: Acid and Sonar Reply by: TeeCee Date:12/30/2002 10:48:08 AM Hmmmm. I had a similar problem after installing the released version of CD Architect. Three or four SoFo plugins were unusable in SONAR and prevented my projects containing them from working. I pulled the proper .dll from my Acid (maybe 4.0a) install and fixed it. TeeCee
Subject:RE: Acid and Sonar Reply by: pwppch Date:12/30/2002 4:33:46 PM I have contacted Cakewalk and they said it is their problem and that it will be addressed in an update to SONAR. Peter
Subject:RE: Acid and Sonar Reply by: dkistner Date:12/30/2002 4:46:26 PM It's so nice when somebody owns up to it being their problem instead of finger-pointing...and even nicer when they do something about it! :)
Subject:RE: Acid and Sonar Reply by: billybk Date:12/30/2002 6:32:27 PM Look for it to be fixed in the next SONAR 2.2 update next month, and all will be good again :) Not everything is SOFO's fault. Billy Buck

Subject:Acid and Sonar

Posted by: waynegee

Date:12/26/2002 1:38:54 AM

Was the problem of Sonar NOT being able to use SoFo plugins or the loss of Sonar sessions using SoFo plug-ins after installing Acid update 4.0b addressed yet by SoFo? I might've missed it. Or has anyone come with a fix of some kind? Dood, this sucks.