...
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.
...
Logging in Audio Weaver
If you are having issues or trying to debug the tuning interface, turning on logging can be a big help. See the image below for information on our different logs and how to enable/disable them.
...
AWE Server Menus
List Modules
...
Each module has an associated runtime status with 4 possible values:
Active
...
— The module's processing function is being called. This is the default behavior when a module is first instantiated.
Muted
...
— The module's processing function is not called. Instead, all of the output wires attached to the module are filled with zeros.
Bypassed
...
—The module's processing function is not called. Instead, the module's input wires are copied directly to its output wires. Some modules use an intelligent generic algorithm which attempts to match up input and output wires of the same size. Other modules implement custom bypass functions.
Inactive
...
— The module's processing function is not called and the output wire is untouched. This mode is used almost exclusively for debugging and the output wire is left in an indeterminate state.
| Note |
|---|
Use Inactive runtime status with caution! |
...
Start the AWE Server on your Target. This can either be a local AWE Server on another PC or something like AWE_command_line. Make sure you know the IP or hostname of your target that’s running the server.
Open the Global Preferences window from the file dropdown menu
Switch the “Connection Type” dropdown from Local Server to Remote Server.
Enter the IP or hostname of your remote target. The click “Reconnect to Server”
If a successful connection is made, you will see a “Connected” string appear under your remote connection string. You will also notice that the default Audio File path has changed to your target’s filesystem.
Now you can run your Designer layout on your remote target as if you were connected to a local target.
...
The predefined variables section automatically defines symbols derived from the layout’s HW input pin. If the HW input attributes are changed, these symbol values will also change to match. The TOP convention is used in these variables to indicate that they represent the top level input and output pin values.
TOP_SAMPLERATE
...
— the sample rate of the HW input pin
TOP_BLOCKSIZE
...
— block size in samples of the HW input pin
TOP_BLOCKRATE
...
— HW input sample rate divided by the HW input block size
TOP_NUMIN
...
— HW input pin number of channels
TOP_NUMOUT
...
— HW output pin number of channels
User Variables
The user variables section is where arbitrary symbols can be defined by the user. Symbols must be entered as <SYMBOL> = <VALUE>, one per line. Symbol names must begin with a letter. Symbol characters must be upper or lower case letters, digits, or underscore characters. No other characters or special symbols are allowed. If other text or spaces are entered they will be stripped out when the dialog is closed. For example, a user might define a symbol like “SIGNAL_NOISE_RATIO_THRESH”, and then use it in any module argument field in the layout anywhere that SNR is evaluated.
...