Acid4.0a having serious save problems -ACID Product Family

Subject:Acid4.0a having serious save problems Posted by: clarksil Date:10/18/2002 9:54:25 AM This has happened a few times where I'll have maybe 5-7 audio tracks and 1-2 VSTi soft synth midi tracks, and when I do a save, all of a sudden the acd file balloons up to 20 times the size that it should, and then when trying to reopen the project, I get an error message, crash and the program has to be closed. Basically the acd file becomes corrupted somehow and becomes useless, hence I have to completely start the project over again. It happened last night after 3 hours of work!!!! Luckily I had a previous backup so I didn't have to completely start over. This should NOT be happening!!! P2 400, 512 M ram, 20 bit Layla, EZbus, Win ME Also getting sporadic crashes where it may work fine in the morning, but crash again in the afternoon. Very strange!!!! I could list much more, but I am finding some work arounds, but with a program of this stature, this should not have to be done.
Subject:RE: Acid4.0a having serious save problems Reply by: pwppch Date:10/18/2002 11:50:58 AM What VSTis are you using in this huge project? There are some VSTis that save their entire sample memory when we ask them to save thier state in the project. This can get HUGE real fast. This exposed a bug in ACID's project loading code that would cause ACID to crash on load of such projects. This bug has been fixed, but currently there is no work around other than to avoid VSTis that save like this. Peter
Subject:RE: Acid4.0a having serious save problems Reply by: SonyNateM Date:10/18/2002 12:31:20 PM clarksil, Which VSTi's are you using? This could be related to a specific VST instrument (possibly the CM-404? This instrument dumps a ton of information into the ACD when saving it's bank). Currently, depending on the amount of sample data it chooses to save, this can cause problems when reopening the file. This will be fixed with 4.0b, but it's probably safest to avoid using this VSTi until the update is available. Hope this helps, Nate

Subject:Acid4.0a having serious save problems

Posted by: clarksil

Date:10/18/2002 9:54:25 AM

This has happened a few times where I'll have maybe 5-7 audio tracks and 1-2 VSTi soft synth midi tracks, and when I do a save, all of a sudden the acd file balloons up to 20 times the size that it should, and then when trying to reopen the project, I get an error message, crash and the program has to be closed. Basically the acd file becomes corrupted somehow and becomes useless, hence I have to completely start the project over again. It happened last night after 3 hours of work!!!! Luckily I had a previous backup so I didn't have to completely start over. This should NOT be happening!!!
P2 400, 512 M ram, 20 bit Layla, EZbus, Win ME
Also getting sporadic crashes where it may work fine in the morning, but crash again in the afternoon. Very strange!!!! I could list much more, but I am finding some work arounds, but with a program of this stature, this should not have to be done.

Subject:RE: Acid4.0a having serious save problems

Reply by: pwppch

Date:10/18/2002 11:50:58 AM

What VSTis are you using in this huge project?

There are some VSTis that save their entire sample memory when we ask them to save thier state in the project. This can get HUGE real fast.

This exposed a bug in ACID's project loading code that would cause ACID to crash on load of such projects. This bug has been fixed, but currently there is no work around other than to avoid VSTis that save like this.

Peter

Subject:RE: Acid4.0a having serious save problems

Reply by: SonyNateM

Date:10/18/2002 12:31:20 PM

clarksil,

Which VSTi's are you using? This could be related to a specific VST instrument (possibly the CM-404? This instrument dumps a ton of information into the ACD when saving it's bank). Currently, depending on the amount of sample data it chooses to save, this can cause problems when reopening the file. This will be fixed with 4.0b, but it's probably safest to avoid using this VSTi until the update is available.

Hope this helps,
Nate