Audition 2017 crashes when applying Effects Rack containing Waves plugins

[AlanFlint]

Hi,

I have used a small number of Waves plugins for some time, and they have always worked well with previous versions of Adobe Audition and Adobe Audition CC. However, AA CC 2017 has crashed several times this afternoon when trying to apply the Effects Rack.

The message that popped up was:

"Adobe Audition CC 2017.0 has stopped working

A problem caused the program to stop working correctly. Windows will close the program and notify you is a solution is available."

The 'Apply' process gets to 99% then stops working as described in the pop-up error message.

Does anyone have any ideas why this problem might have started to occur, if so, what do I need to do?

Regards,

Alan

[Jari Lampila]

I have used Izotope plugins with Adobe Audition CC without any problems. After the latest update I haven't been able to open some earlier made projects, I get the same message as Alan did and Audition crashes.

After some research I found that problem was with Izotope Ozone 5 which is a mastering tool. Audition CC doesn't work with it at all any more, it crashes immidiately every time I try to use Ozone 5 with it. I cannot call this an improvement and will probably stop using Audition if this problem will not be fixed.

Wishes,

Jari

[ryclark]

See the FAQs Audition Crashed. Now what? Following instructions is the only way that the developers of Audition get to see what went wrong and to offer possible cures.

[AlanFlint]

Hi,

I have followed the steps in Audition Crashes - Now What? Due to the amount of feedback they will be getting I am not anticipating that Adobe will reply anytime soon.

In the meantime I have again tried quite a number to times with trying to apply variations of the Effects Rack with several Waves plugins, and unfortunately still the same result ...... it gets to 99% and crashes

If anyone else has any bright ideas I would very much like to know. The plugins worked very well in previous versions of AA CC.

Regards,

Alan

[AlanFlint]

Just a thought .... if this cannot be solved soon, or an answer found that helps with the problem, is there any way of temporarily 'rolling back to AA CC 2016? That worked fine!

Regards,

Alan

[ryclark]

Yes you should able to roll back to Audition CC2106 with no problem. Open the Adobe Creative Cloud app, go to Apps and click on Latest Versions. A drop down should appear showing Previous Versions. From there you should be able to re-install CC 2016.

[AlanFlint]

I just tried that, but could not see AA CC  2016. Would I have to uninstall AA CC 2017 first?

Regards,

Alan

[ryclark · Accepted solution]

No I don't think so. I believe that it should install alongside CC2017. I have them both installed at the moment so that I can check differences between them.

Hopefully one of the Developers might chime in here with any comments about Waves plugins. Are you using the VST or VST3 versions of the plugins?

[AlanFlint]

When I upgraded to AA CC 2017 it noted that I had an older version installed and as part of the process uninstalled the old version AA CC 2015 (not 2016 as I have said before - my mistake!).

The Waves plugins I use appear in the lists of both VST and VST 3.

Many thanks for your help and advice!

Regards,

Alan

[AlanFlint]

Hi,

I just thought that I should let you know, and anyone else that might be following this thread, that I have now managed to fathom out how to download and re-install the previous version of AA CC 2015. It is now installed, and available alongside AA CC 2017.

I have just tried editing one of our sermon recordings, and thankfully when I applied the Effects Rack containing my usual Waves plugins, everything worked fine (once I had reconfigured the plugin settings).

We seem now to be back to normal and working okay.

It would be useful however, if Adobe Support see this thread (or similar) and take note for when they do the next interim AA CC update.

Once again, very many thanks for your help.

Regards,

Alan

[ryclark]

Just to help others in the same situation how did you manage to download and re-install AA CC2015 please?

[AlanFlint]

In answer to what did I do to install previous version, note below:

I did a search - found the following link, and followed its instructions:

How to Find and Install Previous Version of Adobe Apps in CC 2015 | Adobe Customer Care Team

I then followed the sequence:

1: Open Creative Cloud Desktop App

2: Clicked Find Additional Apps & Selected 'All Apps'

3: Select View Previous Versions

4: Select Desired App (i.e. Adobe Audition CC)

5: Click Install - From Dropdown Menu Choose Required Version (i.e. Audition CC 2015.2)

That's more or less what I did, and as I said it worked ok.

I hope that helps

Regards,

Alan

[Paul_Ferguson]

Hi Alan

I'm using half a dozen Waves plugins on CC 2017, and I haven't had any problems with them.  Win7SP1 64-bit.

[AlanFlint]

Hi Paul,

In response to your first message my laptop uses a Windows 10 64-bit OS.

I generally use the following Waves Plugins to edit the spoken word (i.e. church sermons):

Renaissance Compressor

Renaissance DeEsser

Renaissance Equalizer

MaxxVolume

As fas as the Update Plan is concerned, I fear it may have expired, although I did purchase the individual plugins at different times. I suppose the correct thing to do would be to contact Waves and ascertain the situation. Having said that, if the cost is anything like the $200 - $300 there is no way that I could afford that - unfortunately!

