Saving files in 6.0 under the same name -Sound Forge - PC

Subject:Saving files in 6.0 under the same name Posted by: pup Date:3/17/2003 2:40:01 PM Hello, all - I just got 6.0, and I'm a bit confused. So at the risk of being demoted to newbie status again, I'm asking you all for some clarification. Here's my scenario: I open a HUGE file for the first time (watch it build .sfk and .sfap0 files) chop it up a bit with some edits save it under the same file name (get the prompt to "replace?" - say yes) now close the file Now - shouldn't I be able to open it again and BAM! - have instant access to my file for more editing? I mean, I didn't select "automatically delete temporary files upon closing," but the darn thing has to rebuild the sfk and proxy stuff again while I wait. Is this right? In 5.0 I used to open a file, do some edits, and when some progress was made I'd just hit the save button ans walk away to get some coffee or something. I thought the whole point to SF 6.0 was to keep me from waiting all the time for building peaks and such. Can someone enlighten me on this? Thanks. - pup
Subject:RE: Saving files in 6.0 under the same name Reply by: Sonic Date:3/17/2003 3:20:38 PM Once you save edits to a compressed format, the proxy is no longer valid (since the file has been recompressed). So Sound Forge rebuilds it. Same goes for peaks. If you are saving before you close the window, this should occur right after you save. If it does, and the .sfap0 and .sfk are up to date, they should not need rebuilding on a close and re-open. If you are just closing the file and saving via the "Save changes to blah blah?" box, Sound Forge doesn't bother to rebuild the peak and proxy until you open the file again. If that is not the behavior you are seeing, it may be a bug. Please provide format, length, types of edits, etc. Aside from that, one drawback with 6.0 is that it builds proxies for things that don't really need them (e.g. pca). Proxies are becoming less and less necessary as machines get faster and compression format APIs get friendlier. The next major version of Sound Forge will likely use proxies only in a few rare cases (e.g. interleaved DV audio). Until then, if possible and if disk space is not a huge issue for you, try to use .wav or .w64 as your editing format up until you are ready to compress for final delivery. Besides not requiring a proxy, Sound Forge can attempt to pull some tricks to speed up uncompressed saves under certain circumstances. If you are using a lossy compression format, this is good practice anyway, to avoid re-compressing the material over and over. J.
Subject:RE: Saving files in 6.0 under the same name Reply by: keether Date:3/17/2003 10:58:57 PM "...walk away to get some coffee or something": boy does that bring back memories! I replaced my old 1997 AMD K1 (pentium, essentially) with a generic something cheap but much newer with lots more RAM. I thought it was the new kind of Save they'd gone to, that made everything so sprightly. (They talk about it in the manual.) But after reading your note, I kind of realize it's the computer speed and RAM--at least in part. Even 300MB files open in a few seconds now.
Subject:RE: Saving files in 6.0 under the same name Reply by: pup Date:3/18/2003 1:12:35 PM Well there it is - I use .pca files all the time! Thanks so much for the info. - pup

Subject:Saving files in 6.0 under the same name

Posted by: pup

Date:3/17/2003 2:40:01 PM

Hello, all -

I just got 6.0, and I'm a bit confused. So at the risk of being demoted to newbie status again, I'm asking you all for some clarification. Here's my scenario:

*I open a HUGE file for the first time (watch it build .sfk and .sfap0 files)

*chop it up a bit with some edits

*save it under the same file name (get the prompt to "replace?" - say yes)

* now close the file

Now - shouldn't I be able to open it again and BAM! - have instant access to my file for more editing? I mean, I didn't select "automatically delete temporary files upon closing," but the darn thing has to rebuild the sfk and proxy stuff again while I wait. Is this right? In 5.0 I used to open a file, do some edits, and when some progress was made I'd just hit the save button ans walk away to get some coffee or something. I thought the whole point to SF 6.0 was to keep me from waiting all the time for building peaks and such.

Can someone enlighten me on this? Thanks.

- pup

Subject:RE: Saving files in 6.0 under the same name

Reply by: Sonic

Date:3/17/2003 3:20:38 PM

Once you save edits to a compressed format, the proxy is no longer valid (since the file has been recompressed). So Sound Forge rebuilds it. Same goes for peaks.

If you are saving *before* you close the window, this should occur right after you save. If it does, and the .sfap0 and .sfk are up to date, they should not need rebuilding on a close and re-open.

If you are just closing the file and saving via the "Save changes to blah blah?" box, Sound Forge doesn't bother to rebuild the peak and proxy until you open the file again. If that is not the behavior you are seeing, it may be a bug. Please provide format, length, types of edits, etc.

Aside from that, one drawback with 6.0 is that it builds proxies for things that don't really need them (e.g. pca). Proxies are becoming less and less necessary as machines get faster and compression format APIs get friendlier. The next major version of Sound Forge will likely use proxies only in a few rare cases (e.g. interleaved DV audio).

Until then, if possible and if disk space is not a huge issue for you, try to use .wav or .w64 as your editing format up until you are ready to compress for final delivery. Besides not requiring a proxy, Sound Forge can attempt to pull some tricks to speed up uncompressed saves under certain circumstances.

If you are using a lossy compression format, this is good practice anyway, to avoid re-compressing the material over and over.

J.

Subject:RE: Saving files in 6.0 under the same name

Reply by: keether

Date:3/17/2003 10:58:57 PM

"...walk away to get some coffee or something": boy does that bring back memories!

I replaced my old 1997 AMD K1 (pentium, essentially) with a generic something cheap but much newer with lots more RAM. I thought it was the new kind of Save they'd gone to, that made everything so sprightly. (They talk about it in the manual.) But after reading your note, I kind of realize it's the computer speed and RAM--at least in part. Even 300MB files open in a few seconds now.

Subject:RE: Saving files in 6.0 under the same name

Reply by: pup

Date:3/18/2003 1:12:35 PM

Well there it is - I use .pca files all the time!

Thanks so much for the info.

- pup