...
Developing custom audio modules for the native PC target requires the following:
Valid Audio Weaver Designer – Pro Edition License
Valid Custom Audio Weaver Feature: Module Creator License
MATLAB 2017b (64-bit) or later
VisualStudio Visual Studio 2010 or later
The audio module code is compiled and packaged into an audio module Dynamic Link Library (DLL). The DLL is read by the Server when it launches and makes the audio modules in the DLL available to the Server.
To develop custom audio modules for an embedded target you'll need the software items listed above together with development tools for the embedded target. You first create an audio module DLL using VisualStudio; this describes the audio module to the Server and is needed even if the Server is connecting to an embedded target. You then rebuild the target executable and link in your custom modules using your embedded development tools. The embedded development tools to use depend upon the details of your target processor.
Overall Development Environment
| Anchor | ||||
|---|---|---|---|---|
|
The Audio Weaver environment utilizes MATLAB, a PC-based Server, a hardware target, and development tools for the hardware target, as shown in Figure 1. Much of the design is orchestrated by MATLAB including describing modules, generating code, and generating documentation.
Steps 1 through 9 shown above the dark line in Figure 1 the figure below are for creating custom audio module DLLs on the PC. The main output is an audio module DLL shown as item 9. The DLL encapsulates all of the information required by the Server to natively execute an audio module. This includes the module C functions – Constructor, Set, Get, Process, and Bypass – and schema information describing the module instance data structure to the Server. A DLL may contain one or more audio modules.
...