Since you will be building complex structures in your game, you will need to understand how the different properties are applied to objects within the hierarchy. In Wwise, the properties of an object are divided into two categories:
Relative properties - Cumulative properties that are defined at each level of the hierarchy, for example pitch and volume. The sum of all these values determines the final property value. It is important to know that each relative property will be capped when it reaches either the minimum or maximum limit. The limits for each property are described below:
Volume: (-200 to +200) in dB
Pitch: (-2,400 to 2,400) in cents
Low-pass filter: (0 to 100) in percent
High-pass filter: (0 to 100) in percent
![[Note]](/images/2022.1.17_8543/?source=Help&id=note.png)
Note Not all relative properties are available for all objects and on all platforms.
Note The cumulative behavior of filter properties, such as Low-pass filter and High-pass filter, can be configured. Refer to Understanding Property Filter Behavior (LPF, HPF).
Absolute properties - Properties that are defined at one level, usually the highest, in the hierarchy and then passed down to all child objects below it. For example, output routing for objects. While you can configure these settings at the highest level in the hierarchy, they will actually be applied at each level below. An absolute property can be overridden at each level in the hierarchy.
The following illustration demonstrates how the two types of property values work within the project hierarchy.
 |
Absolute properties: In this example the Output Bus is specified by the Actor-Mixer object. This specifies the Output Bus for the Actor-Mixer object and all its descendants that do not specify an Output Bus. |
 |
Relative properties: In this example each object specifies a relative offset to the Volume property. The sum of the property values is the Volume offset applied to the Sound object. |
After you have imported the assets into your project and organized them into a logical structure using the different object types, you can start defining the specific properties and behaviors of each asset.
Each object in Wwise has its own set of properties and behaviors that you can use to define and differentiate it. The properties, such as volume and pitch, define the characteristics of each object. The behaviors, such as looping and streaming, determine how the object is played back.
You can also define the properties and behaviors for all object types within the hierarchy. This allows you to control the properties of an entire group of objects, and to determine which objects within the group will be played back and in which order.
You can also apply certain Effects to the different objects to create that unique experience that you are aiming for. When applying Effects at the highest level in the hierarchy, it is important to note these Effects are actually applied at each level below.
Was this page helpful?
Need Support?
Questions? Problems? Need more info? Contact us, and we can help!
Visit our Support pageTell 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