Framework Feature Configurability

With the R-Release a new configuration option has been added. By default the high configuration will be build. Following configurations are supported and can be selected:

  • low
  • high (additional features)
    • Swag (Mips & Memory)
    • ProbePoint (formerly LiveStreaming)

To utilize this functionality you can append this argument to the python build commands: –featureConfig=high or -fc=high

These two commands result in mostly the same binary but with these exceptions.  Low will exclude AudioProcessing and AudioCore and provide only AudioProcessingBase and AudioCoreBase.

When implementing as a platform developer – either with or without AudioCore – you will choose your feature set by choosing which class to instantiate.

Here are examples from our IVP project

Implementing AudioCore for full features (when building with -fc=full) class CVSTCore : public CAudioCore, public CWinCoreShared 

Implementing AudioCoreBase for the basic features (no profiling or probe points) class CVSTCoreLite : public CAudioCoreBase, public CWinCoreShared

It is worth noting you can build full and instantiate the lite class – they’re included.  You’ll just have to rely on your linker settings to exclude the extra code.

As above – if implementing only for AudioProcessing the same applies.  AudioProcessing vs AudioProcessingBase.

_________________

Rate this post!