Community Plug-in Development Workflow

Wwise SDK 2024.1.1

This topic lists the main recommendations, requirements, and best practices for developers who are building Community plug-ins for Wwise. Review the list and refer to the linked documentation to ensure that your plug-in satisfies Audiokinetic's requirements.

Key Technical Requirements. Review the Community plug-in technical requirements (that is, what your plug-in must and must not do).
Audio Plug-ins. This section and all of its subtopics are relevant to developers who are creating Audio plug-ins. The following topics and subsections are especially helpful:
- Using the Development Tools. This section explains how to use wp.py (a tool written in Python) to create plug-ins, which you can then build upon as desired.
- Writing the Authoring Part of an Audio Plug-in. This section explains how to write the Authoring part of an Audio plug-in.
- Writing the Sound Engine Part of an Audio Plug-in. This section explains how to write the Sound Engine part of an Audio plug-in.
- Example: Developing a Lowpass Filter Plug-in. This topic provides an example of how to code an Audio plug-in, in this case a lowpass filter.
- Testing Audio Plug-ins. This topic lists a series of guidelines and tests that developers can run to ensure that their plug-in is compatible with Wwise.
- Wwise Source and Effect Plug-in Troubleshooting Guide. This topic provides solutions to common problems that plug-in developers encounter.
Source Control Plug-ins. This section and its subtopics explain how to create plug-ins that integrate Wwise with source control systems such as Perforce or Subversion.
Plug-in Packaging Format for the Audiokinetic Launcher. This topic describes the packaging format required for plug-in distribution through the Audiokinetic Launcher as well as the plug-in store.

Was this page helpful?

Need Support?

Questions? Problems? Need more info? Contact us, and we can help!

Visit our Support page

Tell us about your project. We're here to help.

Get started with Wwise