Overview
This Developers Quick Start Guide is a companion document to the (8.D.2.5) Custom Modules Developer's Guide. It describes creating custom modules for Audio Weaver. Both of these documents reference information contained in the (8.D.2.5) MATLAB Scripting API. This document is intended for developers creating their own custom Audio Weaver module packs.
...
The wizard will create the following folder structure, with default files in each folder as necessary:
📂 my_new_module
📁 my_new_module\doc
📁 my_new_module\images
📁 my_new_module\include
📁 my_new_module\inner
📁 my_new_module\lib
📁 my_new_module\matlab
?? my_new_module\projects
📁 my_new_module\projects\source
📂 my_new_module\projects\VS2010
📁 my_new_module\projects\VS2010\BuildDll
📁 my_new_module\projects\VS2010\BuildLib
📁 my_new_module\projects\xml
Note: When creating or editing module folders, the following items apply:
The folder VS2010 must be renamed to match the appropriate version of Microsoft Visual Studio.
The folder matlab cannot be deleted from the File Explorer if the MATLAB application is open.
...
Traditionally, custom modules created with AWE Designer Pro Edition could only be shared with other Pro users due to technical limitations. Overcoming these limitations, Interpreted Modules allow custom module authors a way to share their modules with other Designer users regardless of Edition used. By following the creation steps below, a Pro user can create an Interpreted Module using the familiar MATLAB API that will behave similarly to other Audio Weaver modules, but importantly will be installable by Pro and Standard Designer using the Setting Search Paths functionality.
Creating an Interpreted Module
...