menu
Version
2017.1.9.6501
2024.1.3.8749
2023.1.11.8682
2022.1.18.8567
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.3.8749
2023.1.11.8682
2022.1.18.8567
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
Since motion data has a separate processing pipeline than audio, it requires its own structure of busses. To handle both motion and audio, the Master Mixer hierarchy has been divided into two main branches: one for audio and one for motion. At the top of each of these branches are the following master busses:
Master Audio Bus - A top-level output bus where the final mix for audio data is performed.
Master Motion Bus - A top level output bus where the final mix for motion data is performed.
You can create an unlimited number of busses under each master bus to group the many different objects in your project. When building a bus structure, the same features, rules, and conditions apply to both branches. Since audio and motion are handled differently, all sounds and music objects must pass through the Master Audio Bus and all motion data must pass through the Master Motion Bus.
![]() |
For more information on building an output structure for motion, refer to Overview.
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