This applies only if you’re using Unity: After my experience yesterday I would recommend thinking twice about updating to the newest legacy version unless you absolutely have to. Doing so in my project completely broke everything half way through my day yesterday, I spent the next 9 or 10 hours trying to repair things, and at the end of it I no longer could even use sound because the new FMOD version failed to initialize the system with Unity unless the debug define was in place. So it was not even usable for me. It could have been my fault somehow, but after many hours I could not find or figure out a way of fixing it.
Instead what I’m doing today is trying to switch over to the Integration 2.0 (v1.08). I’ve made a new project just to tinker and learn, and so far it looks like a substantial improvement. You can drag and drop sounds into the scene and it’s all just much more cleanly integrated with Unity. Looks impressive, really, a lot of the FMOD studio stuff is built in to Unity now which I was not even hoping for. I had a hiccup with FMOD Studio, but FMOD staff answered it quickly and was plenty helpful.
It might be too early to tell but at this point the new integration looks really good. So I’m going to try switching my other project (now broken) over to this today and see how it goes. It may be less painful to just switch yours over to Integration 2.0 than it is to try and use the latest legacy system. There’s a built in migrator script in it that supposedly can handle some of the transfer, and the docs for migrating look plenty comprehensive and easy to follow. Something to think about anyway.
If you go with legacy first, definitely back up your project completely before you try it. Running that Unity package naively just obliterated me, and attempting to recover through an SVN backup was not successful.