ACID / SOUNDFORGE INSTALLATION CRASH WITH WIN2K / PLUG-INS -ACID Product Family

Subject:ACID / SOUNDFORGE INSTALLATION CRASH WITH WIN2K / PLUG-INS Posted by: jlourau Date:5/1/2001 11:05:22 AM I'm repeating the installation problems between SoundForge 5 and Windows 2000 / plug-ins (depends on the cases). The same problems occur with Acid Pro 3 beta version, plus additional crashes that completely prevent from using it. So it seems that the same (buggy) installation process is used in the new line of Sonic Foundry products. In the previous message, someone from SoundForge admits that there is a problem, which is not linked to Windows 2000, but to the plug-ins. But Sonic Foundry gives no guarantee that there will ever be a patch for the least lucky users of Sound Forge (and Acid Pro 3 beta), those who have some well- known plug-ins. Once again, in order to prevent users who want to use Windows 2000 or plug-ins from buying the latest versions of Sonic Foundry products, I'll post below the problems I've had, described as precisely as I can in order to help Sonic Foundry's technical service. Some news : With a bit of chance, SoundForge can eventually run, with the same bug at each launch, with the same failing process of trying to import plug-ins, it crashes again, and you can finally use SoundForge, but only with chance will you be able to use plug-ins. (I've tried to install several times, and I could only get the plug-ins to work the third time...??) ---------------- I have the same problem, which apparently occurs because of some plug-in installed on the system. I have lots of plug- ins and I've tried to uninstall the half of it (waves, opcode filter/vinyl/vocoder, etc.) and it doesn't change anything. During most installs, the crash occured once, and after each relaunch, no crash would happen anymore, but no directx plug-in (those native from sonic foundry or others) would be registered in the software. (Same problem with Acid beta 3, which seems to use the same plug-in importation process. After many reinstalls, magically all the plug-ins got registered, and the DirectX menus appeared, but nothing about the native plug-ins that are supposed to be installed with soundforge5 such as warhammer, amplitude modulation, etc. But at every relaunch, the crash event happens (with the whole failed plug-in importation procedure), and once it even registered the sonic foundry plug-ins who, once displayed in the effects menu, worked fine. Actually, even before getting available in Sound Forge, these plug-ins were available to other music programs such as Acid Pro 2. Seeing that the problem seemed to be solved - despite the fact that I would have this crash splash screen every time I run Sound Forge, I decided to reinstall the plug-ins I had uninstalled for debugging purposes. I reinstalled Waves, which got back in the Acid Pro 2 plug-ins list, and worked fine, but it didn't want to appear in the DirectX menu of SoundForge. Why can't Sonic Foundry solve this problem and why don't they have a plug-in configuration editor for us users to solve the problem if they don't wanna do it themselves? There's no .ini file it seems that could allow us to solve this manually. I've even tried the registry!
Subject:RE: ACID / SOUNDFORGE INSTALLATION CRASH WITH WIN2K / PLUG-INS Reply by: DaveP Date:5/2/2001 9:24:35 AM The update to Sound Forge 5.0 to 5.0b is available. The update specifically addresses the plugin problems that you had mentioned in your post as well as several other issues.
Subject:RE: ACID / SOUNDFORGE INSTALLATION CRASH WITH WIN2K / PLUG-INS Reply by: jlourau Date:5/3/2001 10:25:29 PM The new 5.0b version seems to solve the problem. Thanks to Sonic Foundry for the fast solution, I was amazed. I guess you just have left to implement these improvements to the beta version of Acid 3.
Subject:BUG IN ACID BUILD 189 : THE SOUND FORGE FIX ABOUT THE PLUG-INS ISSUE NOT APPLIED YET TO ACID 3.0 BUILD 189 Reply by: jlourau Date:5/9/2001 6:07:09 PM The 3rd-party bug that crashed when "importing" plug-ins in Sound Forge and that was also appearing in Acid 3.0 doesn't seem to have been fixed even in the latest build of Acid 3.0. As other users, I get (with the build 189 version) the same bug of fatal exception during a very slow directX plug- in scan as in the buggy version of Sound Forge 5.0. The corrected process (in Sound Forge 5.0b) is ten times faster and doesn't crash. A side-effect of this bug is that after the plug-in scan crash, ACID runs correctly, you can play the demo song for instance, but once you try to create a bus with a plug-in effect or to insert an assignable FX, the list of the plug-ins is empty! So my question is, does Sonic Foundry intend to release a ACID 3.0b version, as well as for Sound Forge.

I'm repeating the installation problems between SoundForge
5 and Windows 2000 / plug-ins (depends on the cases). The
same problems occur with Acid Pro 3 beta version, plus
additional crashes that completely prevent from using it.
So it seems that the same (buggy) installation process is
used in the new line of Sonic Foundry products. In the
previous message, someone from SoundForge admits that there
is a problem, which is not linked to Windows 2000, but to
the plug-ins. But Sonic Foundry gives no guarantee that
there will ever be a patch for the least lucky users of
Sound Forge (and Acid Pro 3 beta), those who have some well-
known plug-ins. Once again, in order to prevent users who
want to use Windows 2000 or plug-ins from buying the latest
versions of Sonic Foundry products, I'll post below the
problems I've had, described as precisely as I can in order
to help Sonic Foundry's technical service. Some news : With
a bit of chance, SoundForge can eventually run, with the
same bug at each launch, with the same failing process of
trying to import plug-ins, it crashes again, and you can
finally use SoundForge, but only with chance will you be
able to use plug-ins. (I've tried to install several times,
and I could only get the plug-ins to work the third
time...??)
----------------
I have the same problem, which apparently occurs because of
some plug-in installed on the system. I have lots of plug-
ins and I've tried to uninstall the half of it (waves,
opcode filter/vinyl/vocoder, etc.) and it doesn't change
anything. During most installs, the crash occured once, and
after each relaunch, no crash would happen anymore, but no
directx plug-in (those native from sonic foundry or others)
would be registered in the software. (Same problem with
Acid beta 3, which seems to use the same plug-in
importation process. After many reinstalls, magically all
the plug-ins got registered, and the DirectX menus
appeared, but nothing about the native plug-ins that are
supposed to be installed with soundforge5 such as
warhammer, amplitude modulation, etc. But at every
relaunch, the crash event happens (with the whole failed
plug-in importation procedure), and once it even registered
the sonic foundry plug-ins who, once displayed in the
effects menu, worked fine. Actually, even before getting
available in Sound Forge, these plug-ins were available to
other music programs such as Acid Pro 2. Seeing that the
problem seemed to be solved - despite the fact that I would
have this crash splash screen every time I run Sound Forge,
I decided to reinstall the plug-ins I had uninstalled for
debugging purposes. I reinstalled Waves, which got back in
the Acid Pro 2 plug-ins list, and worked fine, but it
didn't want to appear in the DirectX menu of SoundForge.
Why can't Sonic Foundry solve this problem and why don't
they have a plug-in configuration editor for us users to
solve the problem if they don't wanna do it themselves?
There's no .ini file it seems that could allow us to solve
this manually. I've even tried the registry!