Subject:Save as, other various affects freazing the system

Posted by: JH_Radio

Date:11/8/2003 10:41:54 PM

Hi.
Running Sound Forge 7.0A here. When trying to save wave files, only get about 36 minues saved before the computer freazes. I've checked the portion of the wave file saved, so that is how I knew how long of the three hour file was in fact saved.
ALso, I've noticed that other efects such as normalize, volume, wave hammer, etc are also freazing during the process of scanning before it even makes changes to the sound file.
What should I do from here?
I've made sure to run Nortin Win Doctor and corrected all of the shortcut problems, and other areas in the registery. Since I have my temp files saving on a different drive, I have defraged the temp drive. also, i ran add-aware and cleaned 46 spywhere itimes from my system.
I am not runing other programs other then Sound Forge, some services, and Jaws for windows, my screene reading program.
System is P 4, 2.6GB processor. NT5 service pack 4. 512 MB DDR ram.
Any ideas?
Thanks all.

Subject:RE: Save as, other various affects freazing the system

Reply by: Iacobus

Date:11/9/2003 7:07:23 AM

Has it been awhile since this system's been formatted? You may want to do so if that's the case.

HTH,
Iacobus
-------
RodelWorks - Original Music for the Unafraid
mD's ACIDplanet Page

Subject:RE: Save as, other various affects freazing the system

Reply by: JH_Radio

Date:11/9/2003 1:34:48 PM

I just got this system formatted in Augest of this year. (2003). I have had other problems with Sound Forge 5.... For example, if I just opne a file, I can't open big wave files in Sound Forge Five, without the system freazing. IF I try to play a short wave, or mp3 file that gets opend in SF 5, the sytem also freazes.
I do not have problems doing other tasks such as Eudora E-mail, Internet vroseing, Winamp, or DC++. The system works flawlissly and can stay up for weeks at a time as long as I don't use SF or WinMX.

Subject:RE: Save as, other various affects freazing the system

Reply by: Iacobus

Date:11/9/2003 2:14:41 PM

-Try updating drivers for any hardware devices in your system, including your soundcard and your video card.

-Reduce or turn off video acceleration.

-Pick up the latest update to 5.0 if you haven't done so already.

-Did this just start happening with 5.0, or has it happened all along?

Iacobus
-------
RodelWorks - Original Music for the Unafraid
mD's ACIDplanet Page

Subject:RE: Save as, other various affects freazing the system

Reply by: JH_Radio

Date:11/9/2003 3:18:27 PM

It has always been happening with 5.0 (only under Windows 2000).
Here is the verion I've got of 5.0...
Sonic Foundry Sound Forge Version Version 5.0f (Build 259)
Problems have been happening with both sound forge 5.0 and 7.0A on Windows 2000. Sound forge 5.0 worked fine under windows 98...
What is vidio exceleration and how do I turn this off? Will it affect anything else on my system?

Subject:RE: Save as, other various affects freazing the system

Reply by: JH_Radio

Date:11/10/2003 1:56:35 PM

I've also noted that SF 7.0A wo't record more then around 20 to 25 minutes on my system without freazing the computer.
What is it about my setup that c could be causeing these problems only with Sound Forge?

Subject:RE: Save as, other various affects freazing the system

Reply by: msterlin

Date:11/10/2003 4:55:58 PM

The first thing i would do is try to update the video driver and/or turn down hardware acceleration as suggested by mD. Right click on desktop->properties->Settings->Advanced->Troubleshoot (for XP, path is similar on other windows versions). Other drivers, irq conflicts, not using direct memory access (dma) on your ide controllers, etc - lots of possibilities.

It might seem odd that a display driver could affect audio, but it actually can affect anything that needs to update the console or display. I once worked on a project where it took nearly 2 hours to do a full clean build and often when i came back the machine would be frozen solid. It turned out that the display driver couldn't update the console window fast enough to display all the messages from the build process and simply minimizing the console window after starting the build solved the problem.