Any reason why MB32 only recognises VST 2 plugins?

[TheBassBagwhan]

Hey everyone, this is an addendum to a previous thread, now deleted through no responses... I've discovered that MB32 only wants to recognise the VST2 versions of my NI and XLN (Addictive Drums) plugins. 

Any ideas on that? Am I "missing out" on something by using the VST versions?

Thanks

[Dingo]

Are you sure that NI and XLN have a VST3 version installed or in the correct position ?
Go to Window / Plugin Manager and look to see if NI or XLN VST3 are Ign (Ignored) or Hidden.
You might want to trash the VST3 Blacklist and rescan.

[TheBassBagwhan]

Go to Window / Plugin Manager and look to see if NI or XLN VST3 are Ign (Ignored) or Hidden.
You might want to trash the VST3 Blacklist and rescan.

Thanks Dingo, I've definitely got the VST3 .dll(s) in the right folder, and that folder is in the Scan path. They don't appear in the Plugin Manager at all ... not as Ignored or Hidden, or Error -- simply not there as if the Scan process doesn't see them. Clear "Ignore" does nothing -- that's the MB32 version of a Blacklist, right? Or is there a separate Blacklist different to the Ignore list?

The VST2 versions are a workaround, but it always bugs me when something like can't be explained and suggests other issues lurking somewhere.

By the way, this is after a full re-install of Mixbus after uninstalling through the Windows App function. (Mind you, the new install "remembered" the custom VST paths, so is there like a Windows-style Preference folder worth trashing?)

Cheers for your help. Bag.

[Dingo]

Clear "Ignore" does nothing -- that's the MB32 version of a Blacklist, right? Or is there a separate Blacklist different to the Ignore list?

Yes my bad, with v7 and Plugin Manager 'Blacklist' is now known as 'Ignorelist' which is a much better description.

[sunrat]

In Linux the full VST3 directory tree needs to be present for it to be scanned and work correctly. It doesn't work to just drop the binary in a directory by itself. Don't know about Win/Mac.
Here is the directory listing for my vst3 plugins. I only included the subdirectories for Bertom_EQCurveAnalyzer.vst3 but the other ones are similar.

Code:

ls -R .vst3
.vst3:
Bertom_EQCurveAnalyzer.vst3  FirComp.vst3  presets  sfizz.vst3  u-he

.vst3/Bertom_EQCurveAnalyzer.vst3:
Contents

.vst3/Bertom_EQCurveAnalyzer.vst3/Contents:
i686-linux  x86_64-linux

.vst3/Bertom_EQCurveAnalyzer.vst3/Contents/i686-linux:
Bertom_EQCurveAnalyzer.so

.vst3/Bertom_EQCurveAnalyzer.vst3/Contents/x86_64-linux:
Bertom_EQCurveAnalyzer.so

...

[madmaxmiller]

Go to Window / Plugin Manager and look to see if NI or XLN VST3 are Ign (Ignored) or Hidden.
You might want to trash the VST3 Blacklist and rescan.

By the way, this is after a full re-install of Mixbus after uninstalling through the Windows App function. (Mind you, the new install "remembered" the custom VST paths, so is there like a Windows-style Preference folder worth trashing?)

Cheers for your help. Bag.

There is, probably in %username%\appdata (hidden folder)
In Linux it's ~/.config/mixbus7
On Apple - I would need to look this one up

MMM

[Joe K]

Go into preferences and turn the plugin scan time all the way up and try again. That's what it took for all of my plugins to be recognized.

[TheBassBagwhan]

Thanks Joe, but that's standard for me ... only way to get my Waves plugs happening. Cranked up to 90 seconds. No joy.
It's a strange one ...

[JamieLang]

What's the NI plug? Addictive Drums, I just updated via their online installer. There is no VST3 version, which FWIW--would not end in "dll", but ".vst3"

[Dingo]

@jamielang well spotted.