menu
Version
2017.1.9.6501
2024.1.5.8803
2023.1.13.8732
2022.1.19.8584
2021.1.14.8108
2019.2.15.7667
2019.1.11.7296
2018.1.11.6987
2017.2.10.6745
2017.1.9.6501
2016.2.6.6153
2015.1.9.5624
2024.1.5.8803
2023.1.13.8732
2022.1.19.8584
2021.1.14.8108
2019.2.15.7667
2019.1.11.7296
2018.1.11.6987
2017.2.10.6745
2017.1.9.6501
2016.2.6.6153
2015.1.9.5624
In Wwise, Master-Mixer Hierarchy objects (busses) are handled under the hood as non-mixing busses, unless they need to be converted to mixing busses. Non-mixing busses propagate their bus properties to their inputs because it is a more efficient use of CPU and memory. A non-mixing bus is promoted to a mixing bus when such propagation would not work because:
One way to verify the status of the bus is by inspecting the Voices Graph tab or the Busses tab of the Advanced Profiler while capturing. Only mixing busses appear there; non-mixing busses do not.
As seen below in the screenshot taken from the Wwise Integration project, the Environmental Bus must be non-mixing because it does not show up in the Advanced Profiler's Busses tab while its child Hangar_Env Auxiliary Bus does. Incidentally, as a non-mixing bus, the Environmental Bus's volume is included in the Hangar_Env Auxiliary Bus Bus Volume column.
![]() |
Questions? Problems? Need more info? Contact us, and we can help!
Visit our Support pageRegister your project and we'll help you get started with no strings attached!
Get started with Wwise