ABSTRACT
Virtualizing inaudible or lower priority sounds allows Wwise to track a sound's state without processing the sound's voices through the mix engine in order to save CPU, memory, and in some cases hardware voices. There are two reasons a sound goes into a virtual voice mode in Wwise: the voice falls below the volume threshold, or the voice has been pushed out due to playback limits and priority settings. The "Virtual voice behavior" property is also called the "Below Threshold Behavior" in XML and code, so the two names are used interchangeably. Although the authoring tool presents this property in the "Virtual Voice" group, it is also where the familiar playback settings of "Continue to Play" and "Kill" are assigned. Of the different behaviors, "Kill if finite else virtual" is recommended as the default and hints at the expected use-case for virtual voices. Finally, micromanaging virtual voice settings per container increases the chance of errors and generates unnecessary data.
