FMOD returns error code 36 (FMOD_ERR_INVALID_HANDLE) executing setRelativeAudibility

Unity Engine
,
1

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.

4 Likes
2

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

3

up +1

4

up +1

still happening on WebGL
Version 2022.2.3f1

5

up + 1

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

6

up +1

still happening on WebGL
Version 2022.2.4f1

7

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

8

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

9

Have anyone made bug report about this?

10

up

11

same here

12

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…

1 Like
13

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

14

Hi everyone,

I find no report on the public issue tracker or in our internal backlog. I’m really sorry about this. :sweat_smile:

Some of you seem to say that it’s more of an inconvenience but @elit says it’s leaking memory which is a serious concern. Please you submit a bug report, the most helpful thing you can do is to provide a sample project highlight a reproduction of the issue.

Thank you all for your help!

edit: typo

15

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

16

Hi @Laur3nt1u ,

Strangely I cannot find it on the public (or internal) issue tracker… Maybe it is still processing or something went wrong during the submission. Did you receive a url to track you issue that you could share?

Thanks!

17

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

1 Like
18

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. :frowning:

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

19

It seems like there is an issue according to this reply . The bug report as been created, and we’ll eventually get to it! The WebGL platform audio support is the most interesting challenge we have in my opinion. Can’t wait to see how it will evolve :wink:

1 Like
20

I also created bug report for it. IN-32364

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

1 Like