scook
Run the installer, don't worry about uninstalling the previous version. Voxengo installers use the previous version as a guide for what and where to install the update.

OK I'm good to go, many thanks!!!

bitflipper

mike_mccue
Aleksy seems completely disinterested in providing AAX versions of his products. He says he can't get PT to work even though seemingly anyone else with PT is using it as if it works.

Actually, all of the plugin developers I talk to have been struggling with ProTools compatibility. It's not PT per se, but rather the new Pace signing requirement that's messing everybody up. Word is that Pace documentation and developer support is very poor unless your product is iLok-protected. Surprising, given how rock-solid Pace software has always been. ;)

 
 
Ah heck, even Melda productions does AAX... it can't be all that hard. :-)
 
Sonitus x64 DX and Voxengo VST are the only efx I own that I can't use as AAX. ;-)
 
We must have completely opposite lists of dsp vendors if all of your contacts have difficulty with it and almost all of my vendors have supplied full compatibility.
 
What I was explaining is that Aleksy explains that he can't even get PT 10 or 11 to work on his system... and so he doesn't have a practical way to test.

Ah heck, even Melda productions does AAX... it can't be all that hard. :-)

It apparently really is a PIA. Not because of AAX specifically, which by all accounts is well-documented and well-supported. Rather, it's because of the new requirement - and a new third-party software dependency - to have Pace digital signing implemented in every AAX plugin.
 
What that means is you get a little piece of Pace copy-protection magic bundled into every AAX plugin, whether it uses iLok or not. It means nobody can write an AAX plugin that doesn't have Avid's official blessing, because you need a special tool from Pace to generate the signature and they'll only give it to official Avid developers.
 
Avid would like very much to do away with the small independent software developer and leave it all to the "Pros". They're reportedly (developers are expressly forbidden from discussing this) charging a $500 annual fee to AAX developers to license the Pace signing code, a significant hit for the bedroom coder who only makes a couple grand a year off plugin sales.
 
Somebody wrote an AAX wrapper that would allow PT users to use any VST plugin. Avid killed it immediately, since they have a built-in kill switch to disable any plugin they don't approve of, and the terms of the SDK license say they don't need to give a reason for doing so. Avid does not appear to be putting users' needs at the top of the priority list. 
 
I'm so glad I never went the ProTools route. I have an acquaintance who went with a full HD rig 10 years ago. He was pretty pleased at the time even though it cost as much as a new car. I wonder how he's enjoying his gold-plated boat anchor today.
 
 

I'll bet the >3ms latency full featured monitor mixes sound just as good now and they did then. ;-)

I just read up on the PACE license: "AAX plug-ins must be digitally signed and this requires a fee in certain cases."
 
http://www.avid.com/US/pa...dio-plugin-dev-program
 
I wonder how you get to be a "certain case" and how you get to be one of the many vendors who made updating to AAX seem simple.

mike_mccue
I just read up on the PACE license: "AAX plug-ins must be digitally signed and this requires a fee in certain cases."
 
http://www.avid.com/US/pa...dio-plugin-dev-program
 
I wonder how you get to be a "certain case" and how you get to be one of the many vendors who made updating to AAX seem simple.

I think the fee does affect some smaller vendors.  I think it is ironic that the issue is due to anti-piracy measures when pirates actually have no trouble getting around Pace

If it is truly no trouble to get around PACE then the cost of fees, if any, don't seem like a convincing cause for small vendors to avoid updating to AAX.
 
 
 
 
Consider, if you will, Michael Carnes as an example. He runs a one man show, he makes two plugins, he was one of the first vendors to offer AAXx64 compatibility. He answers emails promptly, he always seems to be working on a update to enhance his two plugins, and he seems to have time to enjoy skiing in winter and hiking in summer.
 
The PACE doesn't seem to be slowing him down. :-)
 
 
 
 
edit spelling

dubdisciple

mike_mccue
I just read up on the PACE license: "AAX plug-ins must be digitally signed and this requires a fee in certain cases."
 
http://www.avid.com/US/pa...dio-plugin-dev-program
 
I wonder how you get to be a "certain case" and how you get to be one of the many vendors who made updating to AAX seem simple.

I think the fee does affect some smaller vendors.  I think it is ironic that the issue is due to anti-piracy measures when pirates actually have no trouble getting around Pace

I thought that iLok2 was secure. Are all the plugins cracked?

ANY copy protection can be circumvented if somebody has the patience, time and motivation to do so. But digital signing doesn't have as much to do with anti-piracy as it does with Avid wanting Apple-like control over who gets to sell software for their platform. This scheme lets them dictate who can sell ProTools plugins, with the added bonus of collecting a commission.
 
The positive spin is that this will yield more reliable plugins that conform to standards set and enforced by Avid. No more letting third-party components crash the DAW. Unfortunately, as long as plugins run in the same process as the host, such assurance isn't really possible.

bitflipper
ANY copy protection can be circumvented if somebody has the patience, time and motivation to do so. But digital signing doesn't have as much to do with anti-piracy as it does with Avid wanting Apple-like control over who gets to sell software for their platform. This scheme lets them dictate who can sell ProTools plugins, with the added bonus of collecting a commission.
 
The positive spin is that this will yield more reliable plugins that conform to standards set and enforced by Avid. No more letting third-party components crash the DAW. Unfortunately, as long as plugins run in the same process as the host, such assurance isn't really possible.

I have heard that anything is breakable if the will is adequate; I just don't see that iLok2 has been broken yet. It's been out a while too.