If you notice a high CPU utilization while using the SoundID Reference standalone app on your macOS 10.14 Mojave or 10.15 Catalina device, this guide details the issue and provides a workaround for affected users.
In this article:
- CoreAudio and SonarworksASPProxy cause a high CPU
- Fix not planned
- Support discontinuation for macOS 10.14 and 10.15
- Solutions
Known issue: Fix not planned
Issue reported: Jul 6, 2023
Article updated: Mar 27, 2024
CoreAudio and SonarworksASPProxy cause a high CPU
With the release of SoundID Reference version 5.7.3, some users of macOS 10.14 Mojave and 10.15 Catalina with specific CPU chipsets might experience high CPU issues while SoundID Reference is running. This can be observed by opening the Activity Monitor utility and checking the CPU readings for these two processes:
- coreaudiod ~100% CPU
- SonarworksASPProxy ~30% CPU
In some cases, it might cause a significant and noticeable CPU overload, resulting in computer fans blowing at full power, playback glitching (especially video content via Safari or other browsers), or the computer freezing up.
Fix not planned
We recognize the challenges some of our users have faced with the SoundID Reference app on macOS 10.14 Mojave and 10.15 Catalina, particularly those with specific CPU chipsets, following the release of our updated standalone app HAL driver in version 5.7.3 (September 2023). After thorough investigation and consideration, we must share that a resolution to this issue cannot be achieved within the current framework of the new standalone app driver.
This decision comes in light of the dynamic evolution of macOS system architecture, which necessitates continuous updates to SoundID Reference to harness the capabilities of newer operating systems, incorporate the latest features, and enhance overall performance. Given these constraints, maintaining backward compatibility for macOS 10.14 and 10.15 has become unfeasible within our latest Release versions.
Support discontinuation for macOS 10.14 and 10.15
With the 5.10.0.54 update, SoundID Reference will no longer support macOS 10.14 Mojave and 10.15 Catalina. Consequently, we will not be pursuing a fix for the CPU issue. We understand the impact of this decision and are committed to assisting our users through this transition. Below, we outline several options available to those affected by this change.
All users that have reported this issue will be reached out to and solutions will be provided as per the below options and within warranty terms, or alternative solutions.
Solutions
Update to macOS 11 Big Sur
Updating to macOS 11 Big Sur or higher, as the issue is not present on newer operating systems. If this is not an option on your Mac, we recommend the following solutions for different scenarios:
Revert to an earlier version
If updating the operating system is not possible it's recommended to revert back to the last version before the new driver release: version 5.7.2.
- Uninstall the current version fully: [MAC] How to uninstall SoundID Reference?
- Download and install version 5.7.2.8 here: SoundID Reference 5.7.2.8.pkg
Note: Follow the linked uninstall instructions carefully, make sure to remove all remaining files and components, and back up your speaker profiles before uninstalling.
34 comments
would love an update on this issue. does the november update address this at all?
I reverted to 5.7.2.7 and it's fine working again.
prior to revert I was getting +100% CPU from sonarworksASP and/or coreaudio driver, even after forcequitting them multiple times/restarting computer. latency was atrocious and audio would frequently stop working altogether until a restart. even disabling sonarworks from autoloading with startup didn't solve it, CPU usage would just spike right back up. it was a headache until I found this thread.
I'm running Catalina 10.15.5 and can't update my OS any futher. (stable hackintosh reasons) I hope Catalina will continue to be supported
I wish that known issues for "compatible" OS's would be published clearly with the update notifications, or even in an email.
d_hydrate Sorry to hear that! If you are encountering a "Preset Switch Failed" error, please see our guide for some workaround suggestions here: "Preset switch failed" error message
The 5.7.3.17 update includes a major macOS driver rework which aims to resolve this error as well. This error may appear if you've reverted, but trying out the suggestions the guide linked hopefully will help get rid of it.
Just in case, you can submit a ticket to our support team here: Submit a request
Beta doesn't work either. Keeps saying "Preset switch failed". Then it gives an option to contact support, but the page doesn't exist.