Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.37f1
2021.3.7f1
2022.1.10f1
2022.2.0b2
2023.1.0a4
2023.2.0a1
Issue ID
UUM-9852
Regression
No
Toggling the "Spatialize" flag on and off on a playing audio source causes a loud burst of distorted audio
How to reproduce:
1. Open the attached “OnAudioFilterReadTest_2020-3-37” project
2. Open the “SampleScene”
3. Select the “SimpleRepro” GameObject in the Hierarchy
4. Disable the “Change Spatialize” flag in the Inspector under the Audio Test (Script) settings
5. Enter Play mode
6. Toggle the “Spatialize” flag in the Inspector under the Audio Source settings on and off repeatedly
7. Observe the audio
Expected result: The audio switches normally between its spatialized and non-spatialized versions
Actual result: Occasionally, a very loud burst of audio can be heard
Reproducible with: 2020.3.37f1, 2021.3.7f1, 2022.1.10f1, 2022.2.0b2, 2023.1.0a4
Reproducible on: Windows 10
Note: The loud burst sound is the same sound that occurs if "Change Spatialization" is enabled and the “Spatialize” flag is clicked repeatedly
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
- The Scrollbar becomes unusable when adding Elements to the List
- "One or more data file missing for baking set NewScene Baking Set. Cannot load shared data." error in Player when a specific project is built
- Choosing new HDR Colour using RGB values breaks colour on Intensity Selectors
- Rendering/Decal Layer Mask options are different inside Prefab Mode and outside Prefab Mode when the project is upgraded to Unity 6
- Incorrect Realtime GI Light Probes baking when more than one Light Probe Group is used and "Baked Global Illumination" is enabled
Resolution Note:
A workaround has been provided by the customer that reported this issue. While we've identified the root cause of this issue, the solution requires a substantial rewrite of the audio C++ code base. We're planning to do a proper refactor of the parts of the code that are causing this issue, but unfortunately we're unable to provide a quick fix at this point.