I need to maintain two different versions of FMOD banks for a certain period of time to release packages, but I don’t want to maintain two different versions of FMOD projects at the same time.
I hope to be able to use an old version of the project, and when a new version bank needs to be created, I can use the command line to have fmod studio automatically open the old version project and upgrade to the new version, and then build the bank. But now it seems that upgrading the FMOD project requires opening the graphical interface and manually clicking “continue”. Is there a way to automate this step?
Or can I use FMOD script to upgrade the old XML?
As of the time of writing (September of 2025), there is no way to migrate an FMOD Studio project using the command line tool, and FMOD Studio scripting does not support updating FMOD Studio projects’ xml files.
Is it actually necessary that you maintain two different versions of the FMOD Studio project? The FMOD Engine is backwards-compatible with banks built in earlier versions of FMOD Studio, so you can (for example) use FMOD Engine version 2.03.09 to load a .bank file built in FMOD Studio version 1.03.00. If you’re not making use of new features introduced in FMOD Studio versions later than the one your project was created in, you could potentially just build the banks in that version, and use the same .bank files in both versions of your game.
We are upgrading FMOD version and bank version.
We hope to only allow a certain number of players to use new version of FMOD to verify stability. We will fully apply it only after verification is completed. So I hope only these players are using the bank generated by the new version.
Thanks for the information. Unfortunately, I suspect I’m misunderstanding something: If your goal is to provide the new bank version to only a subset of players, and then to later roll out that bank version to all players, why is it necessary to automate migration of the project? It seems like you could just migrate it once, build the banks, and then provide those banks to your players without having to migrate the project again subsequently.
Sorry for the misunderstanding. Our game requires weekly updates (hot updates), which usually involve some audio updates. This update must also be released simultaneously to the current official version and the test version. If the bank cannot be automatically updated, the sound effects team must export two different versions of the bank every week. Due to the long testing time, we want to minimize labor costs as much as possible.
Anyway, if we really can’t automatically update the bank, we’ll have to handle it manually. Thank you for your help.