Below features are developed across the domains of AudioworX ( xAF and GTT).
Features | Updates |
Master Control | This feature enables users to route control signal(s) on device level. This means, that now controls can be routed across xAF instances and (Virtual) Cores.
Key features
In y-release, group size is restricted to 256 but will be extended to 2^31 in y+1 release.
|
Core dependent Audio and Core Object filtering | This feature allows the AO developer to specify supported cores for the audio or core object. Third party objects not always support all AWX supported target processors. This feature enables the developer to restrict the usage of the audio object only for the supported targets. This is an extension of the supported block length and sample rate feature.
![]() ![]() Key features
|
IVP Soundcard setup | This feature enables the user to use new host APIs for the sound card configuration. For low latency requirements the newer WASAPI host can be used instead of MME if no ASIO ™ device is available.
Key features
|
Third-party framework inside AudioworX as a core audio object | This feature enables customer to integrate AWE audio objects into AudioworX without any effort. With the help of bridge application, user will be able to tune AWE audio objects using AWE designer/Tools.
Key Features |
AudioworX Starter Kit Updates
- Enabled support for HiFiBerry DAC8x and ADC8x Add-on.
- Improved latency is achieved with the Starter Kit.
- Starter Kit has been updated to include an option for MIPS measurement from real-time clock.
- New example GTT project included for the AudioworX Starter Kit with support for 8 inputs and 8 outputs (HiFiBerry DAC8x and ADC8x add-on combination).
- Implemented and tested SKUtility-UI tool to enable Raspberry pi board control through a graphical Interface.
- Changed Starter Kit target installation directory on the Raspberry Pi for better portability.