Wwise Help

You can convert many audio files at once by right-clicking a high-level object in the hierarchy, such as a container, and then selecting Convert from the shortcut menu. If you want to set the Conversion Settings for an entire group of objects, you can right-click the top-level object and select Conversion Settings from the shortcut menu. You can also multi-select objects in the Project Explorer and then define their Conversion Settings or convert them all simultaneously.

Many times, when a studio develops a game, it examines each platform and then allocates a “budget” for such items as the memory footprint, CPU, and bandwidth. The audio team is given a portion of this budget and it is up to them to manage this budget efficiently for each platform. Depending on the platform, these allowances will be different, so the audio designer needs to understand how to efficiently compensate for these differences and still deliver great sound using the various Conversion Settings available. To see how well you are doing, you can monitor your project's performance in game using the Game Profiler, and adjust the Conversion Settings as needed to stay within your budget.

Audio formats must also be considered in your budget. It is useful to review the characteristics of the different formats supported by Wwise so that you can make good choices for your project. A general rule is that the less a file is compressed, the less processing power is needed; however, an uncompressed file usually uses more memory or disk space.

The following table provides you with some basic suggestions and information to help you decide how to encode your audio files.

By default, the Vorbis encoder uses a Seek table granularity (sample frames) of 16384. While seek tables are not always necessary, you must use one in the following circumstances:

To enable the seek table for a selection of Vorbis encoded files, do the following:

Smaller seek table granularities require more memory. Sample-accurate seeking (interactive music or seek actions) may incur a CPU spike if granularity is too large, and inefficient I/O usage if it is larger than the disk streaming granularity. As a rule of thumb, pick a seek table size that is smaller or equal to your disk streaming granularity, which is the value used for AkDeviceSettings::uGranularity during initialization.

	Seeking can fail if the file is too small
	If the file is smaller than or very close to the size of the Seek table granularity, seeking may fail. In such cases, make the Seek table granularity smaller.

WEM Opus is a particular format in that its decoding behavior is dependent on the platform's capabilities. Specifically, WEM Opus will attempt to use hardware acceleration on platforms that support it. Therefore, its limitations (and overall usefulness) depend on the target platform.

On most platforms, WEM Opus is decoded on the CPU, similar to Opus (standard). When this is the case, its limitations are similar to Opus (standard): overall higher CPU usage than Vorbis, in exchange for better compression. It is worth noting, however, that seeking operations have been optimized compared to Opus (standard) for streamed media.

When the target platform supports Opus hardware acceleration, this limitation goes away: CPU usage will be very low, even when seeking. For these platforms, the Wwise sound engine will expose an option to turn on or off low-latency hardware decoding during initialization:

Note that this option is a global setting; it is not possible to toggle it on or off for individual sounds. The trade-offs must be carefully considered in the context of your project's specific use cases.

Please consult your target platform's specific SDK documentation page to learn whether it supports Opus hardware acceleration, and how to turn on or off low-latency decoding.