Auto Trim/Crop corrupts WAV files in Windows 7 -Sound Forge - PC

Subject:Auto Trim/Crop corrupts WAV files in Windows 7 Posted by: Velcro Face Date:12/17/2009 9:15:06 PM After I run Auto Trim/Crop on a lengthy stereo WAV file, Windows 7 sees it as corrupt. It can't be moved, copied, deleted, or played (except in Sound Forge). Merely opening the folder that contains the file pegs the CPU at 98%. The only way the file can be deleted is through a command prompt. I have opened a ticket with Sony, and have exchanged messages over the course of the past couple weeks, but we're still at square one. I've been working with these files for years under Vista, without an issue. I use Auto Trim/Crop extensively to condense consultations, and I'd hate to abandon that feature just because it doesn't work in Windows 7. I'm especially disappointed because the primarey reason I upgraded to Sound Forge 10 (from version 9) was its support for Windows 7. Has anyone else experienced this issue?
Subject:RE: Auto Trim/Crop corrupts WAV files in Windows 7 Reply by: ForumAdmin Date:12/18/2009 7:45:50 AM Please define "lengthy" and specify file format, how/where the file was generated, Auto Trim/Crop settings, and Save settings/method if applicable. J.
Subject:RE: Auto Trim/Crop corrupts WAV files in Windows 7 Reply by: Velcro Face Date:12/18/2009 8:17:45 AM The files range in length from 300 MB to 800 MB. I have yet to try it on smaller files. These are Microsoft WAV files created at 48,000 Hz using CallBurner (a Skype audio recorder). Each side is recorded separately as a mono file, and I combine them to make a stereo file in Sound Forge. I use the "Phrase concatenator 1" setting in Auto Trim/Crop, which creates lots of regions in the file. -- Michael

Subject:Auto Trim/Crop corrupts WAV files in Windows 7

Posted by: Velcro Face

Date:12/17/2009 9:15:06 PM

After I run Auto Trim/Crop on a lengthy stereo WAV file, Windows 7 sees it as corrupt. It can't be moved, copied, deleted, or played (except in Sound Forge). Merely opening the folder that contains the file pegs the CPU at 98%. The only way the file can be deleted is through a command prompt. I have opened a ticket with Sony, and have exchanged messages over the course of the past couple weeks, but we're still at square one.

I've been working with these files for years under Vista, without an issue. I use Auto Trim/Crop extensively to condense consultations, and I'd hate to abandon that feature just because it doesn't work in Windows 7. I'm especially disappointed because the primarey reason I upgraded to Sound Forge 10 (from version 9) was its support for Windows 7. Has anyone else experienced this issue?

Subject:RE: Auto Trim/Crop corrupts WAV files in Windows 7

Reply by: ForumAdmin

Date:12/18/2009 7:45:50 AM

Please define "lengthy" and specify file format, how/where the file was generated, Auto Trim/Crop settings, and Save settings/method if applicable.

J.

Subject:RE: Auto Trim/Crop corrupts WAV files in Windows 7

Reply by: Velcro Face

Date:12/18/2009 8:17:45 AM

The files range in length from 300 MB to 800 MB. I have yet to try it on smaller files. These are Microsoft WAV files created at 48,000 Hz using CallBurner (a Skype audio recorder). Each side is recorded separately as a mono file, and I combine them to make a stereo file in Sound Forge. I use the "Phrase concatenator 1" setting in Auto Trim/Crop, which creates lots of regions in the file.

--
Michael