Welcome to our Community Plug-ins developer page. We’re pleased to offer you the opportunity to develop, and feature your plug-ins for use with Wwise on the Audiokinetic Store, or to distribute them on your own.
Please note that to become a Community Partner you must agree to comply with certain requirements of our program, which may include technical requirements related to use of our development tools and ensuring that your plug-ins are packaged correctly, as well as some other program rules and guidelines based on your commitment to one of two agreements.
This agreement provides you with all the advantages of the Audiokinetic Community Partner Program, including featuring and selling your plug-in for use with Wwise to Wwise users via the Audiokinetic Store.
This agreement allows you to distribute your plug-in for use with Wwise on your own as a Community Partner, and should be what you choose to complete your registration process if you do not want to distribute your plug-in via the Audiokinetic Store.
Whether you wish to distribute your plug-in through your own channels of choice, or feature your plug-in for use with Wwise on the Audiokinetic Store, please apply to participate in the Community Partner Program to register your plug-in.
Select your choice of commitment below and complete the Audiokinetic Community Partner Program registration process.
Please read the following documents carefully prior to registering your plug-in.
All Community Plug-in submissions must be made through the AUDIOKINETIC portal and will be subject to approval by AUDIOKINETIC.
AUDIOKINETIC Approval Process
Once you have submitted your AUDIOKINETIC Community Partner Program registration application, you can expect us to get back to you within 10 business days to confirm your participation in the program and provide you with a Company ID created by AUDIOKINETIC.
AUDIOKINETIC will evaluate each Community Plug-in submission to ensure it meets Technical Requirements and Marketing Guidelines for the Community Partner Program. Once you submit your Community Plug-in for approval, you will be informed through the AUDIOKINETIC portal whether or not it has been approved by AUDIOKINETIC. AUDIOKINETIC will have no obligation to provide you the reasons for which it did not approve your Community Plug-in.
Access to Wwise
Once your Plug-in has been approved by AUDIOKINETIC, and we have confirmed you can participate in the Community Partner Program, you will receive a non-commercial license key to enable you to fully develop your Community Plug-in. You will also receive beta access to early versions of future Wwise releases, so that you can prepare your Community Plug-in updates alongside ours.
AUDIOKINETIC Store Badge
Once your Plug-in becomes an approved Community Plug-in, you will be provided with the AUDIOKINETIC Store Badge and granted rights to use it on all your communication material and marketing channels. This AUDIOKINETIC Store Badge is for use only by approved AUDIOKINETIC Community Partner Program members, and only for their approved Community Plug-ins.
Always use the AUDIOKINETIC Store Badge without modification. AUDIOKINETIC reserves the right to withdraw permission for use of the AUDIOKINETIC Store Badge should its use be inconsistent with these guidelines or is otherwise deemed inappropriate by AUDIOKINETIC.
The Technical Requirements and Marketing Guidelines for the Community Partner Program are subject to change at any time at AUDIOKINETIC’s discretion, and are intended to help Community Partners assemble marketing collateral and meet prerequisite technical requirements towards featuring their Wwise Plug-in on the AUDIOKINETIC Store.
Please refer to the Technical Requirements and Marketing Guidelines for complete information. Below, you’ll find a summary of the essential Community Partner Program terms.
Key Technical Requirements
Your Community Plug-in may not:
Your Community Plug-in must:
Any compiled binary file, or code (DLL, LIB, EXE, or any executable format) executed by the Wwise Sound Engine or the Wwise Authoring shall be tested under all configurations and conditions.
Note that Audiokinetic will not evaluate the performance nor will it perform any aesthetic/quantitative testing (i.e. evaluate the quality).
We recommend that your Community Plug-in be developed and made available for all platforms, but this remains at your discretion. If your Community Plug-in can be used for restricted platforms (consoles, for example), we will require proof of your developer access to those platforms before making your Community Plug-in available to users.
The documentation you make available with your Community Plug-in must meet all Technical Requirements. We recommend that your documentation be available in the five languages supported by the AUDIOKINETIC Store:
End User License Agreement
You are responsible for providing an End User License Agreement governing the use by Wwise licensee of your Community Plug-in. Your End User License Agreement should not contain any requirements regarding credit in products.
If your Community Plug-in contains open source software, you will have to follow AUDIOKINETIC’s technical requirement to include the information in your documentation. If a user wants to avoid the use of such open source components, they will have to contact you directly.
At no time will you be required to deliver the source code of your Community Plug-in to AUDIOKINETIC.
Your Community Plug-in will be made available to users in object code only through the AUDIOKINETIC Store. AUDIOKINETIC will be responsible for making your Community Plug-in available and all purchase transactions. You may make your Community Plug-in available to users directly from your website, but the AUDIOKINETIC Store will not allow links to third party sites or pages for the purposes of selling or allowing download of the Community Plug-in from a third party site.
You are responsible for defining the pricing for your Community Plug-in, which must be based on our three tier licensing model (see the AUDIOKINETIC Detailed Pricing page ). You may also submit free Community Plug-ins.
You agree that whatever your pricing, your Community Plug-in must be made available free of charge for evaluation, academic, and non-commercial projects in a way that is consistent with the AUDIOKINETIC business model.
AUDIOKINETIC will create license keys (the “License Key”) using the Company ID created by AUDIOKINETIC for each Community Plug-in to provide access to users on a project by project basis.
The license key will allow each Project team member to download and use the Community Plug-in in accordance with the relevant license Agreement and the licenses thereunder. A new License Key shall be available through the Project License Page in the event of any change in the terms of the license or in access granted.
The License Key can unlock the Community Plug-in with one or several platforms, to the extent provided under the relevant License Agreement. If a license is purchased for a specific platform, the License Key shall be designed to unlock the Community Plug-in with this or these platforms only.
Users who download a trial version of the AUDIOKINETIC Wwise Technology will be able to select your Community Plug-ins for download for trial; they will be installed in the Wwise Launcher. The Trial version of the AUDIOKINETIC Wwise Technology does not allow the user to generate SoundBanks using unlicensed plug-ins.
Evaluation licenses for the AUDIOKINETIC Wwise Technology may be granted to users by AUDIOKINETIC on demand only, in which case Community Plug-ins selected by the licensee will be unlocked and available for installation in the Wwise Launcher for the same period as the evaluation license period.
Support and Maintenance of Community Plug-ins
With every major release, once available and at AUDIOKINETIC’s own discretion, AUDIOKINETIC will make available to you a beta version of the AUDIOKINETIC Wwise Technology to allow you to update your Community Plug-in as required. You will be required to support the most current version of Wwise (at plug-in release) in addition to a 1-point preceding release version.
You will be required to maintain and test every major version of your Community Plug-in before it is made available to AUDIOKINETIC for distribution. If you fail to maintain your Community Plug-in to allow its compatibility with the latest version of the AUDIOKINETIC Wwise Technology for a period of more than 6 months, your Community plug-in may be removed from the AUDIOKINETIC Store.
AUDIOKINETIC will not provide any free support to you or the users of your Community Plug-in. If you need support, you will have to buy support tickets (Pay2Go) from AUDIOKINETIC. AUDIOKINETIC will have a link to your site for users requiring support for your Community Plug-in. You will be required to fix any bugs within 30 days.
Every time your Plug-in is sold through the AUDIOKINETIC Store, you will earn a seventy percent (70%) revenue share of your Plug-in’s retail price net of any discounts granted to the customers.
Collection and Payment
Once you have submitted your AUDIOKINETIC Community Partner Program registration application, you can expect us to get back to you within 10 business days to confirm your participation in the program and provide you with a Company ID created by AUDIOKINETIC. In the case that your Community Plug-in does not get approved, AUDIOKINETIC will have no obligation to provide you with the reasons for its decision.
Below, you’ll find a summary of the essential terms related to the SDK Agreement. Please refer to the legal agreement upon submitting your plug-in, for complete information.
Key terms as per your commitment to the SDK Agreement.
Developers seeking to feature their Wwise plug-in on the Audiokinetic Store need to provide Audiokinetic with the following marketing collateral.
Logo needs to be provided in PNG format, on a transparent background. Note that it also should be at least 220 px wide, and its height should be equal to the width, or smaller.
Up-to approximately 50 words.
Up-to approximately 125 words.
For each benefit provided, please include a descriptive sublist of features or capabilities written in concise sentences.
Example benefit: Sense of Presence and Immersion
Example sublist of functionalities or capabilities: Use dynamic early reflections to automatically add life to each of your sounds. Any slight movement or rotation from the emitter or listener renders a different audio output, which is much more realistic than standard static rendering. Enrich the sense of space and physicality with surrounding materials using acoustic textures: A four band filter designed to simulate real world absorption of typical materials such as wood, concrete, drywall, and fabric.
Up-to 3 screenshots of your plug-in in action. Screenshots should be at least 800 px wide, and any height is acceptable.
Here is an example of how a Wwise Plug-in dedicated page would look like on the Audiokinetic Store.
Please refer to the detailed Technical Requirements to build and prepare your Wwise Plug-in.
Please refer to the detailed Technical Guidelines to build and prepare your Wwise Plug-in.