Wwise Help

Consider a sample project with the following contents:

After SoundBank generation has completed successfully, Wwise will have created the file structure shown in the following figure:

	Output folder for the Windows platform.
	Output folder for localized SoundBanks. There is one folder for each of the project's languages. Refer to Managing languages for more details.
	SoundBank file sb_hello.bnk. Because the SoundBank contains localized assets (Voice hello.wav) the SoundBank is also localized.
	SoundBank file sb_beep.bnk. Because the SoundBank does not contain localized assets (SFX beep.wav) the SoundBank is not localized.
	Metadata file sb_beep.json. This file contains metadata on the contents of SoundBank sb_beep.bnk.
	The Init SoundBank is automatically created by Wwise for all projects, regardless of SoundBank settings.
	Metadata file SoundBankInfo.json. This file contains metadata for all SoundBanks generated.
	Metadata file PlatformInfo.json. This file contains metadata for the last SoundBank generation configuration.
	Metadata file ProjectInfo.json. This file contains metadata for the Project's configuration during the last SoundBank generation, such as the list of platforms.

	Note
	Metadata files are optional and are generated according to the user's SoundBank settings. Refer to SoundBanks Tab for details.

The previous section described the output folder structure for user-defined SoundBanks. User-defined SoundBanks are those listed in the SoundBanks tab of the Project Explorer.

The project might be configured to automatically define SoundBanks. If so, Wwise will generate SoundBanks for certain project objects. See Auto-defined SoundBanks for details.

To better understand, consider the following changes to the sample project described in SoundBank files:

For auto-defined SoundBanks, Wwise creates a new SoundBank hierarchy for each object type, using the same structure described above for user-defined SoundBanks. In the updated sample project, Wwise creates a new folder hierarchy for auto-defined Event and Bus SoundBanks. The following figure shows the updated folder structure and generated files.

	A new folder hierarchy is created for SoundBanks auto-defined from Event objects.
	The new folder hierarchy has the same localization folders as the hierarchy for user-defined SoundBanks.

	Note
	For simplicity, the figure omits the following: Metadata files. Metadata files are created for Auto-defined SoundBanks using the same SoundBank Settings as for user-defined SoundBanks. Auto-defined SoundBanks for Busses.

Your Project's SoundBanks might not contain all the required media files. Media files not included in SoundBanks are left out for a variety of reasons, such as:

See Auto-defined SoundBanks for further details.

The SoundBank Settings can be configured to copy the missing media files to the output folder. In this case, Wwise creates a new folder hierarchy for the copied media files. Refer to Managing SoundBank media for details.

Referring to the same sample project described in SoundBank files, Wwise will not include the media files referenced by the auto-defined SoundBanks:

To better illustrate, assume that Wwise has assigned the Media IDs as follows:

The following figure shows the updated folder structure with the copied media files.

	The root folder of the Media folder hierarchy.
	The Media folder also has its localization hierarchy.
	Media file footstep.wav, copied and renamed using its assigned Media ID.

For large Projects, it's not uncommon to end up with an output folder with thousands of files. The majority of these files tend to be in the Media and auto-defined SoundBanks folders. This can lead to issues on platforms that enforce limits on the number of files per folder. Wwise offers the SoundBank setting Sub-folders for Generated Files to further divide the files of each folder into sub-folders. See SoundBanks Tab for more details.

When the setting is enabled, Wwise moves files of the following types:

In each case, the first two digits of the file's ID (decimal format) is used to determine the sub-folder name. In the case of media files, that's simply the first two characters of the file name. For SoundBank files, the SoundBank's ID is used. A SoundBank's ID can be obtained from either its associated metadata file, the global metadata file SoundBankInfo.json, or by calling the API function AK::SoundEngine::GetIDFromString.

The following figure shows the contents of the output folder with the setting enabled. This example assumes that the SoundBank name resolves to the following IDs:

Note that user-defined SoundBanks are not moved to sub-folders. Sub-foldering only applies to the auto-defined SoundBanks and Media folders.