How To Export SoundBank From Wwise

How To Export SoundBank From Wwise

Wwise 2024.1 What'S New _ Defining the SoundBank settings for your ...

Exporting SoundBanks in Audiokinetic Wwise is the critical final bridge between interactive audio design and game engine implementation, transforming your hierarchical event and asset structures into optimized binary packages. Mastering this workflow requires precise platform targeting, SoundBank generation settings management, and proper output directory configuration to ensure flawless integration into engines like Unreal and Unity.


Pre-Production & Workflow Requirements for SoundBank Generation

Proper preparation of your Wwise project architecture prevents runtime memory bottlenecks, missing audio assets, and unlinked event triggers during the SoundBank generation phase. Before initiating the export process, ensure your project dependencies, conversion settings, and platform configurations are fully synchronized and validated.



  • Essential Tools & Software: Audiokinetic Wwise Authoring Tool (matching the exact major and minor version of the target game engine integration), target game engine (Unreal Engine 4/5 or Unity) with the official Wwise plug-in installed, and adequate local disk space for high-resolution uncompressed asset caching.
  • Mandatory Prerequisite Knowledge: Familiarity with Wwise project hierarchy, Event-to-SoundBank associations, Source Control systems (Perforce, Git, or SVN), and platform-specific audio codec limitations (such as Opus, ADPCM, or PCM).
  • Time & Scope Benchmarks: Project export and generation times typically range from 30 seconds for small indie titles to 15 minutes for massive open-world projects containing tens of thousands of audio assets and multiple platform streams.

Step-by-Step Guide to Generating and Exporting Wwise SoundBanks

Executing a clean SoundBank export requires navigating the SoundBank Manager layout, selecting the appropriate generation flags, and confirming output path integrity across all designated platforms. Follow this sequential workflow to ensure your audio assets compile correctly without throwing metadata corruption errors.



Step 1: Access the SoundBank Manager and Layouts

Navigate to the top menu bar within the Wwise Authoring Tool and select Layouts, then choose SoundBank, or use the default keyboard shortcut (F7) to switch views. The SoundBank Manager pane typically populates on the left side of the interface, displaying your hierarchical list of SoundBanks categorized by user-defined groups and language settings. Verify that all newly created or modified Events, Work Units, and audio structures are explicitly dragged and dropped into their respective SoundBanks before proceeding.

Pro-Tip: Always use the Project Explorer filter system to check for orphaned Events or unassigned audio objects that might have been omitted from your target SoundBanks.



Step 2: Configure Platform and Language Targets

Within the SoundBank Manager pane, locate the matrix grid displaying your project platforms (such as Windows, PlayStation 5, Xbox Series X, and iOS) and localized languages (such as English, French, or Japanese). Check the generation boxes corresponding to the exact platforms and languages you intend to export for the current build phase. Avoid generating unused platforms simultaneously, as redundant transcoding significantly increases build times and fills your local development folders with unnecessary binary files.



Step 3: Validate Conversion Settings and Audio Quality

Before hitting the generation trigger, review your Conversion Settings ShareSets assigned to your Actor-Mixer hierarchy. Open the Conversion Settings Editor to confirm that sample rates, compression codecs (such as Wwise Opus for general assets or PCM for low-latency UI elements), and quality factors align with the performance budget of your target platform. Running a SoundBank generation without updating stale conversion parameters can result in runtime clipping, excessive memory footprints, or platform playback crashes.

Warning: Modifying conversion settings alters file sizes and seek tables; always perform a full regeneration of your SoundBanks rather than an incremental update when major codec changes occur.



Step 4: Execute SoundBank Generation and Verify Output Paths

Locate the Generate SoundBanks dialog box, which can be opened by pressing Shift+F7 or clicking the Generate button within the SoundBank Manager. Ensure that the "Generate SoundBanks" checkbox is active alongside any optional metadata generation flags required by your game engine, such as SoundBank Info (.json or .xml) files. Confirm that the root output path points directly to the streaming assets folder of your game engine directory (for instance, Content/WwiseAudio for Unreal or Assets/StreamingAssets/Audio for Unity) to eliminate manual file copying errors. Click Generate and monitor the Output Log for any red error warnings regarding missing media or duplicate Event IDs.


