Understanding How Wwise Prioritizes Objects

The Advanced Settings (for playback) determine which objects are played at any point in your game. These playback settings are defined at two different levels within Wwise: at the object level in the Actor-Mixer Hierarchy and Interactive Music Hierarchy, and at the bus level in the Master-Mixer Hierarchy. Because these settings are defined at different levels within Wwise, an object must pass through two separate processes before being played.

The first process occurs at the Actor-Mixer or Interactive Music level. When you define the Advanced Settings for objects at this level, you are setting a limit that is either global or per game object. If the limit is reached, the priority then determines which objects will be passed to the bus level in the Master-Mixer Hierarchy.

The following flowchart shows how Wwise determines which sound and motion objects within the Actor-Mixer Hierarchy or which music objects within the Interactive Music Hierarchy will be played per game object. In reality, there may be several iterations through different parent objects (each of which may have its own limit) before it is ultimately decided which objects are sent to a bus.

If the new object is not killed or sent to virtual voice at the Actor-Mixer or Interactive Music level, it passes to the second process at the Master-Mixer level. At this level, it goes through a similar process based on the voice limits set within the bus structure.

The following flowchart shows how Wwise determines which objects will be output through a bus.

At this point, the global project limit, Max Voice Instances, defined in the Project Settings General tab determines if sounds are killed or put into virtual voice based on their own virtual voice settings.

[Note] Note

All the properties on the Advanced Settings tab of the Property Editor are absolute properties. For more information on absolute properties and overriding a parent’s properties, refer to Defining Absolute Properties.

Volume Threshold and Virtual Voices

Along with Playback Limit and Playback Priority, Wwise allows you to determine which sound, music, and motion objects will play based on a volume threshold. When the volume level reaches a specified volume threshold or when the number of sounds is over the limit specified in the Playback Limit, the object can do one of the following:

  • Continue to play.

  • Be killed.

  • Be moved to the virtual voice list.

The virtual voice list is a virtual environment where certain parameters of an object are monitored by the sound engine but no processing occurs. If you select this option, objects move from the physical voice to the virtual voice and vice versa based on their volume levels. If the volume returns above the Volume Threshold or the number of playing sounds goes under the limit of simultaneous playing sounds, the objects automatically move back into the physical voice. For more information on setting the volume threshold, refer to Specifying Volume Thresholds for a Project. For more information on defining the behavior of low-volume objects, refer to Managing Low-Volume Objects.

Was this page helpful?

Need Support?

Questions? Problems? Need more info? Contact us, and we can help!

Visit our Support page

Tell us about your project. We're here to help.

Register your project and we'll help you get started with no strings attached!

Get started with Wwise