Search Issue Tracker

Fixed in 2021.2.X

Fixed in 2020.3.X

Votes

7

Found in

2019.1.0a8

2019.4

2020.1

2020.2

2020.2.0a19

Issue ID

1270635

Regression

Yes

[WebGL] FMOD error spam in the console when playing an Audio Clip in a Timeline

WebGL

-

How to reproduce:
1. Open the user's attached "WebGLAudio2020-2.zip" project
2. Open the "SampleScene" Scene
3. Go to File -> Build Settings
4. Make sure Platform is set to WebGL
5. Press Build And Run
6. Inspect the console in the browser

Expected result: No error messages are spammed in the browser's console
Actual result: "FMOD returns error code 78 (FMOD_ERR_UNIMPLEMENTED) executing setMix" error message is getting spammed in the browser's console

Reproducible with: 2019.1.0a8, 2019.4.9f1, 2020.1.4f1, 2020.2.0a21
Not reproducible with: 2018.4.26f1, 2019.1.0a7

Note:
- In 2018.4.26f1 - 2019.1.0a7 the same message is getting spammed as info message, but not as an error message (which should be the correct behavior, since the console could be filtered and important error messages would be visible, while in 2019.4, 2020.1 and 2020.2 error messages are getting spammed and important error messages can be lost in all of that spam)

  1. Resolution Note (fix version 2021.2):

    Fixed in: 2021.2.0a7

  2. Resolution Note (fix version 2020.3):

    Fixed in: 2020.3.39f1

Log in to vote on this issue

Comments (16)

  1. 5argon

    Oct 15, 2021 02:21

    Still "Planned for 2020.3.X" after a year and more later.. This bug implies you cannot touch both Timeline and even manually managed Playable Graph in WebGL game if it has an audio node. That sounds like a very serious bug to me. All the cutscenes must be mute! Or having to time the audio separately using Timeline Marker that fires audioSource.PlayOneShot or something.

    (By the way, the audio sounds perfect like it works, just that there are error spam. If Unity take a a day or a week surely this could be fixed? Come on, please!!)

  2. VARtechLLC

    Sep 17, 2021 15:40

    Clearly Unity has no interest in resolving this error...

  3. naber78

    Apr 19, 2021 17:57

    When will it be fixed in 2020.x LTS?

  4. paulksi

    Apr 04, 2021 07:37

    Not fixed 2020.03

  5. MidniteOil

    Dec 13, 2020 20:19

    I am seeing this issue in version 2021.1.1.0a5.1029.

  6. JuanJSAR

    Sep 16, 2020 21:31

    this error is still from Unity version 2018.4.25f1

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues