Note: when a mobile game stutters due to audio, it's not a bug but an architectural flaw. On Android, standard AudioTrack latency can reach 200 ms (unacceptable for rhythm games or shooters). FMOD Studio with AAudio support cuts it to 20 ms. Replacing Wwise with FMOD Studio in a $50k project saved 30% setup time and $12k in licensing (Wwise Indie threshold $150k, FMOD Studio is free up to $200k).
We integrate FMOD Studio into games on Unity and Unreal Engine. We work with event models, adaptive music, DSP effects. This article covers key technical decisions for mobile platforms, including Events, Banks, Parameters, and output configuration for OpenSL ES and AAudio.
FMOD Architecture in a Mobile Project
FMOD Studio is based on an event model: each sound is an EventInstance controlled from code via API. Events contain tracks, effects, transition logic. Banks (.bank) store all data — we load them selectively: Master.bank, Music.bank, SFX.bank. Typical memory budget on a mid-range Android is 32–48 MB, controlled by virtual voice limit (64) and streaming for long tracks.
Game code creates and manages EventInstance:
// Unity FMOD — start event FMOD.Studio.EventInstance footstepEvent; void Start() { footstepEvent = FMODUnity.RuntimeManager.CreateInstance("event:/Character/Footstep"); } void PlayStep(string surface) { footstepEvent.setParameterByName("Surface", GetSurfaceValue(surface)); footstepEvent.start(); } void OnDestroy() { footstepEvent.release(); } All events are stored in .bank files — FMOD Banks. Typical structure for a mobile project: Master.bank (metadata), Master.strings.bank (event names), plus separate banks by category (Music.bank, SFX.bank, UI.bank). Banks are loaded via FMODUnity.RuntimeManager.LoadBank.
Parameters and Interactivity
FMOD Parameters are the analog of RTPC in Wwise. A parameter Intensity (0–10) on a music track changes mix: at 0 only ambience, at 10 full battle arrangement. Continuous parameter updates in real time, Labeled parameter gives discrete states (Calm, Tense, Combat).
Timeline in FMOD Studio: Cue markers allow code to rewind the track to a specific point via EventInstance.setTimelinePosition. This is used to sync music with cutscenes or level phases without hardcoded temporal ties in code.
Transition Regions on the Timeline — an FMOD Studio feature: you can define "transition zones" that the track jumps to when a parameter changes. This is simpler to set up than Wwise's Music Switch Container, but less flexible for complex adaptive systems.
How FMOD Solves Latency on Android?
Audio output on Android. FMOD Studio recommends FMOD_OUTPUTTYPE_OPENSL for Android API < 26 and FMOD_OUTPUTTYPE_AAUDIO for API 26+. AAudio gives lower latency (~20 ms vs ~50–100 ms with OpenSL ES). Configured via FMOD.System.setOutput or through FMODUnity.Settings in Editor. In our practice, latency drops 2–3 times on modern hardware. According to AAudio documentation, minimum latency is achieved in exclusive mode.
iOS AVAudioSession. FMOD Studio automatically sets the .playback category. Problems arise with Mixed Reality or VideoPlayer — category conflicts. You need to configure FMODUnity.Settings.forceSpeakerOutput and check behavior on incoming call: FMOD Studio should restore the session via AudioInterruptionNotification.
Output type comparison on Android
| Output type | Android API | Latency (ms) | Recommendation |
|---|---|---|---|
| OpenSL ES | <26 | 50–100 | Legacy but compatible |
| AAudio | 26+ | 15–25 | Preferred for games |
| AudioTrack | any | 100–200 | Not recommended |
Differences from Wwise
Based on our experience, FMOD Studio is 2–3 times faster to set up than Wwise for projects with a single adaptive track. Licensing savings can reach $5–15k per year.
| Criterion | FMOD | Wwise |
|---|---|---|
| License | Free up to $200k | Free up to $150k (Indie) |
| Setup complexity | Lower | Higher |
| Adaptive music | Timeline + Parameters | Music Container (more flexible) |
| Profiler | Built into Studio | Separate Wwise Profiler |
| Documentation | Good | Excellent |
For small teams without a dedicated technical audio designer, FMOD Studio is easier to maintain.
What's Included in FMOD Integration?
- Project analysis — audit of current audio system and sound requirements.
- Design — creating event architecture, parameters, and banks.
- Integration — plugin installation, output configuration, connecting events to gameplay.
- Adaptive music — implementing Intensity principle with parameters and Transition Regions.
- Testing — verification on target devices, memory and latency measurements.
- Optimization — voice limit tuning, streaming, priorities.
- Documentation and training — handover of materials and team consultation.
Timeline
3–5 business days for basic system integration: plugin installation, bank setup, SFX and UI events, one adaptive music track with a parameter. Cost is calculated individually after a project audit. To stay within budget and get integration advice, contact us — we'll choose the best integration plan for your game. Request a project audit — we'll estimate the scope and propose a solution.