Subject:What is the deal w/Saving in Sound Forge 8???

Posted by: Illogical

Date:5/16/2006 4:57:26 PM

I have all kinds of problems with saving in SOund Forge 8. I keep getting an error when I try to save a file after editing it, saying the file is either locked or corrupted. If it's playing in Sound Forge, it's obviously not corrupted (right?), and I checked each file (there are many that do this) and they're not marked read-only. I have build D, I have 'Keep Media Files Locked' UNticked, I have plenty of other files working fine and saving fine but about 10% of my files get this error when I try to save them after a bit of normalization or just adjusting the Acid Properties.

There's a fair amount of other weird bugs, (random crashes especially) but this is the biggest problem I'm having. DOes anyone get this too or know why it's happening?

Thanks in advance!

Subject:RE: What is the deal w/Saving in Sound Forge

Reply by: rraud

Date:5/18/2006 3:09:18 PM

What file format are the source files and what file format are you trying to save?
Does the same happen when you select "Save as?

Subject:RE: What is the deal w/Saving in Sound Forge

Reply by: Illogical

Date:5/18/2006 6:10:51 PM

No, I don't get it...'save as' always works, so I end up saving as an alternate copy and then deleting the original and changing the name of the copy back. It's a pain in the backside, dunno why it does that but it's done it on quite a few files. They're all wave files, different bitrates and stuff, but all waves.

Subject:RE: What is the deal w/Saving in Sound Forge

Reply by: Geoff_Wood

Date:5/22/2006 6:22:40 PM

Is the original is on CD-ROM, or have a Read Only attribute ? Would be difficult Saving those.

geoff

Subject:RE: What is the deal w/Saving in Sound Forge

Reply by: GenJerDan

Date:5/23/2006 4:46:21 AM

I used to get that in v7 a LOT. Never did find out what it was, but it stopped doing in v8 (so far).

I'd do a Save and it would give me that error and then crash, leaving me with nothing. :(

One way to get around it is to go into Windows Explorer and delete the existing file first, then save the new version. Pain in the butt, but it worked.

Subject:RE: What is the deal w/Saving in Sound Forge

Reply by: Illogical

Date:5/23/2006 1:54:33 PM

^^ nope, it's not on CD-Rom. It's on my hard drive, it's not read-only, there's no reason for this to keep happening, but it does. I guess I'm the only lucky one though.

I guess I should be thankful my problems aren't as severe as GenDerDan's were, at least it doesn't crash, it just won't let me save the file until I rename it something else.

Subject:RE: What is the deal w/Saving in Sound Forge

Reply by: Geoff_Wood

Date:5/23/2006 3:07:57 PM

I wonder if it's something to do with folder paths ?

geoff

Subject:RE: What is the deal w/Saving in Sound Forge 8???

Reply by: Multitech

Date:5/24/2006 7:21:00 PM

I had an issue similar to this in previous version of Sound Forge and on an earlier edition of WIN2K. After copying a .wav file off of CD to the hard drive and keeping the CD stil in the drive. When editing the file you couldn't save the file that was on the hard drive even after resetting the attributes. Once the CD that had the same file name was removed the problem went away.

Can you save it as a different file name?

Subject:RE: What is the deal w/Saving in Sound Forge 8???

Reply by: GenJerDan

Date:5/25/2006 4:36:49 AM

Hmmm...maybe that's caused by the Indexing Service? Windows didn't notice the changed location yet?

Subject:RE: What is the deal w/Saving in Sound Forge 8???

Reply by: ForumAdmin

Date:6/7/2006 11:18:24 AM

If the files in question were generated in a third-party application (technically, if metadata chunks Forge does not recognize occur after the data chunk), then I expect if you just close and re-open the file after seeing the error, the changes you made have been saved, just not all the metadata.

If that is the case, this workaround will take care of the error message (and persist the unrecognized metadata):

1) Hold down Ctrl+Shift and select Options->Preferences
2) Select the "Internal" tab
3) Find the entry labeled "Enable quick, natively supported fi..."
4) Set it to FALSE
5) Appy and OK

This will be resolved in future versions of Sound Forge.

J.