Audio from Timeline is not playing in WebGL build

In my Timeline I have an Audio Track that I use to play a few wav files during a cutscene. When the cutscene plays in the editor or a standalone executable, everything works fine. When the cutscene plays on a WebGL build, there is no audio from the Timeline. Other game audio works fine in the WebGL build.

A few other sources on the internet mention that the audio asset’s Load Type must be set to Streaming, but this does not resolve the issue for me.

Here are the current settings for the audio file. I have also tried:

  • checking / unchecking Load In Background
  • Compression Format: Vorbis
  • Decompress on Load with and without Preload Audio Data

9757995--1397358--upload_2024-4-8_13-50-5.png

Is there anything else that I can try or check?

Here are some screenshots of the Timeline and the game object with the Playable Director component. The Audio Source I’m using in the Timeline is attached to the same game object as the Playable Director.

1 Like

Just because I know it feels awful when you ask for help and nobody answers ,

Timeline DOES work, without issues on all platforms.

You don’t say which version of unity you are using, so I think the problem is you are using a 2021 vesrion that had a bug in it.

Update it to the newer ones

additionally, the PCM tab is not the one webgl uses … it’s the last one, that is converted to mp3 anyway internally if they didn’t change it again

Sorry I forgot to include the Unity version. I am using 2021.3.11f1. If there is a bug in that version specifically then I’ll have to evaluate if it’ll be more work to add a workaround or to transition the project to a newer version.

Thanks for the reply.

Just to close the loop here, I updated my Unity version to 2022.3.25f1 and the audio from the Timeline work as expected now.

:wink:

This bug seems to be back in 2022.3.38f1. I submitted a bug report.

Or does it work for you in latest 2022.3 ?

1 Like

The bug is weirdly and not fully correctly described by Unity QA , but this is the public bug tracker link:

This bug seems to be back in 2022.3.33f1

1 Like

We also encounter this problem 2022.3.53f1