Generate Target Files
Audio Weaver can generate “Target Files” that can be used with an AWE Core integration. For example, you can compile your Audio Weaver layout to an AWS file which will be a list of all the Server commands that make up a design.
...
For more information about how to use these target files, please see the AWE Core 8 API Quick Start.
Attach to Running Target
If a target BSP uses AWE Core to locally load an AWB, Designer can still connect to the target and manipulate that layout without interrupting the ongoing processing. This can be extremely useful for troubleshooting, and is referred to as “Attach(ing) to a Running Target”
...
When you are done tuning, the target can be detached by selecting Designer’s “Tools/Detach from Target” menu item.
Module Testing
The Module Tests are used to verify that modules are properly implemented on a connected target. There are two types of tests that can be run from the Tools -> Module Tests menu: Regression Tests and System Tests.
...
After selecting the “Start Test” button, the tests will be executed and the results will appear in the “Results” pane. The results can be saved to a CSV file using the ‘Save Results’ button.
...
Real-Time Profiling
When a layout is running, its computation and memory usage can be measured by selecting the ‘Tools 🡪 Profile Running Layout’ menu item. This will pop up a dialog displaying fine grained profiling information for the entire layout and for each module.
...
Manual Profiling
In addition to the real-time profiling offered by Profile Running Layout menu, Designer also provides the ‘Tools 🡪 Manual Profile Layout’ tool. The Manual Profiling tool manually pumps each sublayout in a design with tuning commands, which does not rely on any real-time audio interrupts. Collecting data in this way allows for more accurate profiling in certain situations:
...
Additionally, the Manual Profiling tool allows the user to input an audio file in order to profile the layout under specific scenarios. Both real-time and manual profiling results can be saved to file for later use using the ‘Export to File’ button. Results will be refreshed using the ‘Refresh’ button.
Show Unsaved Changes
To see all the changes since the last save, select ‘Tools Show Unsaved Changes’ for a display using the diff tool the you set in the ‘Global Preferences’ Dialog.
...
Compare Layouts
Two layouts can be compared by selecting the ‘Tools → Compare Layouts’ menu item and selecting the AWD files associated with the layouts.
...
Diffing Systems
Audio Weaver layouts can also be compared using a ‘diffing’ capability. This can be useful for example to figure out changes between different versions of a layout during the design and tuning process. This functionality requires a Diff tool like WinMerge, to be installed. First specify your Diff tool under the ‘File → Global Preferences’ menu item, then use the menu item ‘File → Compare Systems’ to make the comparison between two different layouts.
...
For quick diffing, LST files can also be generated / compared.
Measurements
Many modules have associated frequency responses. The measurement dialog measures the composite frequency response between two points in your signal processing layout. To set up a measurement, first place marker modules at the beginning and end points of the desired measurement path in the layout.
...
Here you can select all the properties of the measurement display. When you push the OK button, an editable measurement graph will be displayed.
...
Tuning Interface Test
This function performs diagnostic measurements on a connected tuning interface, and is handy to have when developing an AWE Core BSP, or while troubleshooting a tuning interface implementation. The functionality can be accessed via the ‘Tools Tuning Interface Test’ menu item. Test results indicate the interface speed under various conditions, defined by the user in the Test window.
...
Comma separated list of vector lengths to test
Number of Biquads to load
Number of seconds to run each test.
Flash Manager Tool
| Anchor | ||||
|---|---|---|---|---|
|
The Flash Manager tool, which is delivered as part of the AWE Server, enables users to easily add and remove Audio Weaver Binary files (AWB) on targets that support flash file systems. Once added to flash, the AWB file will be loaded by the AWE Core at boot-time and the target can run in stand-alone operation. See the next section ‘Using the Flash Manager’ for instructions on how to do this.
Note that another alternative for stand-alone operation is to store the AWB contents in a C array and compile it into an application directly. This method can be used on targets with or without a flash file system. For more information on this, see Standalone Operation.
Using the Flash Manager Tool
Generate an AWB file for your desired Audio Weaver design (AWD ) in Designer by going to ‘Tools -> Generate Target Files’.
Select ‘AWB’ target file type and choose the directory to which the AWB file will be saved. Change the ‘Save Basename’ field to a name that is less the 16 characters, then hit the “Generate” button. It will then start compiling the system for creation of the AWB file.
Once the AWB file has been successfully generated, the following window will appear:
In AWE Server, select ‘Target -> Change Connection’ and connect to your target with the appropriate option.
In AWE Server, select ‘Flash -> Flash Manager’. Then press “Add File” button.
Browse to the previously-created AWB file and select it as the input file. Ensure that the file type is “Compiled Script” and check the box next to “Boot file” to designate this file to be used at boot-up (attribute = 26). Click the “Add” button to load the file into memory.
Once the progress completes, click “OK”.
After the file has been added, it will show up in the list “Flash file system on target” in the Flash Manager window. When you reset your target hardware and reconnect AWE Server to it, you should see a non-zero CPU % and heap allocated in the AWE Server, which indicates that the layout is indeed running.
Overflow Detection
On certain targets, AWE Core will detect any overflow conditions while a layout is running and present this information in AWE Server. An “overflow” occurs when the previous pump is not completed before attempting to schedule the next pump. The overflow logic is capable of detecting overflows in any of the sublayouts in a multi-rate layout.
...
Note: This feature is currently supported only for AWE Core based targets and is not supported on Native or AWE Core OS targets.
Process Files Tool
...
The Process Files tool can be used to process audio files through a layout and record the output as WAV files. The tool accepts MP3 and WAV files as input, but always generates a WAV file as output (even if an MP3 file is provided).
...