# FMOD\_ERR\_NOTREADY
**URL:** https://qa.fmod.com/t/fmod-err-notready/12347
**Category:** Unreal Engine
**Created:** [March 3, 2016, 8:03pm UTC](https://qa.fmod.com/t/fmod-err-notready/12347 "2016-03-03T20:03:51Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@pwkmikekelly](https://qa.fmod.com/u/pwkmikekelly)
#### Post date: [March 3, 2016, 8:03pm UTC](https://qa.fmod.com/t/fmod-err-notready/12347/1 "2016-03-03T20:03:51Z")
In our Unreal 4.10.4 game on standalone PC, StudioSystem[EFMODSystemContext::Runtime]-\>update() in FFMODStudioModule::Tick will suddenly start returning FMOD\_ERR\_NOTREADY every frame. If the game is exited at that point, it will crash in FFMODStudioModule::DestroyStudioSystem. It looks like FMOD is corrupted at that point, although hard to tell for sure from a third party minidump. Everything seems fine up until it starts failing. Any ideas where to look for clues?
---
### Author:  [@geoff](https://qa.fmod.com/u/geoff)
#### Post date: [March 4, 2016, 3:47am UTC](https://qa.fmod.com/t/fmod-err-notready/12347/2 "2016-03-04T03:47:53Z")
You can enable trace logging in FMODStudioModule by changing the debug initialization to the following:
```
FMOD::Debug_Initialize(FMOD_DEBUG_LEVEL_WARNING | FMOD_DEBUG_TYPE_TRACE, FMOD_DEBUG_MODE_CALLBACK, FMODLogCallback);
```
It should then print a callstack out of the error that causes the FMOD\_ERR\_NOTREADY result. That will help track down what is going on.
---
### Author:  [@pwkmikekelly](https://qa.fmod.com/u/pwkmikekelly)
#### Post date: [March 10, 2016, 9:43pm UTC](https://qa.fmod.com/t/fmod-err-notready/12347/3 "2016-03-10T21:43:20Z")
> [@](#):
>
> You can enable trace logging in FMODStudioModule by changing the debug initialization to the following:
>
> ```
> FMOD::Debug_Initialize(FMOD_DEBUG_LEVEL_WARNING | FMOD_DEBUG_TYPE_TRACE, FMOD_DEBUG_MODE_CALLBACK, FMODLogCallback);
>
> ```
>
> It should then print a callstack out of the error that causes the FMOD\_ERR\_NOTREADY result. That will help track down what is going on.
Adding FMOD\_DEBUG\_TYPE\_TRACE doesn’t produce any more output. I can change the log level in Unreal, but then I get too much all the time.
I added a check/assert on the result from update(). I haven’t been able to repro this running out of the debugger, but I had it happen while running a packaged build. I connected the debugger to it, and it looked like the FFMODStudioModule object itself was corrupt - almost null.
---
### Author:  [@geoff](https://qa.fmod.com/u/geoff)
#### Post date: [March 11, 2016, 2:33am UTC](https://qa.fmod.com/t/fmod-err-notready/12347/4 "2016-03-11T02:33:35Z")
To get the trace results coming through unreal, try editing FMODLogCallback and adding an extra case statement just before the verbose logging, to turn FMOD\_RESULT messages into warnings:
```
// new code start
else if (strstr(message, "FMOD_RESULT"))
{
UE_LOG(LogFMOD, Warning, TEXT("%s(%d) - %s"), UTF8_TO_TCHAR(file), line, UTF8_TO_TCHAR(message));
}
// new code end
else
{
UE_LOG(LogFMOD, Verbose, TEXT("%s(%d) - %s"), UTF8_TO_TCHAR(file), line, UTF8_TO_TCHAR(message));
}
```
---
### Author:  [@pwkmikekelly](https://qa.fmod.com/u/pwkmikekelly)
#### Post date: [March 12, 2016, 3:58am UTC](https://qa.fmod.com/t/fmod-err-notready/12347/5 "2016-03-12T03:58:20Z")
I did that, and I’m getting a lot of:
LogFMOD:Warning: c:\jk\workspace\Build\_\_1.7\_\_UE4Libs\_Win\lowlevel\_api\src\fmod\_dsp.cpp(490) – FMOD\_RESULT = 31 – An invalid parameter was passed to this function.
Should I be concerned?
I’m not seeing a call stack.
---
### Author:  [@pwkmikekelly](https://qa.fmod.com/u/pwkmikekelly)
#### Post date: [March 12, 2016, 11:05pm UTC](https://qa.fmod.com/t/fmod-err-notready/12347/6 "2016-03-12T23:05:08Z")
I changed FMODLogCallback to log warnings only for FMOD\_RESULT = 46, and reproduced it again on my machine, running out of a packaged build. Here are the logs:
[2016.03.12-22.57.42:195][171]LogFMOD:Warning: c:\jk\workspace\Build\_\_1.7\_\_UE4Libs\_Win\lowlevel\_api\src\fmod\_sound.cpp(137) - FMOD\_RESULT = 46 – Operation could not be performed because specified sound/DSP connection is not ready.
[2016.03.12-22.57.42:195][171]LogFMOD:Warning: c:\jk\workspace\Build\_\_1.7\_\_UE4Libs\_Win\studio\_api\src\fmod\_playback\_resource.cpp(144) - FMOD\_RESULT = 46 – Operation could not be performed because specified sound/DSP connection is not ready.
[2016.03.12-22.57.42:195][171]LogFMOD:Warning: c:\jk\workspace\Build\_\_1.7\_\_UE4Libs\_Win\studio\_api\src\fmod\_playback\_instrument.cpp(1158) - FMOD\_RESULT = 46 – Operation could not be performed because specified sound/DSP connection is not ready.
[2016.03.12-22.57.42:195][171]LogFMOD:Warning: c:\jk\workspace\Build\_\_1.7\_\_UE4Libs\_Win\studio\_api\src\fmod\_playback\_instrument.cpp(548) - FMOD\_RESULT = 46 – Operation could not be performed because specified sound/DSP connection is not ready.
[2016.03.12-22.57.42:195][171]LogFMOD:Warning: c:\jk\workspace\Build\_\_1.7\_\_UE4Libs\_Win\studio\_api\src\fmod\_playback\_instrument.cpp(179) - FMOD\_RESULT = 46 – Operation could not be performed because specified sound/DSP connection is not ready.
[2016.03.12-22.57.42:195][171]LogFMOD:Warning: c:\jk\workspace\Build\_\_1.7\_\_UE4Libs\_Win\studio\_api\src\fmod\_playback\_instrument.cpp(2928) - FMOD\_RESULT = 46 – Operation could not be performed because specified sound/DSP connection is not ready.
[2016.03.12-22.57.42:195][171]LogFMOD:Warning: c:\jk\workspace\Build\_\_1.7\_\_UE4Libs\_Win\studio\_api\src\fmod\_playback\_instrument.cpp(2918) - FMOD\_RESULT = 46 – Operation could not be performed because specified sound/DSP connection is not ready.
[2016.03.12-22.57.42:195][171]LogFMOD:Warning: c:\jk\workspace\Build\_\_1.7\_\_UE4Libs\_Win\studio\_api\src\fmod\_playback\_event.cpp(1352) - FMOD\_RESULT = 46 – Operation could not be performed because specified sound/DSP connection is not ready.
[2016.03.12-22.57.42:195][171]LogFMOD:Warning: c:\jk\workspace\Build\_\_1.7\_\_UE4Libs\_Win\studio\_api\src\fmod\_playback\_event.cpp(1288) - FMOD\_RESULT = 46 – Operation could not be performed because specified sound/DSP connection is not ready.
[2016.03.12-22.57.42:195][171]LogFMOD:Warning: c:\jk\workspace\Build\_\_1.7\_\_UE4Libs\_Win\studio\_api\src\fmod\_playback\_event.cpp(1225) - FMOD\_RESULT = 46 – Operation could not be performed because specified sound/DSP connection is not ready.
[2016.03.12-22.57.42:195][171]LogFMOD:Warning: c:\jk\workspace\Build\_\_1.7\_\_UE4Libs\_Win\studio\_api\src\fmod\_playback\_timeline.cpp(1918) - FMOD\_RESULT = 46 – Operation could not be performed because specified sound/DSP connection is not ready.
[2016.03.12-22.57.42:195][171]LogFMOD:Warning: c:\jk\workspace\Build\_\_1.7\_\_UE4Libs\_Win\studio\_api\src\fmod\_playback\_timeline.cpp(1932) - FMOD\_RESULT = 46 – Operation could not be performed because specified sound/DSP connection is not ready.
[2016.03.12-22.57.42:195][171]LogFMOD:Warning: c:\jk\workspace\Build\_\_1.7\_\_UE4Libs\_Win\studio\_api\src\fmod\_playback\_timeline.cpp(1708) - FMOD\_RESULT = 46 – Operation could not be performed because specified sound/DSP connection is not ready.
[2016.03.12-22.57.42:195][171]LogFMOD:Warning: c:\jk\workspace\Build\_\_1.7\_\_UE4Libs\_Win\studio\_api\src\fmod\_playback\_timeline.cpp(112) - FMOD\_RESULT = 46 – Operation could not be performed because specified sound/DSP connection is not ready.
[2016.03.12-22.57.42:195][171]LogFMOD:Warning: c:\jk\workspace\Build\_\_1.7\_\_UE4Libs\_Win\studio\_api\src\fmod\_playback\_event.cpp(401) - FMOD\_RESULT = 46 – Operation could not be performed because specified sound/DSP connection is not ready.
[2016.03.12-22.57.42:195][171]LogFMOD:Warning: c:\jk\workspace\Build\_\_1.7\_\_UE4Libs\_Win\studio\_api\src\fmod\_playback\_system.cpp(151) - FMOD\_RESULT = 46 – Operation could not be performed because specified sound/DSP connection is not ready.
[2016.03.12-22.57.42:195][171]LogFMOD:Warning: c:\jk\workspace\Build\_\_1.7\_\_UE4Libs\_Win\studio\_api\src\fmod\_playback\_system.cpp(1059) - FMOD\_RESULT = 46 – Operation could not be performed because specified sound/DSP connection is not ready.
[2016.03.12-22.57.42:195][171]LogFMOD:Warning: c:\jk\workspace\Build\_\_1.7\_\_UE4Libs\_Win\studio\_api\src\fmod\_runtime\_manager.cpp(235) - FMOD\_RESULT = 46 – Operation could not be performed because specified sound/DSP connection is not ready.
[2016.03.12-22.57.42:195][171]LogFMOD:Warning: c:\jk\workspace\Build\_\_1.7\_\_UE4Libs\_Win\studio\_api\src\fmod\_asyncmanager.cpp(688) - FMOD\_RESULT = 46 – Operation could not be performed because specified sound/DSP connection is not ready.
[2016.03.12-22.57.42:195][171]LogFMOD:Warning: c:\jk\workspace\Build\_\_1.7\_\_UE4Libs\_Win\studio\_api\src\fmod\_asyncmanager.cpp(718) - FMOD\_RESULT = 46 – Operation could not be performed because specified sound/DSP connection is not ready.
[2016.03.12-22.57.42:195][171]LogFMOD:Warning: c:\jk\workspace\Build\_\_1.7\_\_UE4Libs\_Win\studio\_api\src\fmod\_asyncmanager.cpp(731) - FMOD\_RESULT = 46 – Operation could not be performed because specified sound/DSP connection is not ready.
[2016.03.12-22.57.42:214][171]LogFMOD:Warning: c:\jk\workspace\Build\_\_1.7\_\_UE4Libs\_Win\studio\_api\src\fmod\_asyncmanager.cpp(182) - FMOD\_RESULT = 46 – Operation could not be performed because specified sound/DSP connection is not ready.
[2016.03.12-22.57.42:214][171]LogFMOD:Warning: c:\jk\workspace\Build\_\_1.7\_\_UE4Libs\_Win\studio\_api\src\fmod\_studio\_impl.cpp(1295) - FMOD\_RESULT = 46 – Operation could not be performed because specified sound/DSP connection is not ready.
[2016.03.12-22.57.42:214][171]LogFMOD:Warning: c:\jk\workspace\Build\_\_1.7\_\_UE4Libs\_Win\studio\_api\src\fmod\_studio\_impl.cpp(3915) - FMOD\_RESULT = 46 – Operation could not be performed because specified sound/DSP connection is not ready.
[2016.03.12-22.57.42:224][171]LogFMOD:Error: ‘StudioSystem[EFMODSystemContext::Runtime]-\>update()’ returned ‘Operation could not be performed because specified sound/DSP connection is not ready.’
---
### Author:  [@geoff](https://qa.fmod.com/u/geoff)
#### Post date: [March 15, 2016, 12:21am UTC](https://qa.fmod.com/t/fmod-err-notready/12347/7 "2016-03-15T00:21:07Z")
Thanks for the log. This looks like Studio is calling some query functions on streaming sounds that potentially can return not ready. I’ll let you know when a fix is available.