# FMOD\_SPEAKER\_MAX' failed error

**URL:** <https://qa.fmod.com/t/fmod-speaker-max-failed-error/23032>\
**Category:** Unity\
**Tags:** unity\
**Created:** [June 11, 2025, 9:59am UTC](https://qa.fmod.com/t/fmod-speaker-max-failed-error/23032 "2025-06-11T09:59:38Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Leah\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/leah_fmod/32/3685_2.png) [@Leah\_FMOD](https://qa.fmod.com/u/Leah_FMOD)\
**Post date:** [June 16, 2025, 12:34am UTC](https://qa.fmod.com/t/fmod-speaker-max-failed-error/23032/5 "2025-06-16T00:34:33Z")

</div>

Thanks for the log - I can confirm that the assert is happening erroneously, and has been scheduled for a fix.

The assert itself is benign in this case, and should only happen in non-release builds where [debugging is enabled](https://www.fmod.com/docs/2.02/api/core-api-common.html#debug_initialize), but if you’d like to strip the assert out of your Unity logs entirely, you can modify `RuntimeManager.DEBUG_CALLBACK()` to check for the assert message in the `FMOD.DEBUG_FLAGS.ERROR` so it can be ignored.

See this post for an example of how to do so, in this case with a `WARNING` instead of an `ERROR`: [Adding signal DSP causes starvation - #7 by Leah\_FMOD](https://qa.fmod.com/t/adding-signal-dsp-causes-starvation/22011/7)

---

_[View the full topic](https://qa.fmod.com/t/fmod-speaker-max-failed-error/23032)._