|
Subject:Acid 4.0d upgrade causes Cakewalk problems
Posted by: gigasaurus
Date:6/6/2003 4:07:10 PM
The other day I was prompted in Acid Pro 4.0a to upgrade to the new release of 4.0d. I did the upgrade and its reaped havoc on my Sonar 2.2. I open up Sonar project files that I was working on before the upgrade, and I am informed that a number of my FX (including Cakewalk FX) are missing. Project files that give this error WILL NOT PLAY and you can't add FX to them. Also a number of my Sonic Foundry plugins have stopped working in Sonar (I re-registered Acid and the plugins became available, but most of them cannot be added to tracks containing audio). Cakewalk tech support duplicated the problem and have received the same complaint from other people. I reccommend you do NOT DO THE UPGRADE until this issue has been resolved. |
|
Subject:RE: Acid 4.0d upgrade causes Cakewalk problems
Reply by: ihisert
Date:6/6/2003 7:02:49 PM
I had this exact same problem with Acid Pro 4.0b. I haven't upgraded to 4.0c or 40.d yet, but now I know what to expect. Fortunately, there is a way around this problem. 1) Uninstall Acid 4.0d. 2) Reinstall 4.0 or 4.0a (if you don't have you're 4.0a patch, SoFo can still provide you with one if you e-mail their tech support). 3) Go to the C:\Program Files\Sonic Foundry\Shared Plug-Ins\Audio folder and copy the .dll files to another folder for safekeeping. 4) Install Acide 4.0d 5) Copy the 4.0 or 4.0a .dll files you stored from step 3) above back into the C:\Program Files\Sonic Foundry\Shared Plug-Ins\Audio folder. 6) All yur SoFo effects should now run fine in Sonar 2.2 I figured this might happen again when I upgraded from 4.0b to 4.0d - Now I know it will, so I'm going to take the same pre-cautions. Ian |
|
Subject:RE: Acid 4.0d upgrade causes Cakewalk problems
Reply by: SonyJEV
Date:6/6/2003 8:10:42 PM
Actually, there is a new problem that we are still working with Cakewalk to diagnose. The old problem that Ian is talking about is that Sonar would not connect to some of our updated plug-ins. This is supposed to be fixed with a Sonar update (2.3). Project5 seems to have gotten the fix for this as our plug-ins work there. The new problem somehow affects the Cakewalk plug-ins used in Sonar. We have so far been unable to reproduce this in-house and are hoping for more information from Cakewalk. I believe that 4.0d is almost identical to 4.0c, so the c update may be problematic for Sonar users as well. --j |
|
Subject:RE: Acid 4.0d upgrade causes Cakewalk problems
Reply by: ihisert
Date:6/6/2003 8:57:00 PM
Wow! Thanks for the tip on that (I didn't read gigasuarus wrote clearly enough). I'm definitely not going install 4.0c until that's all ironed out. Ian |
|
Subject:RE: Acid 4.0d upgrade causes Cakewalk problems
Reply by: TeeCee
Date:6/20/2003 3:48:25 PM
It's about time this has been fixed. I've been re-back-cross installing apps, copying files, etc. Each time after having a panic attack that my SONAR work is unusable. Now, we just need that SONAR 2.3 patch available to the public. TeeCee |
|
Subject:RE: Acid 4.0d upgrade causes Cakewalk problems
Reply by: VUZZ13
Date:6/23/2003 10:00:15 AM
Same problems here, complete with the panic....My only work-around so far is to hit "shift", open your Sonar project, and remove the offending SF plug-in, then resave....you will lose the SF plug-ins, but perhaps you can substitute another third-party's... Good Luck. Vuzz13 |
|
Subject:RE: Acid 4.0d upgrade causes Cakewalk problems
Reply by: TeeCee
Date:8/26/2003 7:02:04 PM
No update on this issue? I still don't see a Sonar 2.3 on the Cakewalk website. TeeCee |