Possibly a VERY serious bug in ACID 3.0b??? -ACID Product Family

Subject:Possibly a VERY serious bug in ACID 3.0b??? Posted by: JPThere Date:8/28/2001 1:27:59 PM Symptom: When rendering an entire song (~7 minutes) to a new file, 48Khz-24bit samples, the filesystem pointers are corrupted. I run Windows98, PII 450MHZ, 4 hard drives (IDE), 512MB of RAM. Programs (ACID and Sound Forge amongst others) are on a separate physical hard disk, away from the data (.wav files). After running a large rendering job using ACID3.0b (Render to new file), I am finding that pointers to .wav files associated with other ACID projects sitting on the same hard disk are being corrupted (ie: attempting to play one of these corrupted files yields playback of a portion of an MP3 files on the same physical disk.) Other symptoms are: an ACID project, as well as Sound Forge, cannot open a previously 'OK' .wav file due to a RIFF indicator being missing/corrupted. And in one case, a .acd file itself was corrupted. The more times you run "Render to New File" (we're talking LONG files being rendered - around 7-minute songs), the more corrupted the disk becomes. I have duplicated this on to separate physical disks. This did not seem to occur with ACID2.0. I cannot verify if it occurred with ACID3.0 build 189. This could prove to be a nightmare for me if I find out that I cannot repair the corrupted ACID project file... SF, have you heard of this problem? BE SURE TO BACKUP BEFORE RENDERING LARGE FILES!!! John
Subject:RE: Possibly a VERY serious bug in ACID 3.0b??? Reply by: xxFT13xx Date:8/28/2001 1:46:15 PM that sounds like a user problem. you should really upgrade your processor. it probably cant handle the 512 of ram you have. i have acid 3 and im using a Athlon 1gig with 512 ram and i have no problems..other than bog down when i layer on all my TONS of effects! -Sin
Subject:RE: Possibly a VERY serious bug in ACID 3.0b??? Reply by: spesimen Date:8/28/2001 2:08:41 PM after you run a render job does scandisk complain at all about the fat table being messed up? i frequently render out files in the 5-6 minute range and have had no problems, although that isn't quite 7 minutes. also, i generally use "save each track as a separate file". also, it sounds like you know whats up, but generally disk corruption stuff is happening at a lower level than an app. acid would have to try pretty hard to go in and mess up the fat when it is just opening and writing a file - it sounds like maybe your bios isn't happy or something. i had similar problems with an older bios rev on my mobo which was fixed with a newer release..
Subject:RE: Possibly a VERY serious bug in ACID 3.0b??? Reply by: jonah303 Date:8/29/2001 11:56:31 AM uh, i can make acid 2 write 0-byte filesizes on any of my .acd files. and this happened to me 3 or 4 times (after the first i started saving backups thankfully) without understanding why, but now i can reproduce that problem. i'm sure i could reproduce that in acid 3 as well. about rendering, i can make acid 3 give me an "unable to mix audio" error (or sometimes it does it randomly) when rendering.

Subject:Possibly a VERY serious bug in ACID 3.0b???

Posted by: JPThere

Date:8/28/2001 1:27:59 PM

Symptom: When rendering an entire song (~7 minutes) to a new file, 48Khz-24bit samples, the filesystem pointers are corrupted.

I run Windows98, PII 450MHZ, 4 hard drives (IDE), 512MB of RAM. Programs (ACID and Sound Forge amongst others) are on a separate physical hard disk, away from the data (.wav files).

After running a large rendering job using ACID3.0b (Render to new file), I am finding that pointers to .wav files associated with other ACID projects sitting on the same hard disk are being corrupted (ie: attempting to play one of these corrupted files yields playback of a portion of an MP3 files on the same physical disk.) Other symptoms are: an ACID project, as well as Sound Forge, cannot open a previously 'OK' .wav file due to a RIFF indicator being missing/corrupted. And in one case, a .acd file itself was corrupted.

The more times you run "Render to New File" (we're talking LONG files being rendered - around 7-minute songs), the more corrupted the disk becomes.

I have duplicated this on to separate physical disks. This did not seem to occur with ACID2.0. I cannot verify if it occurred with ACID3.0 build 189.

This could prove to be a nightmare for me if I find out that I cannot repair the corrupted ACID project file...

SF, have you heard of this problem?

BE SURE TO BACKUP BEFORE RENDERING LARGE FILES!!!

John

Subject:RE: Possibly a VERY serious bug in ACID 3.0b???

Reply by: xxFT13xx

Date:8/28/2001 1:46:15 PM

that sounds like a user problem. you should really upgrade your processor. it probably cant handle the 512 of ram you have.

i have acid 3 and im using a Athlon 1gig with 512 ram and i have no problems..other than bog down when i layer on all my TONS of effects!

-Sin

Subject:RE: Possibly a VERY serious bug in ACID 3.0b???

Reply by: spesimen

Date:8/28/2001 2:08:41 PM

after you run a render job does scandisk complain at all about the fat table being messed up?

i frequently render out files in the 5-6 minute range and have had no problems, although that isn't quite 7 minutes. also, i generally use "save each track as a separate file".

also, it sounds like you know whats up, but generally disk corruption stuff is happening at a lower level than an app. acid would have to try pretty hard to go in and mess up the fat when it is just opening and writing a file - it sounds like maybe your bios isn't happy or something. i had similar problems with an older bios rev on my mobo which was fixed with a newer release..

Subject:RE: Possibly a VERY serious bug in ACID 3.0b???

Reply by: jonah303

Date:8/29/2001 11:56:31 AM

uh, i can make acid 2 write 0-byte filesizes on any of my .acd files. and this happened to me 3 or 4 times (after the first i started saving backups thankfully) without understanding why, but now i can reproduce that problem. i'm sure i could reproduce that in acid 3 as well. about rendering, i can make acid 3 give me an "unable to mix audio" error (or sometimes it does it randomly) when rendering.