Hi.
For awhile, Sound Forge 13 was quite stable on this Windows 10
machine running Jaws. A recent update caused things to return to a
very unreliable state, similar to how Sound Forge 12 behaved. Doing
a periodic save, save as, etc. causes the program to crash.
Relaunching the program, I get the dialog stating that the last
session ended prematurely and to click Recover. I do so, and get
another error that the file cannot be found or opened.
Here's the really bad part. I then search my hard drive for the wav
file I was working on, and it's gone! Poof! It's not where it was
saved, it's not in the Recycle Bin, and it's not in any of the
temporary files in Sound Forge's temporary work folder.
So, if you're currently running SF 13 build 96, my advice is to stay
there, and ignore the message asking you to update to build 100.
Chris
----------------------------------------
Check out The Making Better podcast, interviewing some of the world's
finest thinkers, discussing an optimistic vision of the future.
https://www.makingbetterpod.com/
PLEASE READ THIS FOOTER AT LEAST ONCE!
To leave the list, click on the immediately following link:
ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe
If this link doesn't work then send a message to:
ddots-l-request@xxxxxxxxxxxxx
and in the Subject line type
unsubscribe
For other list commands such as vacation mode,
click on the immediately following link:
ddots-l-request@xxxxxxxxxxxxx?subject=faq or
send a message, to
ddots-l-request@xxxxxxxxxxxxx
and in the Subject line type
faq
