Search Issue Tracker
By Design
Votes
0
Found in
2018.1.2f1
Issue ID
1043869
Regression
No
Large numbers of Audio Mixer Groups cause a performance hit even when not connected to an Audio Source
Steps to reproduce:
1. Open attached project "Unity_Audio_Mixer_Issue.zip"
2. Make sure Window>Audio Mixer is open
3. Enter Play Mode
4. Check PostLateUpdate.UpdateAudio for the numbers
Expected result: disconnected Audio Mixer should not affect performance in Editor
Actual result: project performance while running in Editor takes a hit
Reproduced with: 2017.1.1f1, 2017.4.5f1, 2018.1.2f1, 2018.2.0b8, 2018.3.0a1
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
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
- Hidden Tabs do not shift into empty space after closing visible Tabs
- [Android] Application not deployed on a device when "activity-alias" is used in the AndroidManifest
- Shader compile process adds shader ID to the constant buffer name when the word "Globals" is being used in Vulkan
- Audio Mixer Snapshot link to the documentation isn’t working
Resolution Note:
What is referred to as "mixers" in the repro case is actually channel strips. This slows down everything, even painting the mixer UI is super-slow. A more realistic project would split up the channel strips between multiple sub-mixers (for ambience, dialogue, music etc). In this case, there is code that makes sure only the mixers with actual active sources allocate CPU time. After a period of inactivity, these will enter suspended mode to save CPU.