Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.4.X, 2020.1.X
Votes
0
Found in
2017.4
2018.4
2018.4.16f1
2019.2
2019.3
2020.1
Issue ID
1213824
Regression
No
Disabling and enabling an AudioSource component controlled by a Timeline causes a pop and ignores the mixer settings
How to reproduce:
1. Open user-submitted project (769080-AudioSourcePop)
2. Enter Play Mode
3. Select the 'AudioTest' GameObject and disable the 'Audio Source' Component
4. Note the sound pop that briefly occurs
5. Enable the 'Audio Source' Component again
Expected result: disabling the AudioSource does not cause sound pops. Enabling the AudioSource component keeps the assigned Mixer settings(muted)
Actual result: disabling the AudioSource causes sound pops. Enabling the AudioSource component ignores the assigned Mixer settings(audio is not muted like at the start)
Reproducible with: 2017.4.36f1, 2018.4.16f1, 2019.2.19f1, 2019.3.0f6, 2020.1.0a20
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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0b1
Resolution Note (fix version 2020.1):
Fixed in 2020.1.9f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.12f1
Resolution Note (fix version 2018.4):
Fixed in 2018.4.29f1