Blue Cat Audio announces VST3 Plug-In Format Support as a Free Update

[unkJE]

http://www.kvraudio.com/news/blue-ca...e-update-32401


Congratulations Blue Cat Audio - this is great news!

[Seafoam_Green]

Originally Posted by unkJE

http://www.kvraudio.com/news/blue-ca...e-update-32401


Congratulations Blue Cat Audio - this is great news!

I have Bluecat patchwork which I use In Pro Tools 12 (AAX) which I use to occasionally host VSTs within pro Tools ..., or to even host a specific signal chain,

Or ...,

I also use Bluecat Patchwork it in standalone mode for live hosting of V.I's and adding FX (without the need for using a Daw)


Question ;

With the upcoming VST3 capability , I understand (I think I do) thats VST3 is more CPU efficient which will make the Standalone version more CPU efficient.
This is great news, as this should give users more power with reduced latency when patchwork standalone is being used (especially when I host V.I's in a live situation ) .....,


but ....,


Q1 - How will the VST3 capability reflect to Pro Tools (AAX) ?

With the current VST "2" version of patchwork (either in AAX, or the VST2 Patchwork Standalone) ...,


Q2 - Will the current VST2 Patchwork either "load / host" VST3 plug-ins into the current Patchwork VST2 version?

..., or is this capability only possible with the upcoming VST3 Version of patchwork

[DonaldM]

This means I can run my Yahama Motif XS Editor, which is in VST3 format, in Patchwork essentially making my Motif behave like a very large VI!! This will be sooooo nice!!!!

[musicman691]

Originally Posted by Seafoam_Green

I have Bluecat patchwork which I use In Pro Tools 12 (AAX) which I use to occasionally host VSTs within pro Tools ..., or to even host a specific signal chain,

Or ...,

I also use Bluecat Patchwork it in standalone mode for live hosting of V.I's and adding FX (without the need for using a Daw)


Question ;

With the upcoming VST3 capability , I understand (I think I do) thats VST3 is more CPU efficient which will make the Standalone version more CPU efficient.
This is great news, as this should give users more power with reduced latency when patchwork standalone is being used (especially when I host V.I's in a live situation ) .....,


but ....,


Q1 - How will the VST3 capability reflect to Pro Tools (AAX) ?

With the current VST "2" version of patchwork (either in AAX, or the VST2 Patchwork Standalone) ...,


Q2 - Will the current VST2 Patchwork either "load / host" VST3 plug-ins into the current Patchwork VST2 version?

..., or is this capability only possible with the upcoming VST3 Version of patchwork

VST3 capability has nothing to do with how Patchwork works in PT as you're using the aax version of Patchwork and that's all PT sees. And the way I understand it the current Patchwork version won't load VST3 plugins - that's why BCA is doing an update to their plugin line to add VST3 capability.

[thanos4]

just checked in my account for next preview build
apparently there is a vst3 beta for windows and mac
The aax version is still 1.71 and it's the same...meaning no vst3 host..

[WorldStudios]

It hopefully means I can run the Integra 7 editor in ProTools, since the AU one does not work with Patchwork.

The beta is available for paying users. Amma try it out now!

[WorldStudios]

Alas, the plugin works in VST3 format, but it does not HOST vst3 plugins. I just checked. But we can always hope for the future!

[astroturf]

yeah i was wondering what you guys were talking about, it's not hosting vst3, the plugins just now come in vst3 format

[bluecataudio]

Indeed, this update is only meaningful for VST3 hosts such as Cubase - it does not mean that PatchWork can load VST3 plug-ins (we are not there yet...).

By the way, VST3 is not more efficient than VST2 (even if it may be in some cases, because plug-ins can in theory avoid processing unnecessary audio streams. In practice, I would not expect much difference).

[TOM@METRO]

Thanks for the clarification.