Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2022.1.X
Votes
0
Found in
2021.2.0a13
2021.2.1f1
2022.1
Issue ID
1379745
Regression
Yes
Only one 'Compressed in memory' AudioClip is playable in WebGL Player
How to reproduce:
1. Open the user’s attached “AudioBug_.zip” project
2. Open the “SampleScene” Scene
3. Switch to WebGL platform
4. Build And Run
5. In the WebGL Player press “A”, “S”, “D” buttons on the keyboard
Expected result: 3 different Audio Clips are played
Actual result: Only the first Audio Clip played can be played
Reproducible with: 2021.2.0a13, 2021.2.6f1, 2022.1.0b2
Not reproducible with: 2019.4.33f1, 2020.3.24f1, 2021.2.0a12
Notes:
- The expected result can be observed in the Play Mode
- This issue is not reproducible if Audio Clip in the Import Settings has Load Type as “Decompress On Load”
- Tested on Mac
Comments (1)
-
Scott-Elson
Feb 03, 2022 15:51
At least in 2021.2.9 and .10 using "Compressed in Memory" is a problem as well. This happened sometime after 2021.1.12. If you play a sound that lasts for a few seconds the next time you try to play a different sound the previous sound will play instead, even if you're in a completely different scene and all the audiosource and audioclips are gone. There were other issues as well related to trying to stop sounds which also went away when changing the compression.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Getting a deprecated package for JetBrains Rider pop up when opening or creating a project
- [Android] Volume level of the same audio file is different on Samsung Galaxy Tab A8 between 2023.3.0b3 and 2023.3.0b4
- ‘Expected end of value’ warning occurs when a property declaration includes five or more variable references
- Crash on BurstCompilerService::CompileAsync when entering Play mode in a specific scene
- InvalidOperationException when using Game Camera Preview in Scene window with a custom RenderGraph pass
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a4
Resolution Note (fix version 2022.1):
Fixed in version 2022.1.9f1