All-in-one SoundBanks

This method applies if:

The game has a limited amount of audio and/or motion assets.
The game has plenty of free memory.

Of course, most games don't have memory to waste, but this technique has the significant advantage of being very simple to use and maintain. The main reason for using this technique is to have the entire Wwise project integrated in the game in a minimum amount of time.

To create the all-in-one SoundBank in Wwise:

Create one SoundBank, and name it appropriately.
Load the SoundBank into the SoundBank Editor and then drag the following items into the "Add" tab:
- The "\Actor-Mixer Hierarchy\Default Work Unit"
- The "\Events\Default Work Unit"
- The "\Interactive Music Hierarchy\Default Work Unit" (Only required if using interactive music)
- The "\Dynamic Dialogue\Default Work Unit" (Only required if using dynamic dialogue)
The check boxes under the Events, Structures, and Media columns are all selected by default. This is good because, for this method, we want everything to be included in the SoundBank.
Note
In a new project, only the default Work Unit is available. If more Work Units are created, these Work Units can also be added to the SoundBanks as required.
After all the Work Units have been added to the SoundBank, you can generate it and then copy the generated SoundBank folder to the game application.

	Note
In a new project, only the default Work Unit is available. If more Work Units are created, these Work Units can also be added to the SoundBanks as required.

Integration

For integration details, see The All-in-one SoundBank in the Wwise SDK documentation.

Additional notes on this method

The following table lists the pros and cons of the all-in-one SoundBank method.

Pros	Cons
Easiest way to maintain the content of the SoundBanks from the sound designer point of view. No need to recompile the game when changing the content of the SoundBanks since the game always loads the same SoundBank. No complex in-game loading and unloading of SoundBanks. No need to track in-game which sounds are available or not.	Inefficient usage of memory because all Events, structures, and in-memory media for the entire game are loaded at all times.

Pros

Cons

Easiest way to maintain the content of the SoundBanks from the sound designer point of view.

No need to recompile the game when changing the content of the SoundBanks since the game always loads the same SoundBank.

No complex in-game loading and unloading of SoundBanks.

No need to track in-game which sounds are available or not.

Inefficient usage of memory because all Events, structures, and in-memory media for the entire game are loaded at all times.

Even though this method is a good way to quickly and easily integrate the audio and motion in your game, don't wait until the end of the project to switch to a method that makes better usage of your game's memory.

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.

Get started with Wwise

Wwise Help