Hi, I’m experiencing a few critical bugs with the new version update (FMOD Studio 2.03.07).
The software crashes frequently. I haven’t found a way to replicate it, as it seems to happen randomly—whether I’m importing new files, editing a loop region, dragging an instrument, profiling, etc.
Every time I try to expand the left boundary of a trimmed audio region, it drags the clip’s content to the left instead
Live Update has slowed down significantly. It takes much longer to sync, even if the banks are up to date. Sometimes it gets stuck and doesn’t update at all, preventing me from hearing and testing changes in real time. Other times, it simply freezes, forcing me to quit FMOD Studio via the Task Manager
The profiler “Waveform” mode doesn’t seem to work anymore—I can’t listen back to what I recorded during the profiling session
I know this one was marked as fixed in the last update, but the loudness meter reset button still doesn’t work
Thank you for bringing these issues to our attention.
Are you seeing the crash reporter popping up when experiencing the crash? Any information you can provide in the reporter helps us diagnose the issues.
Would it be possible to elaborate on this issue? Is it moving the whole instrument?
Is this happening every time you are connecting or only the first time? How large is the FMOD Studio project? When it is freezing, are you seeing it as (Not Responding) in task manager?
Unfortunately, I was not able to reproduce this issue. Would it be possible to package the profiler session and upload it to your profile with the following settings?
I usually tend to write what I was doing when the software crashed in the reporter to help diagnose the problem. As I said, it occurred numerous times while importing new files (I bounce the assets from Pro Tools directly into the FMOD asset folder and then “import” them manually, since they are flagged as “unimported”). It also happened a couple of times while editing a loop’s transition timeline during playback, while dragging an instrument during playback, and during various profiling and live update sessions.
I’ll make sure to be more detailed in the next reports, should the crashes occur again.
As you can see in this video, if I try and expand the trimmed clip’s left boundary, it will drag the whole instrument’s content to the left, leaving a blank space on the right; if I do the same thing on the right boundary though, it’ll behave as intended.
One project is 24+GB, while the other is 28+GB.
It usually happens after the first time, however. Sometimes, when I make real-time adjustments on FMOD, both the build and the Unity editor won’t reflect those changes, even though the banks are up to date. So I try to disconnect and reconnect again and it gets stuck syncing forever.
The task manager looks as in the attached screenshot below. I tried to reproduce the bug now but FMOD didn’t freeze and let me reopen the project after quitting it due to a failed live update connection.
I need to first send a request to connect to an existing project in my company; otherwise, it won’t let me upload any content. I’ll do this as soon as I can.
Just a follow-up to confirm that I’ve tried to reproduce the profiler’s “waveform” mode bug this morning, but it seemed to work just fine. In fact, it didn’t even make FMOD crash during live update and went pretty smoothly to be fair.
Should it happen again in the future, I’ll package the project and upload it to my profile as you requested.
However, the live update bug still persists. After connecting FMOD the first time, I disconnected and tried to reconnect it again. At that point, it failed and got stuck syncing. So, I quit FMOD but it remained active as a background process in task manager.
Here’s a screenshot of the “Details” tab in task manager
The start of the audio file will always be to the left of the instrument, when an instrument is extended past the length its audio file it will either be represented as the empty space or the looping audio file if looping is enabled FMOD Studio | Working with Instruments - The Content Graphics of Synchronous Instruments. If you enable looping on the instrument
Thank you for the information regarding the Live Update bug, I will investigate this further. In the mean time, could you please test disabling the following setting in the File -> Preferences
By disabling this, the initial connection should be much faster, but it won’t automatically update anything that was modified while it was disconnected.
Good to hear you are no longer experiencing this issue, if it does come up again please do not hesitate to let me know.
Hey Connor, I see that but I am pointing out a different issue here. I must not have explained myself well so I’ll try to be clearer now.
If I drag the left handle of the audio region to the left, I’d expect FMOD to reveal the audio content that comes before the left handle. Instead, FMOD reveals the content that comes after the right handle.
Dragging the right handle, however, behaves as expected and reveals content after the right handle of the region.
To sum it up:
Expanding the left handle reveals content after the right handle (incorrect; it should reveal content before the left handle)
Expanding the right handle reveals content after the right handle (correct in this case).
This behavior changed in the latest FMOD update. Previous versions worked correctly.
I hope this video helps clarify the issue further. As you can see, I first split the audio file in two, then attempt to expand the left handle to “restore” the trimmed portion on the left. What happens, however, is that the audio clip expands on the right side, revealing content after the right handle.
