Global Preferences
To apply custom Audio Weaver Designer settings, use the Global Preferences menu at ‘File → Global Preferences’.
Configure the PC Sound Card
AWE Designer’s Native Target allows audio processing to be performed on the PC. When running layouts on the Native target, the AWE Server can be used to select which PC input and output audio devices should be used. Access this menu from the Server’s ‘File → Preferences’ menu item. Choose your sound card and sample rate for analog I/O. Multiple sound cards can be enabled, and users can choose between DirectX and ASIO drivers. The selected inputs will be interleaved at the input pin of your Audio Weaver layout.
Layout Properties Menu
The layout properties dialog provides information about your layout and along with some control over how the layout behaves. To edit your layout’s properties, navigate to ‘Layout → Layout Properties’ from the top banner of Audio Weaver.
The top section includes information about the current layout. The next section allows the user to control whether the input data source and output data destination is a file or an audio device. The following section provides control of .aws file generation and some extra error checking on the output pin. The .aws file will be generated in the same folder as the current .awd file. If "Validate System Output pin" is checked, then the system checks if the inherited output pin properties fall within the specified ranges for the attached hardware output pin. The final section “Protect Layout” allows the entire layout to be locked from editing.
Managing the Canvas
The AWE Designer Canvas consists of pages. You can change your drawing space using the “Layout → Canvas Size” menu.
Note: The canvas size is limited to 10x5. The zoom and align toolbar icons can be used to change your view and to easily organize your modules.
Setting Search Paths
Audio Weaver Designer comes with a few default search paths for Audio and Modules. You can add additional search paths for both modules and files (audio files, etc) via Designer.
The reason to update a module search path would be if you have created your own custom module. To add additional Module Search Paths, select File-> Set Module Path.
Module Browser/Palette
The Module Browser allows filtering by a few different parameters. You can filter the Module Browser list via data type by selecting/deselecting the boxes above the browser and under the search bar. The browser will only show modules with datatypes that match the selected boxes. For instance, if a user is not interested in any fract32 modules, they could deselect the box and see only float/int modules.
The image below shows the “Gain” modules of all data types.
The next image shows the same “Gain” category but without fract32 modules. Notice that the list is significantly shorter.
If you know the name or a keyword of the desired module, you can also use the search bar to filter the available modules.
By default, the module browser will filter out deprecated modules and missing modules (not present on the connected target). To toggle these filters, open the Designer File->Global Preferences dialog and toggle the “Show deprecated modules” checkbox. Beneath the checkbox, there is also a dropdown menu which provides the option to show all modules, filter by target, or filter by ModuleList.h (see below). Deprecated modules will appear in the browser with a yellow exclamation mark overlay, and missing modules with a red x.
Note: The image above was captured while connected to a target which does not contain the advanced module pack, therefore InvertN is missing.
An advanced feature is the ability to specify a specific ModuleList.h file as module filter. Any modules not in the specified list will appear on the canvas outlined in red.
