Wwise
Game audio middleware that turns finished assets into events, states and a mix that responds to play.
Tool profile
- Kind
- middleware
- Vendor
- Audiokinetic
- Form
- 桌面应用
- Platforms
- macOS · Windows
- Price
- 按量
- Jobs
- 游戏音频 · 交互音乐 · 声音设计 · 实现
- Verified
- 2026-10-30
Related
Wwise is not for writing music. It answers a different question: how one set of assets becomes different music and sound as the player moves, loses health or chooses. Composition stays in the DAW; Wwise decides when it sounds, how it layers and how it ends.
What it lets you finish
Join exploration and combat loops into a system that switches on state, with the switch landing on a bar line. Build segmented boss music that transitions on health without breaking the beat. Route footstep random containers through a material switch, with separate sets for grass and stone. Give dialogue a priority and a concurrency limit so three characters do not talk at once. Run the profiler on device to find clipping, voice limits and CPU peaks.
How it works
An Event is the smallest trigger and holds containers and sources. The Actor-Mixer organises buses, attenuation and effects. State, Switch and RTPC handle discrete states, category changes and continuous parameters. Interactive Music assembles segments, stingers and transitions into a structure that can change. Integration into Unity or Unreal runs through official plug-ins and code, and the runtime loads SoundBanks. Authoring runs on Windows and macOS; on-device checks come back through the profiler.
Limits and traps
- It is not a composition tool. Music and sound are finished in a DAW and imported, and loop points are set there.
- Someone must write the integration and event calls; an audio person cannot ship alone, and the interface with programmers has to be agreed early.
- The Wwise version and the engine plug-in version must be locked; upgrading one forces a regression pass.
- Projects are made of binary work units, so multi-person work needs rules for check-out, naming and merging.
- Licensing is tiered by project scale, and the terms must be read on the current official page rather than carried over from an old project.
- Middleware does not rescue weak assets, and mix problems belong in the bus structure.
Alternatives and pairings
FMOD is faster on small and mid-size projects and has a shorter learning curve. Unity's built-in audio and MetaSounds are enough for a prototype. The split with a DAW is fixed: the DAW supplies assets, loop points and a first mix; Wwise handles triggering, blending and device checks. For the music itself, finish the score in Dorico or Sibelius and cut it into segments here.
First three things to learn
Events and containers, the difference between State, Switch and RTPC, and connecting the profiler to a device. Then read Introduction to Game Audio, Interactive and Adaptive Music, and Game Loops and Interactive Layers, and take one two-layer loop from import to device.
Listen in the library
All tracks from midicn-lib — inline badge is the license tier (C1 commercial / C2 non-commercial / C3 study only).
Sources
- Wwise 的 Event、Actor-Mixer 与 Interactive Music 结构,依 Audiokinetic 公开文档核查,未抄文本
- 状态、开关与 RTPC 的分工,依游戏音频实现资料核查,未抄文本
Used for fact-checking only; all prose is original.