I do appreciate your comments and interest.

Many thanks,

Alan

[Paul_Ferguson]

The reason I asked was because I was wondering if for some reason, updated Waves plugins might not be playing nicely with Audition.  I don't have the WUP, so all my Waves stuff is as I bought it, that is, not updated.

[Paul_Ferguson]

Alan, a question:  Do you subscribe to the Waves Update Plan?

[coastalmedia]

I have this exact same problem.

Very frustrating, considering a $60 copy of REAPER seems never to have an issue.

But then again, Adobe get's our money anyway via subscription, so who cares if the software actually works, right?

[Paul_Ferguson]

I've been around here long enough to know that the Audition developers work very hard at making the program work as well as it can for as many people as it can.  For that reason, I have two things to say to you:

* My Waves plugins are working inside Audition fine on my machine.

* Your cynical, sarcastic comment is way out of line.

[coastalmedia]

Hi Paul,

My cynicism comes from 8 hours a day, 5 days a week full-time, professional use of these products.

I have deadlines to work to.

I have clients to answer to.

I have television networks to answer to.
Every update costs me time, money and to a level some of my personal wellbeing dealing with the problem..

I have a right to my frustration at Adobe's updates - they almost ALWAYS get released with bugs and second rate issues.
In terms of reliability, Adobe software hasn't been the same since CS6.

Yesterday, I bit the bullet and installed Reaper DAW on my machine. I struggled applying an Rcompressor and WLM meter to a very simple 15 second 48,000 32bit WAV file for about 45 minutes with Audition. Hardly an intensive task.

I had my solution within 4 minutes of installing Reaper. An OPEN SOURCE PIECE OF SOFTWARE.

I'm very sorry that you feel I am out of line, but I am very much in line. I am a paying customer. I am a professional user. The fact that the company I pay money EVERY MONTH to for the use of their product has been outdone by a $60. piece of open source software is a really big problem.

It's comical your response in a way, before updating Audition I had no issues.
Yet somehow you've implied that this is my issue.

Like I should have to investigate, un-install, re-install, trash preferences, trash user settings - just to make a piece of software I pay good money for to work, work...

[Paul_Ferguson]

"...so who cares if the software actually works, right?"

Like I said before, my experience is that the Audition team care very much and work hard to make the software as good as it can be.  That's why your comment was out of line: it's rude, and it's incorrect.  It's really crummy that you're having a seriously bad time with Audition right now, and I know how computers can give you a world of grief sometimes.  But that doesn't give you the right to dish out cheap shots like you did.  *That* was out of line.

[coastalmedia]

I'd probably agree with you if it was just Audition, however since Creative Cloud became a thing we have had nothing but issue after issue with Adobe software, mainly Premiere - however After Effects and Audition have their moments too. There are many that share the same point of view with the subscription model.

I expect better for my money, at the end of the day it's not my problem how hard they try or how much they care - it's what they deliver. They'll still happily take my money each month bugs and all, after all.

[nv_audio]

It's not just the Waves plugins that make Audition crash.

I experience it a lot whenever I try to batch process more than 20 files. For instance, I've made a couple of batch processing presets that I use for inserting silence at the beginning and end of files. Whenever I try to batch process more than 20 files at a time Audition crashes as soon as it reaches 99%.

I've experienced this on four different computers now.

There is a quick fix for the effect rack crash though. It's not super optimal, but it works:

If you save your effect rack before applying, you can quit Audition, reopen your project, find your new effect rack preset on the list and then apply it. Now Audition won't crash if you apply the effect rack. You can also change the settings of your plugins, and apply it and it still won't crash. I hope this helps just a tiny bit

[miken55041547]

That did work for a while, now its doing the same thing.  Crashing over and again.  I have to say I see tons of simple programs that do more than the adobe subscription product.  The shame is that adobe has some seriously magic features.  Maybe one day they will be kind and hire a developer per product to just read through these forums.

I mean PS cant even open all jpegs, premier cant handle .mkv's.  This is silly that the most valuable property on earth is poking its users in the eye, and granted, tough to catch.  Frustrate enough people and they will find alternatives.

[r2-no-d2]

Why did you notice this problem solved?

Reinstall the old version is not the solution!

Now the СС2018 and Audition also does not work with same VST plugins!

No one form Adobe has dealt with this problem since the 2017 version!

[Peferling]

This is why you should keep old versions installed, to keep old plugins functional and for the sake of projects that may occasionally need updating without having to start over from scratch.  Been doing this for over thirty years.  Every shop/firm/agency I've dealt with know this and keeps old versions for compatibility reasons.   The trick is make sure that the new update does not uninstall the old. In extreme cases, some will even set up dedicated machines to avoid compatibility issues. A time machine in that sense. 

In short, if you wish to play with older VST plugins, then you need to stick with the same playpen in which they reside.