Skip to main content
W
warrenp36209625
Inspiring
January 23, 2018
Answered

Audition update 11.0.1.49 problems

  • January 23, 2018
  • 6 replies
  • 8203 views

Anyone else having problems scanning existing/loading VST plugins after the latest Audition update? All Waves plugs status shows "Not working" and won't reload, also can't "enable" them either.... Ozone and Neutron VST3 also the same problem... Thanks for any help!!

This topic has been closed for replies.
Correct answer warrenp36209625

Hi guys

Just a heads up, last night iZotope updated some their software, but the latest VST3 updates still don't load in AA.

VST versions are still functioning...

w


Adobe Audition has now released Version 11.0.2.2

Updated this morning and all VST3's loaded without problem.

Thanks to the Audition team for everything!

6 replies

E
emmrecs
Brainiac
February 14, 2018

Thanks also from me!

    Jeremy Ryan
    Jeremy Ryan
    Participating Frequently
    February 13, 2018

    I was having the same VST3 issues with v11.0.1.49.  After several hours of troubleshooting with iZotope, I stumbled upon this thread.  I can confirm that the update v11.0.2.2 solved the problem for me too!  Thank you Adobe.

      DGolf
      DGolf
      Known Participant
      January 25, 2018

      Just thought I'd chime in and let all you Audition guys know that these same VST3 problems are affecting Premiere Pro CC 12.01. And that the workaround, though functional, has meant recreating tons of mix parameters for my current client projects.

      I thought the days of being wary about Adobe updates were behind us ...

        W
        warrenp36209625Author
        Inspiring
        January 27, 2018

        Agreed, that workaround would only mean a huge amount of retweaking!!!

        demodave
        demodave
        Participating Frequently
        January 24, 2018

        I updated Audition this morning and lost the ability to use Izotope Nectar 2 as a VST3 plugin.  I am reverting Audition to an older version and will follow this thread to see what happens.

          W
          warrenp36209625Author
          Inspiring
          January 24, 2018

          demodave  wrote

          I updated Audition this morning and lost the ability to use Izotope Nectar 2 as a VST3 plugin.  I am reverting Audition to an older version and will follow this thread to see what happens.

          Let us know how you get on!

          All my iZotope VST3 have stopped working!

          Charles VW
          Charles VW
          Inspiring
          January 24, 2018

          Thanks everyone for reporting the issue. We're investigating.  At this point, there doesn't look to be a workaround other than to use the VST2 or AudioUnits plug-in version (if available), or to use a previous version of Audition.  We'll post more information when available.

            Charles VW
            Charles VW
            Inspiring
            January 25, 2018

            Update:

            From our testing, it looks like only certain iZotope VST3 plug-ins and at least one VST3 from Waves are affected. We changed the way we initialize a VST3 plug-in in order to fix a bug for a plug-in from a different vendor. The change was within the VST3 specification, but it turns out there are certain plug-ins which have issues with being initialized in this different way.

            If you're crashing when loading a pre-existing session (Audition), or a pre-existing project (Premiere Pro), you can launch and manually trigger an audio plug-in scan. Instructions below.

            Audition:

            1. Launch Audition
            2. Effects > Audio Plug-In Manager...
            3. Check the "Res-can existing plug-ins" checkbox
            4. Press the "Scan for Plug-Ins" button

            Premiere Pro:

            1. Launch Premiere Pro
            2. Open a project which doesn't have these plug-ins, or create a new project
            3. Navigate to the Effects tab.
            4. Open the fly-out menu for that tab, choose Audio Plug-In Manager...
            5. Check the "Res-can existing plug-ins" checkbox
            6. Press the "Scan for Plug-Ins" button

            Following these steps will re-scan all audio plug-ins, and the ones which are crashing will be labeled as "Not Working" and be skipped. You can then open your previous Session or Project, and swap them out with a different plug-in, or in some cases, the same plug-in but with a different plug-in architecture (e.g. AudioUnits or VST). Only VST3 is affected.

            E
            emmrecs
            Brainiac
            January 25, 2018

            Hi Charles, I just had a thought - maybe there is a bug related to iLok? I know nothing about coding so maybe totally off the mark lol

            W


            warrenp36209625  wrote

            Hi Charles, I just had a thought - maybe there is a bug related to iLok? I know nothing about coding so maybe totally off the mark lol

            W

            But I don't use iLok!  So I fear it's not that!

            And the "workaround" is exactly that!  AA is not only crashing when loading a pre-existing session with those VST3s, but also with any new session if one tries to insert one of the now-"troublesome" plugs!  Is it reasonable to enquire which was the vendor and plug-in whose previous problem(s) led to the changes made in AA to its VST3 initialisation?  Was this only one plug-in?  If so, one "problem" has been corrected, only to create several more!

            E
            emmrecs
            Brainiac
            January 23, 2018

            Yes, similar problems here!

            I don't have any Waves plugins and all my existing plugins show as "Working" in the Plug in Manager screen but Ozone and Neutron VST3s both cause AA to crash, VST2s seem to load and work properly.  I haven't yet had time or opportunity to check through every one of my plug ins, and I remember that when (?)Ozone 8 was released by iZotope there was information on their website that AA was no longer "supported", I think.  However, everything worked as expected prior to this latest AA CC update.

            I'm seriously considering reverting to the previous version, since I have at least one customized rack preset based on the VST3 version of Ozone Advanced and RX6 Advanced.

            W
            warrenp36209625Author
            Inspiring
            January 23, 2018

            I actually uninstalled the latest Audition update, restarted and reinstalled the previous version, did the same with Waves (apart from reverting to previous version which you can't) So i'm guessing there's a potential problem with the newest Waves 9.92...  ho hum....

            E
            emmrecs
            Brainiac
            January 23, 2018

            warrenp36209625  wrote

            I actually uninstalled the latest Audition update, restarted and reinstalled the previous version, did the same with Waves (apart from reverting to previous version which you can't) So i'm guessing there's a potential problem with the newest Waves 9.92...  ho hum....

            Did the reversion to previous version solve the problem of your plugins other than Waves not working?

            Since, in my case, attempting to insert Ozone 8 and/or Neutron caused AA to crash I have sent the crash reports and details to audbugs, as per this FAQ.

            Terms & ConditionsAccessibility statement
            Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices