...
Most often, the application that communicates with the target running AWE Core is the AWE Server, which is a component of the PC-based Audio Weaver Designer. When used with AWE Server and Audio Weaver Designer, the tuning interface allows for live tuning of audio system variables by sending set and query commands to the layout on the target. This allows for running automated tests and performing profiling on the target device.
Tuning The tuning interface is one of the most important parts of the Audio Weaver integration. While there are many ways to connect a target device to PC-based Audio Weaver Server, it is important for system integrator integrators to verify that the tuning interface is properly implemented, stable, and fast.
Below is our recommended test procedure to stress test your target device tuning interface.
Stability test:
The Stability test aims to test your target system’s stability in handling tuning messages under high CPU load from audio processing.
...
There should be no crashes or server disconnection disconnections during the stability test. If any occur, debugging is needed to address the issue.
...
Speed Test:
The Speed test aims to verify system responsiveness of the tuning commands. It tests the read/write speed for different vector sizes to simulate what an actual running system may deal withencounter, depending on the design and the number of inspector window windows opened. Slow response from target can result in a communication timeout and can impact tuning capability.
This test only applies to AWECore and AWECoreOS systemsystems.
Launch Audio Weaver and connect server AWE Server to the target device.
Navigate In Audio Weaver Designer, navigate to Tools → Tuning Interface Test.
Change biquad count “Number of Biquads to load” to 1000. Click “Start Test”. Note: a standard 2-channel in, 2-channel out design with 768 block size at 48khz sampling rate will be loaded to the target during the test. Layout I/O check in the target application, if any, needs to be disabled before the test to prevent an assertion error.
Monitor the CPU load in the server AWE Server window during the run. Adjust biquad count “Number of Biquads to load” to reach at least 75% CPU load in Audio Weaver the AWE Server window.
Test result results may vary depending on the interface used for tuning. TCP/IP is the recommended interface if the target platform supports it. TCP/IP normally offers sufficient bandwidth for the tuning traffic (Figure 3). AWECoreOS also provides APIs to directly enable the TCP/IP interface for easy integration (Figure 4). Other interfaces are also supported such as USB HID and Serial UART but the interface bandwidth may differ. When UART is used, the baud rate should be at least 115200 (Figure 5).
...