版本
menu_open

Understanding the Components of the Memory Manager

The Wwise sound engine has a Memory Manager to manage the memory dedicated to the audio in your game. The Memory Manager is initialized by the audio programmer at the startup of your game. When initializing the Memory Manager, the programmer must also create a specific number of memory pools to manage the different audio components in your game.

There are three different types of memory pools in Wwise:

  • Default memory pool - a general usage pool for high-level sound structures. This pool mostly contains the following:

    • Audio structural content.

    • Command queue for posted events.

    • Allocations for registered game objects, game object positions, listeners, RTPCs, switches, states, and so on.

  • Lower engine memory pool - The main audio processing pipeline pool. This pool is generally used for audio playback, audio processing, memory allocated for effects, and so on.

  • Media memory pool - A general usage pool that contains a copy of the media files contained on the disk.

When creating the memory pools for your game, the audio programmer must also define their size. Once a pool is created, it cannot be resized. Memory pools can be created and destroyed during the entire lifetime of the Memory Manager. Pools are segmented into blocks of equal size representing the smallest allocation unit.

You can override the Memory Manager with any other technology, from internal to Unreal, example. For more information on implementing a custom memory manager, refer to the section Overriding the Memory Manager in the Wwise SDK documentation.


此页面对您是否有帮助?

需要技术支持?

仍有疑问?或者问题?需要更多信息?欢迎联系我们,我们可以提供帮助!

查看我们的“技术支持”页面

介绍一下自己的项目。我们会竭力为您提供帮助。

来注册自己的项目,我们帮您快速入门,不带任何附加条件!

开始 Wwise 之旅