Effects VST & VST 3 don't appear.

Forum|Forum|13 years ago
May 18, 2012
5 replies
118361 views

Hi.

I installed Adobe Audition CS6, and VST plugins and VS3T don't appear in Effects Windows, only the names VST and VST3.
I've been in "Audio Plug-in Manager" and selected the folder where the plugins are "C:\Program Files\Adobe\Adobe Audition CS6\Plug-ins\VST3" and "Scan for plug-ins" and don't appear in the "Available Plug-Ins".
This situation is normal?

I have a Sound Blaster Live 5.1 soundcard installed on your system.

Thank you.

Paulo.

Correct answer emmrecs

So you don't have to ask: They are AU, VST, & VST3 plugins. All the Adobe effects work. Adding one of the plugins may have triggered this problem. I'm running Audion CS6 on Mac OS10.11.6 on a 2008 Aluminum MacBook.

I have experienced something similar to this, running CS6 but on Windows so this possible solution may not work!

However, you need to "force" AA to rescan all your plugins. First, check that the "plug in folder" list in Audio Plug In Manager is correct and complete. Then, in the same screen choose "Scan for plug ins" with the "Rescan existing plug ins" checked. This may now find and reload all your existing plugs. In my case, it found some, but not all. So I reselected "Scan for plug ins" but with "Rescan existing plug ins" NOT checked.

I think I needed to repeat this process at least once more and eventually AA "found" all my plugs and loaded those it could use.

M

Mag. Paul3711986028i6

New Participant

I love you guys so much, thank you for saving me possible hours of searching ^^

C

Cameron26209122cs1o

New Participant

Im having a similar problem wtih my VST after upgrading to 2022. In the Audio Plug-in Manager, RX is showing as AU type. It's probably a small fix. Can someone help? Thank you.

H

HarleyTDavis

Inspiring

Hey everybody. Thought I'd jump in here.

Depending on your DAW you may need a specific type of VST. Adobe relies heavily on basic C and Javax api's, along with some quicktime and windows directx commands that allow for heavier effects. Some VST's are for building instrument styled sounds, others are actual effects. DAW's have a similar separation when it comes to supporting VST. Some VST's were designed only to handle specific midi information, while others were designed to handle audio signal input. Some plugins have multiple versions; they might use the same codebase and work the same way, but be for two different application sets, accepting two different kinds of input. Recent VST3's are closing the gap but still lagging behind in the cross-application department.

To get your vst's to run no matter what app you're in, I suggest you download VSTHost, and the slave adaptor plugin, then read up on how to run the host as a slave app. You put the slave adaptor in your VST plugins for your DAW, and then open the slave VSTHost, load the plugins and connect input and output; you can automate the plugin in your DAW afterward.

It can turn 32bit plugs into 64bit functionals, and turn 64bit plugs into 32bit functionals. The audio pathway will have some conversion in the roundtrip, but only if you're converting with a 32bit plug and have a 32bit sample, as most 32bit plugs are 24bit and lower (though some do full 32bit float).

I have personally run Audition CC with this method, and used an audio-playback plug that isn't readable by Audition; it doesn't take input from your app, but instead allows you to set up backing tracks or FOLEY sound for recording into a session at an appointed time. I ran the plug on a record enabled track, using a Presonus 1602 classic firewire hooked to thunderbolt3 over an adapter, and it even sends the audio back out over the same channel I set. It functions normally. Now I don't need rewire or more gear to have a track with playback functionality.

I tried a few more plugs, they work as well. I can even set up chains of them to run as a single plug in audition, all with the same slave VSThost. I can load multiple of them with multiple slaves, or differentiate by input\output numbers. Either way, I can load multiple instances of the slave program and build complex VST chains, then route them all back to adobe audition, turning it into a powerful DAW. However, I do need two screens to work efficiently, and it takes a lot of RAM to run all that together...

Here's the link to the main homepage:

VSTHost

B

briancayko

New Participant

I ran into this same problem Feb of 2017. I have a 64bit windows 10, Audition is installed in "program files" not "program files-x86" so i assumed it was a 32bit version of AA therefore i was trying to install 32bit VST's. When i saved the 64 bit versions of the VST's into a folder, and then used the Audio plug in manager to "add" the folder i created, followed by a "scan for plugins" it found them. I clicked "Enable all" and "ok". they showed up in the drop down effects menu under VST or VST3 depending on the type they were.

bottom line was i had to download the 64 bit versions of the plug ins.

E

emmrecs

Brainiac

briancayko wrote:
I ran into this same problem Feb of 2017. I have a 64bit windows 10, Audition is installed in "program files" not "program files-x86" so i assumed it was a 32bit version of AA therefore i was trying to install 32bit VST's. When i saved the 64 bit versions of the VST's into a folder, and then used the Audio plug in manager to "add" the folder i created, followed by a "scan for plugins" it found them. I clicked "Enable all" and "ok". they showed up in the drop down effects menu under VST or VST3 depending on the type they were.
bottom line was i had to download the 64 bit versions of the plug ins.

Since, in your own words, "Audition is installed in "program files" not "program files -x86"" why did you assume it was a 32 bit program? That "program files" directory is where 64 bit programs are installed, by default.

But yes, the problem is that a 64 bit version needs 64 bit VSTs, though jbridge can enable use of 32 bit versions in a 64 bit environment.

However, the OP to this thread was running AA CS6, which is 32 bit.

SteveG_AudioMasters_

Community Expert

Most VST plugins that install don't go where you said at all - that's just the location of the built-in plugins within the software itself. The default location for ones you install yourself is in C:\Program Files\Steinberg\vstplugins. Make sure that you are scanning this location first, and report back if they aren't there...