Subject:Sound Forge 5 crashes in Win2K

Posted by: johnfoll

Date:4/17/2001 7:58:15 AM

Anybody have luck getting Sound Forge 5 to work in Windows
2000 without crashing? I thought it was working, then I ran
it the other day and it always locks up the computer know
with the splash screen still on the screen. Uninstalling
doesn't help. I repartitioned my hard disk and reinstalled
Windows 2000 Pro again,then Sound Forge 5 and it still
crashes. Does it work with DirectX 8.0? Does it work with
SCSI? Does it work with Yamaha 2100SZ Scsi CD-R?

Subject:RE: Sound Forge 5 crashes in Win2K

Reply by: apsyrtes

Date:4/18/2001 9:16:42 PM

I am using it on Win2K Pro, with DirectX 8.0a - don't know
about the SCSI burner, because I haven't tried burning from
Sound Forge and I don't have SCSI.

Subject:RE: Sound Forge 5 crashes in Win2K

Reply by: doctorsmith

Date:4/18/2001 9:24:59 PM

I found a DirectX 8.0b release at Microsoft.Com. Might help?

Subject:RE: Sound Forge 5 crashes in Win2K

Reply by: Ted_H

Date:4/19/2001 10:21:12 AM

Possibly. There are no known issues with Sound Forge 5.0
and Windows 2000. There have been issues with our programs
locking up on the logo splash screen, and this can often be
resolved by updating your video card drivers.

Ted

Subject:RE: Sound Forge 5 crashes in Win2K

Reply by: cbeck715

Date:4/19/2001 1:38:49 PM

I agree with Ted(Theodore),win2000 is not the problem, I
also had video conflicts until I upgraded my card, as
stated before, check your drivers, or if possible pop for a
new video card.

Subject:RE: Sound Forge 5 crashes in Win2K

Reply by: MikeOlson

Date:4/21/2001 8:34:38 AM

As usual with SF support on this forum, their information is incomplete and/or misleading. There is one big indirect issue with Sound Forge 5.0 and Vegas 2.0d and either Win98SE or Win2000. If a DX application that uses Pace Piracy Protection is installed on the system(e.g., Autotune, Waves 3.0), both Sound Forge 5.0 and Vegas 2.0d can crash not only itself but the entire OS.
Pace has released a new version, which in my experience resolved the problem in Win98SE, but it did not resolve the problem in Win2000.
If you have this particular problem, the sympton is this: SF starts correctly, begins to catalog the various installed DX plug-ins, and then suddenly crashes the OS. The name of the plug-in it appears to crash has nothing to do with the problem.
Some folks within Sonic Foundry are familiar with this problem, and some are not. Peter Haller (?) mentions it specifically in the Vegas forum, but neither of the technicians I talked to one the phone knew anything about it.

Subject:RE: Sound Forge 5 crashes in Win2K

Reply by: MikeOlson

Date:4/23/2001 7:51:40 AM

I received this from a lurker:

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
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: Sound Forge 5 crashes in Win2K

Reply by: Ted_H

Date:4/23/2001 10:59:10 AM

Sorry if you feel mislead, but the question was regarding
issues with Windows 2000 and Sound Forge 5.0, and there are
no issues with this setup. The issue regarding plug-ins is
something different that happens with all versions of
Windows and this is a known issue that we are currenlty
looking into.

Ted

Subject:BIG PLUG-IN BUG WITH SoundForge5 and AcidPro3Beta

Reply by: jlourau

Date:4/26/2001 5:30:20 PM

Hi, I'm the lurker described in an upper message. I'll have
to repeat the problems between SoundForge 5 and some very
standard plug-ins (I couldn't find out which ones). 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. I'll have to agree. 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 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.
----------------
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:Win 2K installation is bad even with no other software on the system

Reply by: kongbalong

Date:4/29/2001 10:45:34 AM

I too was having the problem of getting an error upon Sound
Forge 5.0 start up (under Win 2k), and then having no FX
plugins show up in the menu. I went and uninstalled *all*
my Sonic Foundry products, and plugins...

It still doesn't work! The only plugins are the ones that
installed as part of Sound Forge 5.0, and it still reports
an error when the program is started, and no fX or plugins
are listed.

I installed it on a windows 98 machine, and there was no
problem at all.

Subject:UPDATED VERSION OF THE WIN2K / PLUG-IN PROBLEM

Reply by: jlourau

Date:5/1/2001 11:04: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: UPDATED VERSION OF THE WIN2K / PLUG-IN PROBLEM

Reply by: dansolo

Date:5/1/2001 3:41:33 PM

when i last re-installed win2k i was able to leave off the
old version of the vegas, SF and beta versions as well of
each. i didnot have trouble before but now it wil search
plugins every other time i start each program. otherwise
they are available to me in each program even if i run them
at the same time. this is a time consuming process that may
take up to a minute to complete
i thik the fact that their install program does not
overwrite previos version nor uninstall beta versions when
you buy the product that the regestry gets all messed up.

if you run nortons windoctor or other clean up product you
will see multiple redundancy and garbage entries that go
nowhere. this helps to get things running better but you
must be dilligent about what you change or the progrms will
not run or will fail when searching plug ins.

Subject:RE: Sound Forge 5 crashes in Win2K

Reply by: Beep

Date:5/2/2001 3:21:59 AM

Originally posted by DoctorSmith: I found a DirectX 8.0b release at Microsoft.Com. Might help?

This is for developers only. So nobody should be downloading this unless they design Direct x applications.