Overview
AWE_ProcessFile is a tool designed to perform offline processing of wav files. It loads an Audio Weaver (AWE) design and input wav file, processes the data and generates an output wav file. The initial release is for PC (Win32) and is a simple command line application that can be called from a script to allow automated file processing. Application control is via a configuration file or by command line arguments.
Configuration File
The application may be controlled by a configuration file aweConfig.txt which should be located in the same folder as the executable. The configuration file will be used if the application is called with insufficient arguments to run. The file specifies the AWE binary (.awb) to be loaded, the input and output wav files, the encryption flag and the logging level. Optionally, parameters may also be included. An example is shown below:
...
All messages are written to the console window. Level 0 disables all logging while Level 3 includes all errors, warnings and other information.
Command Line Control
Rather than using a configuration file, users may prefer to pass command line arguments directly when calling the application. Arguments should be separated with a space.
Example:
AWE_ProcessFile C:\tmp\designfiles\aweProcess.awb C:\tmp\data\in_s32_stereo.wav C:\tmp\data\out_s32.wav En1 3 30000 8 2.5e-1
Parameter Setting
If required, module parameters that are exposed may be set. In order to do this, the Control Interface file must be available. It is generated from the AWE Designer GUI under Tools->Generate Target Files. The Control Interface checkbox should be selected. To expose a specific module’s parameters:
...
Note: Pay attention to the data type of the Value to be written. These are noted as a comment just before each Offset #define in the Control Interface file. For example, gain values must be written as a float (with a decimal point): eg for +6dB, the value written should be 6.0 (not 6).
Use verbose logging (Level 3) to display the parameters and confirm how each value is being interpreted.
Encryption
Typically awb’s provided by DSPC will be encrypted. In this case, set the Encryption Flag to En1. If the awb is not encrypted, use En0. Note that the current release does NOT support encrypted files. If an attempt is made to run with an encrypted awb, the program will terminate.
Supported formats
The tool supports 16 bit and 32 bit integer wav files. The output wav file format will match that of the input file. The number of channels in the output file is determined from the AWE layout being processed (.awb file).
Sampling Rate
The sampling rate of the input wav files must match that used in the awb file. If this is not the case, the program will terminate.
Input Channel Matching
If the input wav file has fewer channels than the AWE layout, the missing channels are zero filled. Conversely, if the wav file has more channels than the layout requires, the extra channels are ignored.
Running the Application
If using a configuration file, navigate to the folder where AWE_ProcessFile.exe is located. Edit aweConfig.txt (must be located in the same folder as .exe). Type AWE_ProcessFile in a command window, or double-click on AWE_ProcessFile.exe from File Explorer.
Alternatively, call the application with command line arguments as described earlier.
Multiple input files
It can be convenient to use multiple mono files, or generally just multiple files to get the input data you want into various channels. The syntax is to use a semicolon delimited list in place of a single file like this:
...
Quotes must not be used in the configuration file even if one or more paths or names contain spaces.
...
Missing DLL Error
Several dll’s are required to run the utility. The following should be present in the same folder that the .exe is located: AWELibDll.dll, FrameDll.dll, DVUSB.dll, i2cbrdg.dll. If the awb design includes Advanced modules, ModulePackAweAdvancedDLL.dll will also be required. It is possible that older legacy designs may also need ModulePackAweDeprecatedDLL.dll.
If an error occurs regarding a missing dll such as “MSVCP100.dll” then it may be necessary to install the Microsoft Visual C++ 2010 Redistributable Package (x86) (https://www.microsoft.com/en-us/download/details.aspx?id=5555).
Help
Calling the application with a single argument “help” will display the required arguments to run from the command line.