• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

vsts

New Here ,
Oct 04, 2020 Oct 04, 2020

Copy link to clipboard

Copied

soooo frustratingAudition 13 cc is not recognizing plug ins  this is a huge problem! I have waves, izotope, etc and I really need these. Not a newbie. I know how to add plugin folders to the manager. Previous versions I added vst 64 and vst3, never a problem. Now I do a scan and nothing shows, scan just hangs  Previous editions, 0 issues. If i added new plugin and opened up effects manage/rescan, boom, there it was. What is different?

Win 10/home/16gigs onboard

No issues, same folders vegas 17, sound forge 14, acid, cakewalk

TOPICS
Freeze or hang

Views

258

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Oct 05, 2020 Oct 05, 2020

Copy link to clipboard

Copied

This sounds like file a screwed somewhere in Preferences. You'll lose any settings you've made and saved, but the simple way to reset the preferences is to start Audition with the Shift key held down. Then try again...

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Oct 05, 2020 Oct 05, 2020

Copy link to clipboard

Copied

Steve, never heard of that.Thanks, will certainly try. And yes, all are 64 bit!

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Mentor ,
Oct 05, 2020 Oct 05, 2020

Copy link to clipboard

Copied

Just make sure that these are 64bit plugins

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Oct 05, 2020 Oct 05, 2020

Copy link to clipboard

Copied

Well, no go n the shift/start trick. Just thought of a long shot trick to try, I'll describe it and if it works/fails, but only after. I'll guinea pig and if it doesn't work hopefully I'll save others who may attempt it a little bit of time

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Oct 05, 2020 Oct 05, 2020

Copy link to clipboard

Copied

So I cleared out all the possible vst locations in the manager, copied all the vst folders into the audition folder itself and then pointed the manager to those. Also in preference>effects >sort effects menu, I switched among all categories (vendor/category, category/vendor, etc), still nothing. This is way beyond a bug, and Ive seen this issue come up in previous versions on the threads

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Advisor ,
Oct 06, 2020 Oct 06, 2020

Copy link to clipboard

Copied

I don't think that you should place non-Adobe VSTs in the same folder as those from Adobe.  I'm pretty certain I've read in this forum that Adobe themselves do not recommend this!

 

If this were an app bug it would affect users like me, and it doesn't!  I have all my non-Adobe 64 bit VSTs and VST3s in designated folders and all are seen and available in the app.  I even have some bridged 32 bit VSTs and VST3s listed in the Audio Plugin Manager..

 

If it were me I would move all those non-Adobe VSTs to a folder I created specifically for this, go to the Plugin Manager, add that location and then select to scan, also ticking the box to "Rescan existing plug ins".  In essence, that is how everything is set up on my system - I created a dedicated folder for my VSTs (VST3s install to a default folder which I have not attempted to change) - scanned and everything was listed.

 

So, as SuiteSpot asked, are these VSTs all 64 bit?  Are any of them actually VSTis, which Audition cannot use?

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Oct 07, 2020 Oct 07, 2020

Copy link to clipboard

Copied

So you may have missed it  All plugins:64 bit. All plugins were placed in individual vst folders, including vst3/common files. All were where they should be. Copying those folders into adobe folder was a hail mary to see if I had any luck. I didn't, no harm done, just deleted them and they were only copied, so all vsts are where the should be. Again, not a newbie, and this has never happened in previou editions of audition. Not a single vsti.Scan/rescan not working, looks like I need a re-install.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Advisor ,
Oct 08, 2020 Oct 08, 2020

Copy link to clipboard

Copied

You say all plugin were placed in individual vst folders.  I think that may be where the problem is coming from!

 

On my system I have all the .dlls for my VSTs, with only three exceptions, in one folder.  Those exceptions are in individual folders within the main one, that's how the original installation of the VSTs created them.  With this set up I have no problem with AA seeing and being able to access all my VSTs.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Oct 09, 2020 Oct 09, 2020

Copy link to clipboard

Copied

I will try that. Thing is, it's always worked havingdifferent vst folders before, kinda like you> product specifc folders as pary of the setup, and a secondary for orphan or un cataloged dlls.As of now there are 2, but I'll yhrow everytihng into 1  Frankly it's lloking to me to be as something os related itsef  Just unimstalled a few plugins from the last 2 week, no also to avail.  Anyways guys, thanks for helping out and trying to fix this..really do appreciate! keep them coming if you think i should try

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Oct 10, 2020 Oct 10, 2020

Copy link to clipboard

Copied

Ok great news guys, finally got it. Last thought was to check McAfee to see if something was interefering. Don't ask me why, but one of the designated Adobe ports in my firewall switched from incoming/outgoing to outgoing only. So no talking between pc and adobe servers, only pc talking to adobe.Problem solved. Guys, I thank you all for your suggestions/ideas.I really appreciate it, and hope I can pay it forward soon!

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Mentor ,
Oct 10, 2020 Oct 10, 2020

Copy link to clipboard

Copied

LATEST

Thanks for reporting the solution and the fact that it ended up not being an Audition bug

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines