Here you go! Blue Cat’s PatchWork and MB-7 Mixer can now officially host VST3 plug-ins!
VST3 plugins can loaded next to VST2 plug-ins or Audio Units in the same session, in almost any host application: your favorite VST3 plug-ins can now be hosted in Logic, Pro Tools, Ableton Live and more…
How Can I Get The Update?
As usual, the update is free for existing customers. It can be downloaded from the same location as the original full version (link received by email upon purchase).
Should I use Only VST3s Now?
Definitely not! As explained when VST3 versions of our plug-ins were released, the VST3 plug-in format has some limitations that may not fit your workflow. Also, after a couple of months testing third party plug-ins and hosts, it appears that VST2 or AU versions of the same plug-in are often much more stable than their VST3 counterpart: VST3 is quite new compared to VST2, so many manufacturers are still improving it…
All in all, VST3 support is mainly interesting for the most recent plug-ins that may not have been released as VST2 (or AU).
So when trying to load a new plug-in, we advise you to try the following formats, in order:
- VST2
- VST3
- Audio Unit
Why VST3 as number 2 despite what was said earlier? Simply because it can be loaded on both Windows and Mac (and Audio Units are Mac-only). So if you intend to share your projects or reuse your presets on another platform, you’d better try to use VST2 or VST3.
Enjoy!
Why Audio Unit on last? VST is better than Audio Unit in some way?
No format is better than another: it depends on both the hosts and plug-ins. However, AU is Mac only, so if you want to share your presets or sessions with others who have Windows machines, VST and VST3 are better options.
I’m using VST2, VST3 and AU, mostly because I use different hoses. VST2 -> NI Stuff (Machine, Komplete Kontrol), VST3 -> WaveLab, AU->Logic, Ableton. I prefer AU in Ableton ’cause of the way I can organize them and presetmanagment. BUT there are many AUs which are only sandboxed VST, so there are pros and cons for both formats and sometimes you maybe need both.
Why can’t I use AAX plugins inside Patchwork? The web site claimed it would work with AAX. Now I have spent $99 for nothing. Advertising is misleading. You cannot use AAX plugins inside of Patchwork, but only VST. Hope Bluecat Audio can fix this or refund my money. I have other Bluecat plugins that work just fine in Protools 12.5 but it seems the Patchwork can only be hosted as an AAX shell but not able to load AAX plugins within it.
We apologize if you found the description misleading. The plug-in can be loaded as an AAX plug-in, but it is clearly stated that it will load VST, VST3 and Audio Units:
AAX is a plug-in format that belongs to AVID, which, as far as we know, will not allow third parties to host it. Since most plug-ins are also available as VST or VST3 plug-ins, you can usually load them in these formats. Feel free to follow up by email if you have any question (we have also replied to your email).