Hello,
I’m experiencing a blocking issue here. Fmod is freezing after opening the mixer window. It happens only in one project. Yesterday it was unfreezing after several minutes, but today it’s completely stuck.
Thank you.
Details:
Version: 2.03.06 but I already tried to open it with 2.03.07 and the issue persists
Already tried to save the project as and open the duplicated one.
Already tried to switch audio interface and from Wasapi to Audio.
In the logs, two errors appear: 2025-06-10 09:34:27 “FMOD_ERROR (27): Cannot call this command after System::init.” ----------------- ! 2025-06-10 09:34:27 “FMOD_ERROR C:\buildagent1\work\c1c3f17eb167c494\studio\src\SoundSystem.cpp(131): system->setSoftwareFormat(deviceInfo.sampleRate, speakerMode, 0)”
Thank you for sharing the detailed information and log file.
Unfortunately, I was not able to reproduce the freeze on my end, would it be possible to upload the project or a minimal reproduction to your FMOD profiler so I can take a closer look?
Also, FMOD Studio 2.03.09 is now available on our website’s download page. This version includes fixes for some Qt-related UI hangs. Could you please try updating to 2.03.09 and let us know if the issue persists?
Hello! Sorry for the slow reply but I was out for work. I’ve just uploaded a rar archive of the entire project, called RosesFMODProject.rar, in my profile area.
Thank you
I’m sorry to say that I was still unable to reproduce the issue with the project you provided. I opened it using both 2.03.06 and 2.03.07, and the mixer window opened and closed as expected on my end.
I also tested it at different resolutions and with Live Update enabled. Everything appears to function correctly, both when connected to Unity and when not.
Would it be possible to share a set of reproduction steps to ensure I’m not missing anything or doing something differently?
Additionally, in FMOD Studio, could you try navigating to File > Validate Project to see if that resolves the freezing issue?
I’m experiencing the same on a project I’m working on. Was this ever resolved?
I’ve updated to a new FMOD Studio version to see if that fixed the issue but it didn’t. From 2.03.07 to 2.03.11.
Thank you
* Update: I deleted a Parameter I just created and it solved the issue. I’ll need to work on these parameters at some point in the near future, will it work correctly when all ranges have been set?