What the heck could possibly be going on? Anyone have any ideas? I've attached the error log file that is generated by the error but I doubt it will be of much help.
Actually, there might be a clue there - the logfile is listing everything it does in terms of scanning plugins during startup - and there are an awful lot of those. If one that Audition deems necessary to operate fails (even though you don't want to use it) then the startup will fail.
What we don't get a clue about is why it will start from the extended toolkit - unless this is correctly opening whatever it is before Audition trys to.
But what that means is that it probably isn't Audition itself that's failed - it's something to do with the install state of something it accesses during startup.
Thanks. Yes, I do have a lot of plug-ins, many of them Waves professional plug-ins. You gave me an idea actually. Later tonight when I have some time, I'm going to start Audition using the work-around with the extended toolkit, then once it's open, I'm going to disable all my plug-ins (can't remember how to do that but I'm sure it won't be difficult) then close it, then try to re-open it. If I'm very lucky, it will start, then I can somewhat systematically add the plug-ins back until one causes the restart to fail. Sounds like a plan. Weird though...I swear nothing changed on the computer and my other pro audio apps don't complain about anything on startup. Oh well. I guess I'll know more later.
I opened Audition using the work-around of starting the ExtendScript Toolkit first, then removed the VST folder that has all my VST effects (Effects, Add/Remove VST Directory...). When I closed it and tried to restart it, I got the same error. I've attached the new log file but it looks pretty close to the first log file I attached to me.
I'm not aware of any way to disable DirectX effects from within Audition, so I can't test that option, although I highly doubt it would matter since as I've stated, none of my effects have changed, all my other pro audio apps work the same with these effects, and I've been using this installation of Audtion on this computer for a year before this problem suddenly cropped up about a week ago.
One more bit of information for what it's worth. Everytime I try the work-around of using the ExtendScript Toolkit to launch Audition, after it succesfully starts, I get an error dialogue from the ExtendScript Toolkit that says "Cannot connect to target Adobe Audition 2.0!" I'm not sure if that provides another clue or not.
250_appcompat.txt 221.4 K
stevefoobar2: I may have found a solution for you.
I had the same thing happen to me today. I was using Audition 2 this morning without any problems. But this afternoon, it started giving me the exact same error with no apparent reason. Nothing on my system had changed.
So I uninstalled it and installed Audition 3 in its place. Audition 3 continued to have the same problem that Audition 2 had, so we can assume that this is not something that was changed between versions.
But my attention was brought to the fact that you and I are both running Windows XP SP3 fully up-to-date. So I thought I'd try seeing it from the angle of a problem with Windows instead of Audition, and see if I didn't get a better result -
First, I logged on to Windows as Administrator. This may or may not be required, but you'll probably want to do it just in case (you'll see what I mean later). At this point, Audition still crashed the same way when I opened it, so I moved on to my next troubleshooting strategy -
Instead of opening Audition directly, I right-clicked the Audition icon and selected "Run as..." This may seem odd since I was already logged in as Administrator, but it proved to be the solution in my case.
In the "Run As" diolog, there are two main options: run as current user, or run as another user.
Since I was already logged in as Administrator, I could safely select the first option (run as current user). But here's the catch: selecting the first option allowed me to UNcheck the box underneath that says "Protect my computer and data from unauthorized program activity" (see the attached picture)
Audition opened without any problems when I did this.
This makes me think that one of the Windows security features suddenly decided to block something that Audition was trying to do, crashing the program in the process. By turning off this security feature, the problem was solved. And I only had to do it once. Every time afterwards, Audition has opened without any problems when I simply open it from my desktop. Perhaps Windows now remembers not to block Audition in the future.
However, I have not restarted my computer yet, or logged off as Administrator. You may need to tweak this solution if you plan to do either of these things. You may end up having to "Run as" Audition every time you restart your computer or log off. You may even need to select the SECOND option, and run the program as Administrator with the appropriate password.
Anyway, this was the only post I could find on Adobe.com concerning this problem, so I thought I'd post my solution in case it helped someone else.
Run As - XP SP3.jpg 29.3 K
I have to say that anybody using Audition 2 is strongly advised to upgrade to 3.0.1 - it's a whole lot more stable, and with additional useful features. And Audition always runs most sensibly when you are logged on with Administrator privileges.
Also, it's been noted in several places that Windows updates have done a lot of weird things lately to all sorts of software that used to run fine, and suddenly doesn't. Generally though, when M$ screw something up, they end up fixing it pretty quickly, because they get a lot of complaints. So it's now unfortunately the case that you have to run Windows Update (and we found that one of the more important things to do was to make sure that the .NET framework was up to date) quite frequently if you run it at all. The only alternative is to get a stable system, use it as such and don't run any updates on it ever. The best solution with a dedicated DAW is in fact the latter, and simply don't ever connect it to the internet. But it's not an ideal solution, because of things like online software authentication. FWIW, I think that most people in this situation only connect when they absolutely have to, and always behind a good firewall. Whatever you do, don't use the machine for internet browsing, though!
Thanks Giffyguy. I'm glad this worked for you. In my case, I ended up completely uninstalling Audition then manually editing the registry to make sure there were no Audition entries left. I then rebooted and reinstalled the application and this time, it works normally.
I'm not sure why or if this is related to what you found or Windows XP Pro SP3 updates, but it's likely.
Thanks for the detailed steps you took. I may need them if this starts happening again!
I am having the same issue, except I am using Audition 3.
The error msg reads:
AppName: audition.exe AppVer: 2.0.5306.2 ModName: unknown
ModVer: 0.0.0.0 Offset: 6c694620
I tried the Run As solution that was posted here, but no joy. In fact, I can't even uninstall and
reinstall Audition because the process halts with a message that the
components.msi in the Windows folder is missing or bad.
I'm running this on a Sony Viao VGC-RC219G with Windows XP SP3.