Mixbus, Mixbus32C: v6.2 now available with VST3 support!

[doncolga]

Just did a 30-minute mix on it. NICE!

[MakerDP]

OK so forgive the ignorance but this is the first MB update I will perform... do I just download the current version from the main product page and run the installer? It will correctly install over the old version or do I need to uninstall old version first?

No uninstalling is needed, when you install the upgrade you will be asked if you want to keep the old version as well.

Very good. Thanks.

[Perry Warren]

I have IK Multimedia T-Racks 5 Max and for some reason Mixbus32c does not show the VST3 version. Other VST3 plugins show up after scanning plugins. Not sure if it's a Mixbus problem or T-Racks problem. The T-Racks VST3 plugins show up and work in other DAWs.

Are they installed in a different location? Check to see if your plugin search paths are exactly the same in all of your DAWs.

I'm running Windows 10. I install all VST3 plugins to Documents\VST3 folder. All VST2 plugins go in Documents\VST. I have the path preferences set correctly. The only VST3 plugins that don't show up are the T-Racks plugins and Wilkinson De-Bleeder. The VST2 versions do show up. I use Reaper also, and I don't have this problem with it.

[doncolga]

MIx number 2 for the evening. Very satisfying. The only little snag was there was a little while in the editor Tab wasn't placing markers.

[Dingo]

I have IK Multimedia T-Racks 5 Max and for some reason Mixbus32c does not show the VST3 version. Other VST3 plugins show up after scanning plugins. Not sure if it's a Mixbus problem or T-Racks problem. The T-Racks VST3 plugins show up and work in other DAWs.

Try deleting the VST 3 blacklist (Preferences / Plugins / VST) and do a rescan see if that helps.

---

I forgot I had an auth for T Racks 5, downloaded and authorized.
No issue loading VST3 for T-Racks, so check you have the latest version of Product Manager and check the VST 3 blacklist.

[JiriR]

I will clarify the question. VST3 factory presets appear in the drop-down menu, but cannot be called up. The plugin cannot load them.

Is there a particular plugin that is not recalling or is it all VST3 ?
I am not seeing that in any of the plugins tested so far.
On macOS I have tested most AVA, ACE, Fab Filter, XT, some Waves and a few Brainworx* all without issue.
That has included loading VST2 presets as well as create and load VST3 presets.
With McDSP I have only ever had factory sets on the AU versions.

* Brainworx and some of the Plugin Alliance range show all parameters when inserted.
This is apparently a behavior that is coded by the manufacturer in their VST3 version. Right Click / Controls / Hide all controls.

All VST3 plugins do this
Edit: Plugins from the Plugin-Alliance do this (brainworx, SPL, Unfilterd Audio, etc ...). Please anyone know why?

[fortewal]

For me, PSPaudioware plugins (vst2 and currently vst3): 2445 EMT, oldTimerMB, Twin-L do not work. They are blacklisted. Problem not solved since Mixbus 32C 5.3.22. I applied on February 12, 2020.

[gennargiu]

Hi,many thanks Harrison for this update. I have a testing vst3 with reason intro on windows 10 system and work perfect !!!

[img][/img]

[img][/img]

Best Regards from Naples (Italy)

Gennaro

[Yriisem]

Hi, did anyone notice that in this update the mixer window disappears when interacting with any plugins? I am mostly only in the mixer, so this behavior is very disruptive to work. Otherwise, everything is fine!
Windows 10x64
https://youtu.be/gqYWFI7iu18

[x42]

I'm running Windows 10. I install all VST3 plugins to Documents\VST3 folder.

The VST3 spec mandates that plugins should be in

Code:

    C:\Program Files\Common Files\VST3\

see https://steinbergmedia.github.io/vst3_do...inlocation

It is one of the great assets of VST3 to also mandate this on Windows (previously only Mac had a fixed location for VST plugins). It makes everything more consistent and less likely go wrong.

If you really have to pick another folder, you can configure this in Mixbus Preferences > Plugins > VST > VST3 Path.