Adobe Audition 3.0 crashes in multitrack when attempting to play

Report · Mar 08, 2019

I can no longer play files in multitrack. I don't know why.

I'm using Windows 10, Adobe Audition 3.0, ASIO4ALL v2 driver and it has worked in the past.

Any ideas?

This is the screen I see when I press play.

Report · Mar 08, 2019

Does it still play audio files OK in the waveform Edit view? has Windows 10 done an update since AA3 last worked?

Report · Apr 10, 2020

Same issue. Just started this week. Random, in the middle of working in multitrack and hitting playback, popup error (same as image), crash. I also get a message right before that stating my audio driver is being used elsewhere and is unavailable (motu 24io). P.S I also installed the 3.0.1 update, same issue. I was recently running it in Winodws 7 compatibility mode but now all the modes have the same issue.

Report · Apr 11, 2020

This can happen if, for some reason, system sounds get turned back on. They will grab your sound device, and often reset the sample rate too, so that when you get the sound device back, your audio plays at the wrong speed. Look at that for a start...

Report · Apr 11, 2020

Hey thanks for the input, appreciated!

What I have done so far (and it seems to have worked at this point):

Installed the 3.0.1 update
Backed up and then removed the entire /users/(username)/AppData(hidden folder)/Roaming/adobe/audition/3.0 folder (IMPORTANT TO BACKUP CERTAIN FILES IN THAT FOLDER IF YOU HAVE CUSTOM EFFECTS, RACKS, SETUP, ETC)
Re-installed (repair install) the audio device drivers and software
Restarted Audition so it would rebuild the folder I deleted
Closed Audition and copied back the files pertaining to custom stuff

It seems to be working. I had seen a youtube suggesting the removal of the folder due to corruption issues. Maybe that did it, or it could be that reinstalling the device drivers/software changed the setting back from what you described. Either way its rolling and I will check back here in a few to follow up.

Thanks again Steve.

Report · Apr 18, 2020

Well, follow-up. The Software is still doing the same thing. On a 12 track song that has worked previously for years, playback sits for a good 15 seconds and then returns with a ," The currently selected audio device is not available. Another application may be using the same driver". If I try again I get either the Microsoft Visual C++ runtime error, "The application has requested it to terminate in an unusual way. Please contact the application support team for more information" or the "Audition has encountered an error. [\premiere2.0\MediaLayer\Src\Audio\AsioHost.cpp-635]" error. To recap, I have tried all the different compatibility settings, Uninstalled and reinstalled, deleted settings, shutoff system sounds, reinstalled audio hardware and drivers.

Bunk.I'm hoping I don't lose the ability to access all of the work I've done for the past 5 years.

Report · Apr 19, 2020

Do you have Premiere2.0 installed on your system? It looks very much like it's trying to steal the same ASIO channel that Audition is using...

Report · Apr 22, 2020

I noticed that as well. I have Adobe Design Premium (CS5.5) but other than that no, I do not have any other Adobe products other than Acrobat Reader. Additionally, I do not have folders anywhere named "premier2.0" or "MediaLayer", nor was "premier2.0" listed anywhere in the registry.

I am somewhat stable now other than a weird side effect (more on that below). What I did:

Removed the latest C++ runtime library update (dated 3/1 I believe).
Turned back on some vst dlls I had previously turned off

I don't think the C++ rollback was the deal. I think it was that I had turned off some VST libraries (DtBlkFx.dll, libffw3f-3.dll) that maybe were being used in some sessions? Anyway, have yet to have those specific errors since the two changes.

The side effect has been that periodically Audition is choosing not to playback a random track. This is after it has been played back many times in the session. Audition just stops playing it back, even in solo. It does however play it in edit mode.

Restarting the DAW clears the issue (session saved or unsaved) but it eventually comes up again spontaneously, and on a different track/file. Crazy.

Lastly, thank you so much again for the assistance.