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.
How to Choose a Camera Approach on Mobile Platforms?
Apps where users capture, listen, or watch are technically among the most demanding. We deal with this every day. Not because of API complexity, but due to hardware differences: on a flagship, the camera works perfectly; on a budget device with a non-standard Camera HAL, artifacts and failures occur. On iOS, stabilization differs between generations. Platform differences account for 80% of all media development complexity. Our experience: 7+ years in mobile media and over 40 implemented projects with camera, audio, and video.
What are the Differences Between CameraX, Camera2, and AVFoundation?
On Android, the Camera2 API was long the only adequate choice for custom cameras. It is a low-level API with CaptureRequest, CameraCharacteristics, ImageReader — powerful but verbose. Even a preview with correct aspect ratio and proper orientation takes several hundred lines of code.
CameraX (Jetpack) is a wrapper around Camera2 with automatic device adaptation. Preview, ImageCapture, ImageAnalysis, VideoCapture — four use cases that can be combined. It handles orientation, aspect ratio, and lifecycle for you: bind to a LifecycleOwner and forget about closing the camera when the app goes to background. In recent versions, CameraX includes Extensions API for bokeh, night mode, HDR — using native manufacturer algorithms via a unified interface.
When is Camera2 needed directly?: RAW capture via ImageFormat.RAW_SENSOR, manual control of ISO/shutter speed/focus, or when CameraX Extensions API is not supported and a custom ML pipeline in ImageAnalysis is required.
On iOS, AVFoundation is the only path for a custom camera. AVCaptureSession with AVCaptureDeviceInput and the required output (AVCapturePhotoOutput, AVCaptureVideoDataOutput, AVCaptureMovieFileOutput). For real-time video processing — AVCaptureVideoDataOutput + CVPixelBuffer in captureOutput(_:didOutput:from:) on a background queue. This is where CoreML models receive frames for inference.
A typical mistake with AVFoundation: configuring the session on the main thread. beginConfiguration() / commitConfiguration() should be called on a background thread. Otherwise, the preview freezes, and the user sees a frozen UI. This mistake appears in 70% of the projects we have audited.
Why is AudioFocus Critical for Android Apps?
Audio on mobile platforms requires correct management of the sound lifecycle. AudioFocus is a coordination mechanism between apps. AudioManager.requestAudioFocus() with OnAudioFocusChangeListener. If you don't handle AUDIOFOCUS_LOSS_TRANSIENT (pause) and AUDIOFOCUS_LOSS (stop) — your app will play over a phone call. That guarantees a bad review on Google Play. Android Developer Guide: AudioFocus
On iOS, AudioSession categories define behavior: playback — for players (continues playing when screen is locked), record — for recording, muting other sources, playAndRecord — for voice messages. Wrong category — the app mutes the user's background music on start.
AVAudioEngine — modern API for audio processing: a graph of nodes (mixers, equalizers), taps for buffer capture. For real-time speech — SFSpeechRecognizer + inputNode.installTap.
On Android for recording with noise suppression — NoiseSuppressor.isAvailable() + create(audioRecord.audioSessionId). Works not on all devices, need a fallback.
Video: Playback and Streaming
ExoPlayer (Media3) — standard for Android. Supports HLS, DASH, SmoothStreaming, progressive playback. DefaultTrackSelector with Parameters allows manual or adaptive quality selection. DRM via DefaultDrmSessionManager with Widevine L1/L3.
Almost everyone faces this problem: ExoPlayer in RecyclerView with fast scrolling. Need a PlayerPool — a pool of reusable players. Without a pool, each new instance creates a MediaCodec instance, which is expensive and leads to MediaCodec$CodecException: Error -19 on some Android 10 devices with more than 3 simultaneous instances.
AVPlayer / AVPlayerViewController on iOS — for playback. For custom UI — AVPlayerLayer + custom controls. HLS works natively via AVPlayer(url:) with m3u8. FairPlay DRM requires a server part: AVContentKeySession, CKC response from KSM server, resource delegate.
For Flutter — video_player as a base layer, chewie for UI. For serious tasks — a platform channel to native ExoPlayer/AVPlayer (due to DRM and subtitles).
| Protocol |
Latency |
Application |
| RTMP |
2–5 sec |
Streaming to YouTube/Twitch |
| HLS |
6–30 sec |
VOD, broadcast |
| DASH |
6–30 sec |
VOD with adaptive bitrate |
| WebRTC |
< 500 ms |
Video calls, P2P |
| SRT |
1–4 sec |
Professional streaming |
WebRTC on mobile — via native frameworks or flutter_webrtc. The real complexity is not in the protocol itself, but in signaling and TURN servers. Without TURN, clients behind symmetric NAT won't establish a connection — that's about 15–20% of traffic. Coturn is the standard open-source server.
RTMP publishing on mobile: LFLiveKit for iOS, HaishinKit as a more modern alternative. On Android — rtmp-rtsp-stream-client-java or via FFmpeg with JNI. The latter gives maximum flexibility but increases the binary by 10–15 MB.
Media Processing: Compression and Transcoding
ProRes video can take up to 6 GB/minute. Compression is needed before upload. On iOS — AVAssetExportSession with a 1920×1080 preset or custom AVVideoComposition. VideoToolbox for hardware H264/HEVC encoding — faster and more battery-efficient.
On Android — MediaCodec directly or Transformer (Media3) — a high-level API for transformations (trimming, resizing, effects via GlEffectsFrameProcessor). For images — BitmapFactory.Options.inSampleSize for downsampling, Glide / Coil for caching. Coil on Coroutines fits well with Compose. Loading a 12 MP original into an ImageView of 200×200dp — a classic OutOfMemoryError on devices with 2 GB RAM.
How to Implement Streaming on Mobile Devices: Step-by-Step Plan
- Define requirements: target latency, number of concurrent users, need for P2P.
- Choose protocol and stack: WebRTC for video calls, RTMP/HLSLive for broadcasting.
- Set up signaling (SIP, WebSocket, MQTT) and TURN server.
- Implement publishing/viewing via native API or cross-platform plugin.
- Test on real devices with different cameras and network conditions.
- Optimize bitrate and resolution based on bandwidth.
Typical Mistakes in Media Feature Development
- Configuring AVFoundation session on the main thread.
- Missing AudioFocus Loss handling on Android.
- Ignoring
MediaCodec limitations on cheap devices.
- Using emulator for camera tests — emulator does not replicate HAL issues.
- Memory leaks when recreating media players without a pool.
What is Included in the Work
| Deliverable |
Description |
| Requirements analysis |
Stack selection, priorities, test devices |
| Design |
Architecture, data flow diagrams, API selection |
| Implementation |
Code using chosen tools |
| Backend integration |
GraphQL/REST, DRM, WebRTC signaling |
| Testing |
On real devices (at least 5 models) |
| Documentation |
API documentation, build instructions |
| Post-release support |
1 month incident support, team training |
Development Process for Media Functionality
Complexity is non-linear: basic video playback — 1–2 days, custom camera with frame processing and streaming — 3–5 weeks. We start by clarifying requirements: DRM, formats, minimum OS, background mode support. Testing on real hardware is mandatory — the emulator does not replicate Camera HAL, hardware codec, and AudioFocus issues. Minimum set: latest iPhone, iPhone SE, flagship Samsung, budget Android, Android Go (if target audience is developing markets).
Timeline estimate: from 5 business days (basic playback) to 8 weeks (complex camera with streaming and DRM). Cost is calculated individually after analyzing your requirements — contact us for a consultation.
Our service: "Mobile Media Integration" — this is our expertise. Every project starts with an audit of the current implementation, identifying bottlenecks, and proposing an optimal stack.
Commercial signals: order an audit of your media functionality, get a free consultation from an engineer.
