Bringing ODIN Voice Chat to FMOD: A Complete Toolkit for Studio and Runtime

Bringing ODIN Voice Chat to FMOD: A Complete Toolkit for Studio and Runtime#

Voice chat is a must-have for modern multiplayer games—but integrating it into FMOD? That’s like trying to fit a square peg in a round hole. Real-time peer audio isn’t your average baked asset. You can’t import a sound file, preview an event in the editor, or even find a clear spot for your audio team to tweak it like the rest of your mix. Until now.

With the release of our FMOD Studio Plugin, ODIN’s FMOD toolkit is now feature-complete across both the design-time and runtime sides of the pipeline. This post walks through every component, who it’s for, and when to reach for it.

TL;DR Why use ODIN Voice?#

You’re using FMOD. You want to add voice chat. Most voice SDKs treat audio output as a black box and push you back to Unity’s or Unreal’s built-in audio engine — undoing the pipeline your team has built around FMOD. ODIN is different:

• Voice chat lives inside FMOD. On both Unreal and Unity, peer audio routes through FMOD — so your mix bus structure, effects, attenuation, and spatialization apply to each single voice the same way they apply to every other sound in the game.
• Your audio team mixes voice in FMOD Studio. Our new Studio Plugin lets sound designers join a live ODIN room and tune the mix in the tool they already know — before a single line of game code is touched.
• Built for real-time games. Low-latency, managed voice service with SDKs for every major engine and platform.
• Open-source integration code. Every FMOD integration is published on GitHub — fork it, extend it, or ship it as-is.

The Toolkit at a Glance#

1. FMOD Studio Plugin (New)#

The newest addition to our toolkit, the ODIN FMOD Studio Plugin is a DSP-based plugin that connects FMOD Studio directly to ODIN rooms.

Why this matters for audio engineers: until now, the only way to hear what voice chat sounds like through your project’s FMOD mix was to run the game. With the Studio Plugin, you can join a live ODIN room from inside FMOD Studio, route peer audio through your event’s signal chain, and apply the same DSP, mixing, and spatialization you would for any other sound source.

How it works:

1. Drop the ODIN Playback Plugin into an FMOD event’s signal chain.
2. Enable Persistent on the event.
3. In the Deck, enter your Access Key, Room Id, and an optional User Id.
4. Hit Connect, then Play — remote peers are mixed live into the event output.

Cross-platform testing: pair it with the 4Players Web App to join the same room from a browser and validate your mix against real input, without needing a build.

Studio-only by design. This plugin is intended for design-time work. Do not ship it in console, mobile, or web runtime builds — keep Studio-only event variants so your runtime banks don’t depend on the Studio DSP. For runtime, use the engine-specific integrations below.

2. FMOD Adapter Plugin (Unreal)#

The FMOD Adapter Plugin for Unreal is the fastest path to voice chat in an Unreal project that already uses FMOD. Under the hood it uses the same DSP Plugin and Programmer Sound techniques covered in the integration guide below — packaged as a ready-to-use plugin so your team doesn’t have to build them from scratch.

The plugin ships two key parts:

• UOdinFmodAdapterComponent — a drop-in replacement for the default UOdinSynthComponent. It routes peer audio from ODIN Voice through FMOD instead of built-in audio engine.
• UFmodOdinSubsystem — starts ODIN with FMOD’s configured sample rate automatically.

For audio engineers: the FMOD Event is defined in FMOD Studio with any effects, sends, and 3D attenuation your project needs. The Unreal side just plays it. Your audio team owns the sonic behavior of voice chat the same way they own everything else in the mix.

For developers: drop the component on a Player Character, call Play Odin Voice from your OnMediaAdded event handler, and you’re done. No custom DSP code to maintain.

This is the recommended path for most Unreal teams.

3. FMOD Integration Guide (Unreal)#

If you need full control over the DSP path — custom mixing logic, per-peer channel groups, specialized spatialization — the FMOD Integration Guide for Unreal walks through building a UOdinFmodAdapter from scratch using the same two techniques the Adapter Plugin is built on:

• DSP Plugin (recommended): writes ODIN audio directly to the master channel group via a custom DSP. Low latency, full control over the signal flow.
• Programmer Sound (alternative): uses FMOD’s Programmer Sound API. Easier to wire up, but adds roughly 500ms of latency — generally not acceptable for live voice.

The accompanying sample project is a working reference implementation, including the UOdinFmodAdapter source, a Pan DSP for spatialization, and attenuation parameters exposed to Blueprints.

Reach for this option when the Adapter Plugin’s behavior doesn’t match your needs and you’d rather fork the implementation than work around it.

4. FMOD Integration Guide (Unity)#

The FMOD Integration Guide for Unity shows how to wire ODIN into a Unity project that uses FMOD — whether alongside Unity’s built-in audio or as the sole audio engine.

The centerpiece is FMODMicrophoneReader, a drop-in replacement for ODIN’s default MicrophoneReader:

• Captures microphone audio through FMOD’s recordStart API in PCMFLOAT format.
• Reads the recording buffer continuously and pushes the data to the ODIN servers.
• Handles sample rate and channel count matching between FMOD’s recording device and ODIN’s media streams.

Paired with FMODPlaybackComponent for output, this gives Unity teams a complete capture-and-playback path through FMOD.

Heads up: the Unity playback path is based on FMOD Programmer Sounds and adds roughly 500ms of latency. If lower latency is critical, the FMOD Studio Plugin above is a great place to prototype your mix while we expand the runtime options.

Which One Should You Use?#

A quick decision tree:

• Audio engineer prototyping the mix? → FMOD Studio Plugin.
• Unreal team shipping production voice chat? → FMOD Adapter Plugin (Unreal).
• Unreal team that needs custom DSP behavior? → FMOD Integration Guide (Unreal), forked from the sample project.
• Unity team using FMOD for audio? → FMOD Integration Guide (Unity).

These are not mutually exclusive. Your audio team can iterate inside the Studio Plugin while your engineers integrate the runtime plugin in parallel — both connect to the same ODIN rooms with the same access key, so the mix your audio engineer signs off on in FMOD Studio is the mix that ships.

Getting Started#

• FMOD Studio Plugin → docs.4players.io/voice/fmod/fmod-studio-plugin
• FMOD Adapter Plugin (Unreal) → docs.4players.io/voice/unreal/guides/odin-fmod-adapter-unreal
• FMOD Integration Guide (Unreal) → docs.4players.io/voice/unreal/guides/odin-fmod-unreal
• FMOD Integration Guide (Unity) → docs.4players.io/voice/unity/guides/odin-fmod

Using another audio engine or sound tool?#

Checkout our Wwise integration guide and Wwise adapter plugin for using ODIN with Wwise in Unreal or our atmoky guide with sample project for using ODIN with atmoky trueSpatial in Unity.

These docs should give you a hint to integrate ODIN into any other audio engine or 3rd party sound tool. Feel free to ask us about special development support for your custom integration!

Questions, feedback, or feature requests? Join us on Discord — we’d love to hear how you’re integrating voice into your project.