6.0b Crash when rendering to new track -ACID Product Family

Subject:6.0b Crash when rendering to new track Posted by: nutrapuppy Date:8/18/2006 12:14:25 PM I have been experiencing crashes when rendering to a new track. It seems to happen particularly when soloing and rendering a VSTi part to a new audio track, but that may be because that is where I am concentrating my production right now. The problem started about a week ago, (around the time I updated to 6.0b?) and the frequency of these crashes seems to be increasing as my deadline draws near. :-\| It just happened again. Usually I have been getting the "Acid has encountered a problem and needs to close" followed by the "Rewire DLL error" message. However, this time I got a new error message telling me my system is low on memory. I immedately opened Task Manager to check resources, and though Acid was still "running", I had the vast majority of my system resources available. This particular .acd project is not yet very complex by my normal standards but I do have a bunch of one shots, some disk tracks, NI's FM7 and KOntakt loaded. Is anyone else experiencing this? Any suggestions about chasing down this problem? Message last edited on8/18/2006 12:16:11 PM bynutrapuppy.
Subject:RE: 6.0b Crash when rendering to new track Reply by: nutrapuppy Date:8/18/2006 2:54:58 PM Problem solved. Apparently the problem was caused by using db audioware FX on some unused, muted tracks. I deleted those tracks and the problem went away. Beware of using non sony track optimized effects on individual tracks.
Subject:RE: 6.0b Crash when rendering to new track Reply by: pwppch Date:8/18/2006 3:07:56 PM Which FX from db audioware are you using? Peter
Subject:RE: 6.0b Crash when rendering to new track Reply by: nutrapuppy Date:8/18/2006 6:50:02 PM I was using a ton effects the Quantum package on a kick drum for a special effect transition. ChainSaw, Classic Multiband, Gateverb, Touch Sensitive Flanger, Sweeping Overdrive, and Overdrive Doubler. I know, it looks silly to have that much processing on a track, but it was working fine. The only problem I had was when rendering other, soloed midi tracks to a new track.

Subject:6.0b Crash when rendering to new track

Posted by: nutrapuppy

Date:8/18/2006 12:14:25 PM

I have been experiencing crashes when rendering to a new track. It seems to happen particularly when soloing and rendering a VSTi part to a new audio track, but that may be because that is where I am concentrating my production right now. The problem started about a week ago, (around the time I updated to 6.0b?) and the frequency of these crashes seems to be increasing as my deadline draws near. :-|
It just happened again. Usually I have been getting the "Acid has encountered a problem and needs to close" followed by the "Rewire DLL error" message. However, this time I got a new error message telling me my system is low on memory. I immedately opened Task Manager to check resources, and though Acid was still "running", I had the vast majority of my system resources available. This particular .acd project is not yet very complex by my normal standards but I do have a bunch of one shots, some disk tracks, NI's FM7 and KOntakt loaded.

Is anyone else experiencing this? Any suggestions about chasing down this problem?

Message last edited on8/18/2006 12:16:11 PM bynutrapuppy.

Subject:RE: 6.0b Crash when rendering to new track

Reply by: nutrapuppy

Date:8/18/2006 2:54:58 PM

Problem solved. Apparently the problem was caused by using db audioware FX on some unused, muted tracks. I deleted those tracks and the problem went away.
Beware of using non sony track optimized effects on individual tracks.

Subject:RE: 6.0b Crash when rendering to new track

Reply by: pwppch

Date:8/18/2006 3:07:56 PM

Which FX from db audioware are you using?

Peter

Subject:RE: 6.0b Crash when rendering to new track

Reply by: nutrapuppy

Date:8/18/2006 6:50:02 PM

I was using a ton effects the Quantum package on a kick drum for a special effect transition.

ChainSaw, Classic Multiband, Gateverb, Touch Sensitive Flanger, Sweeping Overdrive, and Overdrive Doubler.

I know, it looks silly to have that much processing on a track, but it was working fine. The only problem I had was when rendering other, soloed midi tracks to a new track.