How to Create Audio-Reactive Objects Using Wwise and Unity | Audiokinetic

How to Create Audio-Reactive Objects Using Wwise and Unity | Audiokinetic

Wwise Platform Codec and Export Parameter Matrix



Platform Target Recommended Primary Codec Maximum Target Sample Rate Default Output File Extension Memory Footprint Strategy
Windows / PC Wwise Opus / PCM 48 kHz / 96 kHz .bnk / .wem High fidelity, stream large ambient loops from disk.
PlayStation 5 hardware-accelerated ADPCM / Opus 48 kHz .bnk / .wem Utilize hardware decoding to minimize CPU thread overhead.
Xbox Series X/S Wwise Opus 48 kHz .bnk / .wem Balance memory pools between streaming and in-memory assets.
iOS / Android Wwise AAC / ADPCM 44.1 kHz / 48 kHz .bnk / .wem Aggressive compression for mobile app size restrictions.

Troubleshooting Common SoundBank Export Failures

Resolving compilation errors, missing reference warnings, and missing metadata issues requires a systematic approach to debugging the Wwise project database and file structures.



  • Root Cause: Missing Media Files Error during generation. Wwise references an audio source object whose physical .wav file was moved, renamed, or deleted from the original sources folder.

    • Actionable Fix: Use the Project Explorer search function to locate the missing asset, right-click to access Source Management, and re-import or relink the correct audio file path before regenerating the SoundBank.
  • Root Cause: Outdated SoundBank Info (.json) files causing integration desynchronization in Unreal or Unity. The game engine reads old Event IDs because incremental generation failed to overwrite metadata.

    • Actionable Fix: Perform a completely clean generation by clearing the generated SoundBanks cache folder manually in your project directory, then execute a full generation across all platforms in Wwise.
  • Root Cause: Duplicate Event ID conflicts across multiple SoundBanks. Two distinct events share conflicting short IDs due to naming collisions, causing unpredictable audio triggers in-game.

    • Actionable Fix: Open the Advanced Profiler or SoundBank generation log to identify the colliding names, rename one of the conflicting events to alter its generated hash ID, and regenerate the affected SoundBanks.

Frequently Asked Questions



Where are exported SoundBank files physically located on my computer?

By default, Wwise exports SoundBanks to the GeneratedSoundBanks folder located directly within your primary Wwise project root directory, subdivided by platform name. However, professional workflows typically redirect this output path directly into the designated audio streaming asset folders of your target game engine project directory.



What is the difference between incremental generation and a full SoundBank regeneration?

Incremental generation only compiles SoundBanks and media files that have been modified since the last generation timestamp, saving considerable time during iterative development. A full regeneration forces Wwise to re-evaluate and recompile every single asset, event, and conversion setting in the project, which is necessary when changing global project settings or troubleshooting corruption.



Why are my audio assets silent in the game engine after a successful export?

This issue typically occurs because the generated SoundBank Info files (.json) were not copied to the game engine, or the game engine's Wwise initialization component failed to load the Init.bnk file at startup. Verify that your game engine's audio integration plug-in points to the exact directory where your SoundBanks were exported.



How do I handle localized audio streams when exporting SoundBanks?

Localization requires you to assign audio files to language-specific SoundBanks or language folders within the SoundBank Manager. During export, you must explicitly check the boxes for each desired language so Wwise compiles localized .bnk packages that your game engine can swap dynamically based on user settings.



Can I automate the SoundBank export process for continuous integration pipelines?

Yes, Audiokinetic provides command-line arguments for the Wwise Authoring Tool that allow developers to trigger SoundBank generation automatically via build scripts, Jenkins, or Python automation scripts without opening the graphical user interface.

Streamline your interactive audio pipeline today by establishing automated Wwise export routines that guarantee synchronization between your sound design workspace and your game engine builds.


How do I upgrade the AeroBand Guitar Soundbank? - AeroBand Help Center

How do I upgrade the AeroBand Guitar Soundbank? - AeroBand Help Center

Read also: How to Move to London From America: The Complete Expatriate Relocation Manual