Bug FMOD returns error code 36 (FMOD_ERR_INVALID_HANDLE) executing setRelativeAudibility

Our project
WebGL
Unity 2022.1.23f1

Things were going well as we started adding audio to our project, but we recently started getting this error when we tried to call Play() on any AudioSource.

FMOD returns error code 36 (FMOD_ERR_INVALID_HANDLE) executing setRelativeAudibility

I have tried updating to Unity 2022.2.1f1, but i still get the error.
Funny thing, when I went back to 2021.3.16f1, I stopped having that issue and everything seems fine. Is there something different in 2022 that I need to account for when using Audio in WebGL? We are currently just using mp3 files.

 

Up, need help too. After 3 days of test i don't have solution. This add memory and crash app after many time

WebGL
Version 2022.2.2f1

 

up +1

 

up +1

still happening on WebGL
Version 2022.2.3f1

 

up + 1

Version 2022.2.1f1
Interestingly sometimes the bug calls, sometimes it doesn't in my case

 

up +1

still happening on WebGL
Version 2022.2.4f1

 

It happens on WebGL in 2022.2.5, 2022.2.6 and 2023.1.b3, the audio is fine it's working but I just get spammed with this error in build

The game works fine in 2021.1.28 but I wanted decals and rendering layers

EDIT: It happens when you play something after an audio source was destroyed or the scene was reloaded

 

I also get this error in versions 2022.2.5, 2022.2.6 . Tried a lot of things, but the problem remains

 

Have anyone made bug report about this?

 

up

 

same here

 

same. 2022.2.7f1 URP WebGL

In my case it always occurs on the second time played, and forever after. First time sound is called it plays as expected.

Perhaps someone from Unity's WebGL team can tell us the path to where in the codebase we can comment the offending line until there's an actual fix? I'm having a tough time locating it and would prefer not having to roll back again...

 

Same issue for us. Is there a bug report for this?

 

I've sent a bug report last week with a small project and instructions attached CASE IN-32105

 

I go this https://unity3d.atlassian.net/servicedesk/customer/portal/2/IN-32105

 

I tried to use the FMOD plugin to try to bypass the issue but I had no luck. It is too convoluted. I could not figure out how to use it without changing the audio listeners and the audio sources, and worst installing their Studio.

A temp way to comment out the error would be ideal since it does not seem to cause any issues otherwise.

 

I also created bug report for it. IN-32364

Thank you for your hard work WebGL 2.0 must be hard as it is ages old code and it does have too many limitations for Unity to shine.

 

The update I got

https://issuetracker.unity3d.com/is...e-scene-reload-or-an-audiosource-is-destroyed

 

H

Hang on, sorry, but that’s not even REMOTELY a valid response. It’s a regression, but the only solution is to upgrade to a current alpha? Am I reading that correctly and that there will be no fix for 2022.2? And what about 2022.3 (when it’ll be released)?

 

I agree with VOTRUBEC, this has to be fixed in 2022.2 as well.

 

Thank you and the team for digging around. It sounds like a fix should be possible, as I'd hate to have to backport the project to 2021 just because of this one issue. I'm sure there's a few people here that would appreciate any update and news when it comes to hand. I understand the commitment to the LTS release, and I'm also curious as to when 2022 will enter LTS. But for the time being, again, thank you for your efforts.

 

Please fix this issue in 2022.1/2, as it issues thousand of error messages per minute.

 

Has anyone tried 2022.2.10f1 by any chance?

 

Did the fix arrive in any 2022.1/2022.2 version?
2022.2 was unusable last time I checked, but I'd give it another try if it has the bugfix

 

Also having this message spammed after upgrading from 2021 to 2022. Currently running 2022.2.11. I'm not sure if it's having negative effects on the game or not, but the spammed error log surely doesn't help for tracking other bugs.

I def don't want to upgrade to 2023 since it's in alpha, so a real fix for 2022 would surely be nice.

 

Same bug in 2022.2.12f1. One of the solutions do not use Unity AudioSource and switch it to FMOD because looks like Unity used very old FMOD technology.

 

Thanks to you and your team for looking into this. Is there a bug report posted somewhere that we could track the progress on this? Will this one be updated with the new fix or is there another place to track: https://issuetracker.unity3d.com/is...e-scene-reload-or-an-audiosource-is-destroyed

Thanks again.

 

@SeventhString Thanks for the update that they're likely in progress. Would you be able to post an update when there is any news? I and I'm sure others are watching this thread.

 

In patch notes for 2022.2.13 it says this:

• WebGL: Fixed FMOD console errors when a scene is reloaded. (UUM-19241)

I'm assuming this may have been fixed in 2022 then. I'll have to test to see for sure.

 

@therobby3 Thank you so much for catching this! I upgraded to the new version and gave it a shot. Looks like the endless FMOD errors have ceased! And thank you @SeventhString for getting this on the dev's radar.

 

Unity 2022.2.13f1 still look like:

 

solve this problem using DontDestroyOnload on my audiosources

 

Hello,

How did you set this? In code?

Thanks,
crafTDev

 

Yes, I set this in script attached to game object with audio source.

https://docs.unity3d.com/ScriptReference/Object.DontDestroyOnLoad.html

Do not destroy the target Object when loading a new Scene, keep it in your mind

 

Problem come back

 

I am seeing this too is it fixed anywhere?

 

I've been stuck on 2021.1.28 every new version has a different audio problem not even 2021.3 LTS is good

 

the attitude towards a regression must be that it gets fixed. It can't be that a regression force version changes. This is irresponsible in the extreme. Users are stuck to big point versions for LOTS of reasons, almost all Unity caused, in that going up a year see dozens or even hundreds of other regressions.

In WebGL world, the iteration time is far faster for game makers, they're often running live games and using WebGL precisely because they can iterate over live game updates with far more ease than the submission processes of other platforms, etc.

It's interesting that you say this:

Are you perhaps aware of ways that you could eventually offer OnAudioFilterRead to WebGL users?

No platform is more fittingly suited to the kinds of optimisations possible with this feature of default Unity Audio, which works on ALL other platforms, just not WebGL, where it's most needed.

 

It might be best to think of WebGL as a unique platform, and not try to shoehorn everything into it, and even have a separate license for it, especially now that Project Tiny is a distant memory.

 

It's where a very large future lays, now that VR has finally played itself out and revealed itself to be a novelty for a long time to come.

In terms of ad games and dynamic, engaging experiences that are truly portable, nothing beats WebGL and Unity could and should have the ultimate foothold into it. I wish you all the best with convincing the management that WebGL is special... because it is. They don't seem to see how uniquely special it is, nor how they could build a pared down editor just to target it, and only it, as those working/aiming at WebGL aren't going to be expecting to easily port to other platforms, and vice versa.

WebGL is unlike all other platforms in that it's an end unto itself.

 

Just switched from 2021.3.25 to 2022.2.19 and will probably have to go back to 2021 because of this. Bizarre that they only fixed it in Alpha version.

 

Yea, not sure what's going on. I don't know if it was fixed in a version then came back, or what. But I'm still getting spammed with this error again in version 2022.2.19. Error is as follows:

./Modules/Audio/Public/AudioSource.cpp(1574) : Error executing dspHead->setRelativeAudibility(relativeAudibility) (An invalid object handle was used. )