The 6025 runtime errror...is the problem AA or my PC?

Occasionally a glitch occurs within AA, freezing it, then causing me to restart the program.  Upon restarting I receive the prompt to continue what I was working on or delete the existing session and start anew - but when I choose to continue the session I'll come up with a 6025 runtime error which will not allow me to continue the session, losing all data.  Prior to that I even removed the audition_settings icon but that didn't help.  Last night I lost a night's recording due to no other option than to reinstall AA.  This glitch occurs seldom, but I'd hate to be in the middle of a great take and have this happen.

Is this a problem with AA, or my PC?  Does anyone know how to remedy this problem? 

Hmmm, with no takers on this so far I'll just conjecture the obvious and state that the problem is the combination of AA2 with whatever else you have on your PC.  How about some details on your hardware and any non-AA effects loaded on your system, particularly if they're VST.  Plus, what were you using in the sessions that crash?

No, this is not normal.

When I had as nearly as possible the same problem with CE2000 (yes, I know it's not the same at all), it was cured by a soundcard driver update - but fine tuning of buffer sizes reduced the problem until then.  What soundcard are you using?

Paul

I don't have AA 2.0, but have experienced a similar problem with AA 1.5. pwhodges alluded to buffer settings...that might be it. Try adjusting all your buffers to their default settings. The default settings are contained in the AA help files.   

Error 6025 is produced when the Audition/CoolEdit is communication with an incompatible VST or DirectX effect.  In every case, we have tracked down the 3rd party effect and were able to reproduce the crash or other bad problems in other audio software (competitor software) as well.  We normally try to add incompatible  3rd party effects to our list of banned DX effects and not let them be used, but new ones are always released after we ship the product and they don't make it on the banned list. 

So check all the DX and VST plugins that you are using in your session and try to figure out which one caused the problem.

A voice of Authority has spoken!  Pedal Steel, where are you?

(Thank you, Nariman!)

you don't have to yell .... sorry..

Thanks Nariman.  I plead ignorance on this situation and trust your wise sounding words.  I'm using the soundcard that came with my pc (a gateway 3 ghz, 3gb ram).  would it be better to get a higher quality soundcard?  I am using a firepod, so I think I'm bypassing the soundcard right now, right?

Anyway, the only plugin I'm using now is the BBE plugin, which worked fine with the previous versions of AA (is that on the banned list?).  I'm thinking of getting the uad project pak.  I hope this will work with AA.

I plead ignorance on this situation and trust your wise sounding words. 

We're talking Audition development team here... it's always good to hear from him, but it doesn't happen too often, so...

I'm using the soundcard that came with my pc (a gateway 3 ghz, 3gb ram).  would it be better to get a higher quality soundcard?  I am using a firepod, so I think I'm bypassing the soundcard right now, right?

Not exactly bypassing, but you are certainly ignoring the internal sound as long as it's not selected. Is it an actual soundcard, or motherboard sound (AC '97 style)? If it's motherboard-based then the best thing to do is turn it off anyway - preferably in the BIOS, as far as I'm concerned!

Anyway, the only plugin I'm using now is the BBE plugin, which worked fine with the previous versions of AA (is that on the banned list?).  I'm thinking of getting the uad project pak.  I hope this will work with AA.

BBE shouldn't be on the banned list, AFAIK. There is another possibility though, and it's something that has happened to at least one user that I'm aware of recently. The AA2.0 effects are now by and large VST effects too, and they can quite easily corrupt themselves. So, if you end up with an internal effect that's corrupted, this could easily cause the same error to occur. The only solution at this point (and if it happens again, I'd definitely try this) is to reinstall Audition.

In principle, there shouldn't be a problem with UAD, but you always have to bear in mind with SW using dedicated hardware that everything has to co-exist happily in your machine and run at the same time, and that there have certainly been issues with some DSP-based systems in the past. The only way to have any real degree of confidence is to hear from an existing user - any takers?

Error 6025 is produced when the Audition/CoolEdit is communication with an incompatible VST or DirectX effect.  In every case, we have tracked down the 3rd party effect and were able to reproduce the crash or other bad problems in other audio software (competitor software) as well.  We normally try to add incompatible  3rd party effects to our list of banned DX effects and not let them be used, but new ones are always released after we ship the product and they don't make it on the banned list.  So check all the DX and VST plugins that you are using in your session and try to figure out which one caused the problem. 

Checked AA 2.0 Edit view / Effects / Add remove VST Directory

Saw Adobe 6.5 plugin. Removed it from the AA 2.0 list.
Refreshed
Can't burn CD's with AA 2.0
Pure virtual function Error 6025

What does Nariman have to say about this?

Liquid, please stop cross posting. This is the fourth thread you are posting the same problem in. I'm trying to help you in one of the other four.

By the way: did you try the suggestions from Nariman and SteveG in this post, and/or my suggestions in the other post in this forum?

Took Nariman's suggestion here:  Removed Adobe 6.5 plugin from the AA 2.0 list.

Didn't help at all.

Brewer, are you having problems? You've been super active recently and I guess you're looking to get recording but are hitting a brick wall. About burning, did you try the aspi repair file which some of the guys have used to their benefit. There is also an extensive list of suggestions here

Hope this helps