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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
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.