Skip to main content
M
madcowzack
Participant
February 9, 2018
Question

Plug In Manager Not Scanning ...

  • February 9, 2018
  • 4 replies
  • 6690 views

Using CS6 V. 5.0.2, build 5 on a Mac Mini (Late 2014), 2.6 GHz Intel Core i5, MacOS High Sierra 10.13.3, 8 GB Ram.

I bought two new plug-ins from Waves ... and when I went to scan for them, the Audio Plug-In Manager didn't do anything - it brought up the "scanning" window, but it just sat there. And now, I have NO plug-ins, whatsoever. Not even the basic ones that come with the program. I've reset the scanning folder options to "default," and unchecked the "rescan" option ... nada. It sits at 0% and eventually crashes.

(All Waves Plugins are all working fine on Audacity, ironically enough.)

    This topic has been closed for replies.

    4 replies

    J
    Joel Moors
    Participant
    March 1, 2018

    Same problem here - CS6 v.5.0.2 build 5 under High Sierra and the plugin scan just fails or crashes out of Audition.

    B
    booch_21
    Participant
    February 28, 2018

    Following this thread.  I have been running CS6.5 on my iMac (High Sierra) and have been successfully running Izotope RX6 and Izotope Nectar.  I tried adding a simple plug-in and now it has wiped out all of my added plug-in's and freezes on scan of new or existing plug-in's.  This is extremely frustrating, and yes, I've removed the plug-in last installed with no luck.  I could really use some suggestions on how to get the plug-in scan to work again.  Thanks!

    B
    booch_21
    Participant
    March 2, 2018

    Additional information.  I completely removed Production Premium 6 last evening.  Used the Adobe cleaning app to make sure it was gone.  Did the reboots as specified.  So I am now on Audition CS6 and tried the Plug-In Manager.  It hung as well, never leaving 0% scanned on the default folders.  Creative Cloud updater began updating to 6.5 soon after.

    Why does this issue not get resolved when I can search it in Google and see it cropping up more frequently than Adobe realizes?  Not everyone wants to pay for CC and are quite happy with 6.5.  I am one of those.  Come on, Adobe, please find a solution.

      M
      madcowzackAuthor
      Participant
      March 2, 2018

      This is gonna be a shocker, but I installed the current CC version, and all of a sudden, everything worked fine.

      I'm with you, Booch, on your last point.

      I cant speak for everyone, but I'd personally rather pay a nominal $19 - $29 for an update every year or two, or when issues like this arise, than pay a monthly licensing fee for all of eternity ... just saying.

      In the meantime, I'm going to do without. And if I want to screw around with the nice plug-ins, most seem to work in Audition ... though not in real time.

      jeremyw85226928
      jeremyw85226928
      Participant
      February 16, 2018

      Im having same issue. Went to place new plugins and and it didnt scan. I ran a update and it didnt help.

      ryclark
      ryclark
      Participating Frequently
      February 17, 2018

      Which version of Audition? This thread was particularly asking about CS6 which is quite old now and only 32bit. So there could be problems with an assortment of 32/64 bit VST plugins.

      M
      madcowzackAuthor
      Participant
      February 17, 2018

      @ryclark How can the problem be with plug-ins that worked moments before I installed a couple new ones ... Then went to scan for them, and the Plug-In Manager sat at 0% / never actually launched? That's like saying, "You put bad gas in a car with a faulty starter & bad alternator, but the gas is why it won't start."

      ryclark
      ryclark
      Participating Frequently
      February 9, 2018

      Are they 32bit or 64bit versions of the Waves plugins? CS6 only accepts 32bit VSTs. Try temporally removing the new Waves .dll files from the Folder to scan and then see if Audition can rescan without them.

      M
      madcowzackAuthor
      Participant
      February 10, 2018

      not sure, but ... even if i set the scan to default mode, it still won't scan at all.

      UPDATE: Moved the Waves file out of the Library/Audio/Plug-ins/VST folder & unselected the 2nd one ... same result.

      Additionally, it crashed immediately thereafter.

      Process:               Adobe Audition CS6 [15743]

      Path:                  /Applications/Adobe Audition CS6/Adobe Audition CS6.app/Contents/MacOS/Adobe Audition CS6

      Identifier:            com.adobe.Audition.5.0

      Version:               5.0.2x5 (5.0)

      Code Type:             X86 (Native)

      Parent Process:        ??? [1]

      Responsible:           Adobe Audition CS6 [15743]

      User ID:              

      Date/Time:             2018-02-09 19:24:14.755 -0500

      OS Version:            Mac OS X 10.13.3 (17D47)

      Report Version:        12

      Anonymous UUID:        361C9D78-06D4-43EB-C235-A0E2E3133871

      Time Awake Since Boot: 100000 seconds

      System Integrity Protection: enabled

      Crashed Thread:        0  Dispatch queue: com.apple.main-thread

      Exception Type:        EXC_BAD_INSTRUCTION (SIGILL)

      Exception Codes:       0x0000000000000001, 0x0000000000000000

      Exception Note:        EXC_CORPSE_NOTIFY

      Termination Signal:    Illegal instruction: 4

      Termination Reason:    Namespace SIGNAL, Code 0x4

      Terminating Process:   Adobe Audition CS6 [15743]

      Firefly Community Gallery
      Adobe Firefly

      Remix with Firefly Community Gallery

      Thousands of free creations to fall in love with and remix in Firefly.

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