Posted on by Debanka

General Limitations

The table below outlines the general limitations of AudioworX.

Limitations Descriptions
GTT/IVP crash because of propagation of wrong core type
  • Under some circumstances, it might happen that your project gets corrupted and GTT closes after clicking reboot or apply button in IVP. If GTT closes again after starting IVP, the following steps are required to recover:
  • Go to your specified VirtualAmp.dll folder and delete all flash files, and start GTT.
  • Go to your device
    • Change Core type to C66 (or any other than WIN64)
    • Save (important)
    • Change core type back to WIN64
    • Save
  • Open IVP
    • start PluginHost
  • Send device config and/or signal flow
[SMART] Label names are lost when it’s associated AO (state variable) is removed from signal flow The linking that is done before the extract will not be available on CAO edit as we are using a dummy device/core hence the hiqnet address would differ. Workaround: Do the smart window mapping only on the CAO edit.
Biquad number of channels Based on the requirement AWXNG-9194, we have a limited number of channels. GTT does not display the limited channels, but if you enter more than 64, it will show as invalid with a tooltip.
Timing based functionality may not work correctly when running signal flows which are over CPU budget for the device. Any functionality that is based on on-device time checks or GTT based timeouts, or other time checks may have failures.  Specifically, during state changes, your ramp time is based on the accumulation of increments, which are calculated up front.  Since calc is running slower, these ramping increments are also happening slower.  Likewise, the pipeline delay functionality is based on the passage of real time, not the number of calculations done, so it would not wait long enough for the cores to actually fill buffers as expected, since they are running slower than they should.  When you load slots in this condition, you may see a GTT timeout message indicating the slot load failed, but it may be it just took too long.
IVP / VST3 builds When connecting cores of different block lengths (which is possible so that it can be done on hardware and buffered outside xAF) note that it will not work in IVP or VST3 in single core processing mode. Processing will not happen when this condition occurs.
Compensation File The compensation file is only considered for magnitude curve correction; it has no impact on calculated metrics such as sound pressure level (SPL) and total harmonic distortion (THD).
Wasapi limitations
  • Bluetooth devices are not supported.
  • While selecting Loopback devices, make sure that the input device and output device are the same, with the input device name appended with ‘Loopback’, as shown below:
Unsupported Bluetooth dongles JBL Quantum 610 and JBL Quantum 800 Bluetooth dongles are currently not supported.