Plans for VST Adapter Support in Pro Tools 11

[audioluche]

I dont think Avid is charging a dime for AAX development.



Here's what Dave Tremblay from Avid wrote in the Kush Audio thread:

[QUOTE/]
There is also a misconception about the cost of AAX development. Let me state categorically, that Avid doesn't charge a dime for AAX development. In fact, we give developers large discounts on hardware. We loan HDX cards, for free, to established developers committed to AAX DSP development. We provide Pro Tools licenses for free to develop and test plug-ins. Compare that with developing for VST or AU, where developers have to buy licenses for all of the various hosts to test with. Sometimes developers can get free licenses, but not always.

We know how important our plug-in platform is, to our business, to our partner's businesses, and to our customers. That is why we're willing to spend the kind of time and money we do to create and support it.

Dave[/QUOTE]

[southboundloco]

Does this mean that some developers are outright lying about having to pay fees and such per plugin?

[guitardom]

Originally Posted by southboundloco

Does this mean that some developers are outright lying about having to pay fees and such per plugin?

Could be mistaken with say a fee ilok charges or something?

[musicman691]

Originally Posted by audioluche

I dont think Avid is charging a dime for AAX development.



Here's what Dave Tremblay from Avid wrote in the Kush Audio thread:

[QUOTE/]
There is also a misconception about the cost of AAX development. Let me state categorically, that Avid doesn't charge a dime for AAX development. In fact, we give developers large discounts on hardware. We loan HDX cards, for free, to established developers committed to AAX DSP development. We provide Pro Tools licenses for free to develop and test plug-ins. Compare that with developing for VST or AU, where developers have to buy licenses for all of the various hosts to test with. Sometimes developers can get free licenses, but not always.

We know how important our plug-in platform is, to our business, to our partner's businesses, and to our customers. That is why we're willing to spend the kind of time and money we do to create and support it.

Dave

[/QUOTE]

Originally Posted by guitardom

Could be mistaken with say a fee ilok charges or something?

I think it's more of a case of the SDK and development tools themselves are free but there's a license fee for working with the AAX format.

[Bob Olhsson]

I suspect that "big bad expensive Avid" is just an excuse. While Pro Tools is the largest professional platform, I understand CueBase users are still by far the largest group of potential customers. I've heard that VST3 has by no means been a trivial transition and suspect many developers would make VST3 a priority over AAX.

[DonaldM]

Its good to get the full explanation straight from the right source! Thank you Ed!! VSTs will work with Reaper via Rewire.

[guitardom]

Originally Posted by DonaldM

Its good to get the full explanation straight from the right source! Thank you Ed!! VSTs will work with Reaper via Rewire.

More specific VSTI's will work this way. Regular VST effects will not unless the audio is in reaper and streaming to PT

[scottgreiner]

As an Avid development partner, I have never been charged ANYTHING to develop plugins for Pro Tools. I also find their development site to be quite responsive, as opposed to AU & VST development, which has no support portal at all.

As far as I've been made aware, the $500 is a Pace license to allow digital signing, which is necessary in Pro Tools 11. This hopefully will go a long way to protecting plugin developers from software pirating.

[rockridge]

Originally Posted by Ask the Developer Guy

We remain open to developers providing access to VST processing in Pro Tools if the products make clear in their interfaces that VST plug-ins are being used as part of an AAX plug-in. For example, a multi-effect plug-in might have a VST plug-in shell implemented within the user interface and accessible within a separate menu of clearly labeled VST plug-ins

Does this mean VST in Protools 11?

[musicman691]

Originally Posted by rockridge

Does this mean VST in Protools 11?

Not natively but within some sort of shell. You'd have an AAX plugin in PT that uses the code of a vst plug inside that AAX plugin. Like this:
((AAX plugin(vst plug in code)AAX plugin)) where PT never actually sees the (vst plug in code) part.