The balance in both the FMOD Studio sound-/music-designer app and the accompanying API is well-judged in terms of simplicity versus complexity. Really simple sound and music design takes no time at all, and a simple runtime sound engine based on the API is similarly simple to code up. Complex sound events, 3D positioning (with customizable roll-off behaviors), and sophisticated interactive music tracks can be designed and auditioned in the app. Admittedly this requires a little more technical knowledge but there's no need for knowledge of C++ programming to achieve this. The app can also connect to a live running game to tweak behaviors in response to the actual live game data, which is invaluable. More complex sound engines using the API are highly customizable too. The API is simple to use and the support forum is very active, and frequented by the actual Firelight Technology engineers (rather than representative to merely triage issues). They are very responsive, in my experience, and they are clearly keen to make FMOD the best it can be. Finally, having used the FMOD Studio app since its very early release, I was impressed with the engineering process (from an external view point) where the initial app was super basic yet developed over time. There is a strong sense that their internal processes for their roadmap prioritization and QA is working well (presumably involving extensive automated tests given the very few regressions I have experienced). Features were added as the FMOD Studio app and API version incremented and these are usually backwards compatible.

The upsides are countless. I don’t know what I was doing before using FMOD.

FMOD is a very powerful tool that let's you implement audio into videogames faster than other middleware software. I has a graphic interface that makes it very easy to tune different elements of an asset. Tuning loops and adaptive music is also very easy with FMOD.