Wwise Help

Click the View Settings icon in the upper right corner of the view.

The Object Property Settings dialog box opens. Select the individual properties for every possible Wwise object type that you wish to display.

Click the Configure Columns... shortcut (right-click) option from the column header band.

The Object Property Settings dialog box opens. Select the individual properties for every possible Wwise object type that you wish to display as a column.

Opens a search field where standard alphanumeric entries filter out unmatching elements from the view. Learn more in Using Tables.

Click the Close icon to the left of the search icon to close the search field and remove the filter.

	Note
	The searches do not include elements in collapsed nodes of the List View, Query Editor, MIDI Keymap Editor, and Reference View.

Common Columns: If the following properties are selected in the Object Property Settings, they are always present as columns in the results area. Other columns display according to which types of objects are listed in the Results area.

Name

The name of the object or project element that matches your search criteria.

Path

The location in the project hierarchy of the object or project element.

Notes

Defines the notes or comments specified for the object or project element.

Type

The type of object or project element included in your results. For example: sound, bus, SoundBank, Query, Effect, and so on.

Default value: All Objects

Controls the Mute and Solo states for the object and shows the implicit mute and solo states for the object.

Muting an object silences this object for the current monitoring session. Soloing an object silences all the other objects in the project except this one.

A bold M or S indicates that the Mute or Solo state has been explicitly set for the object. A non-bold M or S with faded color indicates that the object's Mute or Solo state was implicitly set from another object's state.

Muting an object implicitly mutes the descendant objects.

Soloing an object implicitly mutes the sibling objects and implicitly solos the descendant and ancestor objects.

	Tip
	Hold the Ctrl key while clicking a solo button to exclusively solo the object for which the solo button is associated.

	Note
	Mute and Solo are designed to be used for monitoring purposes only and are not persisted in the project or stored in the SoundBanks.

Size Previews: All the Size Preview values are calculated when opening the view. They will, however, auto-refresh when there are fundamental changes, such as changing the platform.

	Note
	Any fields marked as "-" are either incalculable or inapplicable to the object in question.

Total Size

The sum of the element's Media Size and Structure Size, which approximates the total size that they will take up in a SoundBank.

Media Size

An approximation of the total size that a Wwise object's media files, including converted source files, Events, and Effects, will take up within a SoundBank.

	Note
	For Effects requiring a license, their size value is not included unless the appropriate license is entered.

The parent object will only display the size of the normally smaller audio buffer files if its media files are set to stream with Zero latency. No size displays for the parent object if its media files stream without Zero latency.

	Caution
	There are many situations where the media size of an object has changed but the view is not updated. To ensure that all sizes are up to date, use the Refresh All Sizes shortcut menu option. To update one or several specific items, select them and use the Refresh Size shortcut menu option.

Object Size

An approximation of the size Wwise objects, excluding the size of sound files on disk, will take up within a SoundBank.

	Note
	Actions do not have any size. And objects that are only in the Init bank, such as Game Syncs, are not included.

Structure Size

An approximation of the size an object (Object Size) and its structural descendants will take up within a SoundBank.

Other Columns: Apart from the columns listed above, many object-type-specific properties can be added as columns. These will display according to your results, when the query returns a configured column's property.