Sound Forge 13 freezes and crashes constantly

Gordon-Smith9957 wrote on 2/19/2020, 8:23 AM

I don't know what's up with SF Pro 13 lately... I'm using the latest, Build 131, on two different Windows 10 Pro 64-bit machines with different soundcards/interfaces, and it just freezes and/or crashes every day. SF13 is notorious for freezing after I've minimized it or even just switched to another application and then back to SF13. Yesterday I think I submitted 3 or more crash reports. I'm starting to regret having upgraded from Sony's SF11.

Comments

TR_Mala wrote on 2/28/2020, 8:35 AM

The program has been crashing on me repeatedly for the past several days since updating Windows 10. It seems to do so when manually entering effects parameters in any one of iZotope's 64-bit Neutron/Ozone plug-ins , and only while previewing the track. Entering parameters while not previewing the track doesn't seem to trigger the crash. It's strange...and frustrating. I'm running build 131 of SF13.

James-Lo wrote on 2/28/2020, 11:41 AM

@TR_Mala, I just tested Ozone 8 Elements 64-bit + SF Pro 13-64 bit build 131 on Windows 10 Pro 1903 and Windows 10 Pro for Workstations 1909 and did not crash while previewing and dragging controls around. Have you considered uninstalling the Windows update you suspect was the cause of your problems? Full disclosure: I've never done it--I just saw that it was possible but am scared to try it on my machines because they are currently working for some reason, knock on wood.

@Gordon-Smith9957, what version of Windows 10 Pro are you running?

Gordon-Smith9957 wrote on 3/5/2020, 12:33 PM

I'm running Win10 Pro version 1809 on both PCs: a Dell desktop and a Dell laptop. SF13 has been behaving a lot better since I opened this thread, only crashed once or twice, but it is very sensitive to being backgrounded. I have to be very careful when I bring it back to the foreground, I have to wait until the playback-position cursor starts blinking again before I do anything.

James-Lo wrote on 3/6/2020, 7:23 AM

I'd say: if it's working well enough to get things done, then finish your work, and once you have some breathing room, try updating the OS. If that makes things worse, try uninstalling the update. BTW, if you feel things are now working so well that you'd rather not introduce any risk at all, there is a setting to make Win10 stop checking for updates for a period of time. I'm going to do that the next time I have a big high-pressure project. (Same caveat/full disclosure as my previous post)