We understand that feelings run high about the PACE authorization system, because so many audio plug-in use it. We did not make this decision lightly, and we wanted to explain our reasons to you.

Authorization and copy protection is a pain not only for every legitimate user but also for us - developers. For the last couple of months, problems with our in-house authorization system has been our main cause for support requests, especially on macOS. It seems every OS update brought us new hassles and headaches. We are not a large company with dedicated support staff and programmers who just deal with authorization code; it was getting to the point that trying to keep our authorization system working was taking time away from PSP Audioware’s real mission: developing professional audio processors. We went looking for what technology is out there that other audio plug-in companies are using. The undeniable truth is that a lot of audio companies use PACE technology successfully. They’ve improved the speed at which they support updates to Windows and macOS considerably over the years. Many professionals in the audio world already have iLok accounts with hundreds of licenses that they use without issue so choosing PACE seemed the most seamless and trouble free option.

Our main goal is for this transition to be as seamless as possible to our customers, thus:
All forthcoming updates to existing plug-ins and new plug-ins in the future will use PACE. Versions of software available prior to this announcement will continue to use our in-house authorization system
We won't change our prices to pass our extra costs onto our users.
We intend to keep our license support as direct as before.
We will allow license transfers after initial approval without charging you the PACE license transfer fee.
We do NOT require you to use iLok hardware dongle - you can select hard drive authorization if you prefer.
For your convenience you can activate your license in three separate locations, each of which can be either a computer or an iLok key (2nd generation or above).
The transition of all our authorizations to PACE will take time, and we appreciate the understanding and cooperation of our user community as we make these changes.

Antoni Ozynski