Hi there, I’ve received reports from our QA department regarding a log from FMOD spamming the logs. Attempting to schedule a sound in the past, we’re already loading the banks sample data, but we’re still getting these logs every now and then.
However, we have a bunch of sounds being played making it rather impossible to figure out which sound is actually causing the spam. Would it be possible to include information about which sound is being scheduled so we can investigate where the issue is coming from? I do have a profiler recording which I’ve tried to use to figure out where the log is coming from, but seeing as the log is coming from the fmod debug callback inside of Unity, it’s rather difficult to properly match this with the log.
We’re currently using version 2.02.24 but we’re planning on upgrading to the latest version of 2.03 soon ish. Probably once Unity 6 is officially released.