Subject:Error When Saving A File
Posted by: combee
Date:2/10/2003 10:56:52 AM
I have been receiving an error message occasionally when I am saving a .wav file. It does save the corrected file, but it does not build peaks. I have to close the said file and reopen it for it to build peaks. It does not happen every time. I am wondering if anyone has encountered, or heard of, this problem. I would appreciate any advice to correct it. |
Subject:RE: Error When Saving A File
Reply by: Geoff_Wood
Date:2/10/2003 2:33:26 PM
That is a known bug (many of us get it) and is presumably being fixed. geoff |
Subject:RE: Error When Saving A File
Reply by: combee
Date:2/11/2003 1:35:02 PM
Thanks! I'm glad to know that I'm not alone and I sure hope they fix it! |
Subject:another File-Save error?
Reply by: pbeshuk
Date:2/15/2003 10:33:29 AM
I'm also having a File-Save error. I'm editing fairly large .wav files doing deletes, cross-fades, etc. After about 10 edits and several File-Saves, the next File-Save gives me an error message saying "..an error occurred...check for write access...check for enough free space". There is plenty of space on the drive. When I hit OK, to clear the error message, the file has been successfully saved, but the waveform is gone from the SForge workspace. The file is still apparently open because I can stil play it from the workspace. Any advice would be appreciated. |
Subject:RE: another File-Save error?
Reply by: rraud
Date:2/15/2003 1:37:13 PM
Next time it happens select Special/Re-build Peak Data, the waveform will re-appear. Sonic Foundry and many of us are aware of this bug. It is scary the first few times it happens, looks like everything's gone! SF sez: "it will be fixed with the next update". 6.0e I would guess. |
Subject:When?
Reply by: JTelles
Date:2/15/2003 5:14:31 PM
The only pending question is when this LONG DUE update will be available... JTelles |
Subject:thanks and doh!
Reply by: pbeshuk
Date:2/15/2003 6:28:37 PM
thanks. I actually upgraded to XP trying to solve this problem, never dreaming it was a Sforge problem. As they say...doh! |