| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
This page is a work in progress. Improvements to content and formatting are underway. |
Overview
As shown below, there are 3 main components of an Audio Weaver system that require communication in order to tune an audio system. The Designer GUI will generate text based tuning commands (AWS) based on the layout and any user tuning commands. These commands are sent to AWE Server, which in turn compiles the AWS commands into binary commands (AWB) that can be sent to the target running the AWE Core. The target processes the AWB commands and then generates a reply message that is sent back to the AWE Server.
...
Returns the number of cores (or instances) defined by the target, and all their IDs. See also get_instance_table below which is an alias.
success,number of cores, <list of core IDs>
...
Returns the next object in the forms described in get_first_object, or:
failed, no more objects
...
expression is as described in get_value,
value is a number to be assigned to the location described by expression
...
For more about binary packets, including a detailed list of available commands, see AWE Core Tuning Command Syntax and Protocol .