[MAC] CoreAudio and SonarworksASPProxy high CPU (on macOS 10.14 & 10.15)

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:

 

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. 

 

151466.png

 

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.

  1. Uninstall the current version fully: [MAC] How to uninstall SoundID Reference?
  2. 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.

Was this article helpful?

7 out of 10 found this helpful

Have more questions? Submit a request

34 comments

0

Hi,

Has any progress been made on this bug or is there a release date for the patch ?

I haven't been able to use the “virtual monitoring” version i bought for several months now because of this CPU  bug on my Imac.

Thank you

0

Hi paridem and paul.fairall - sorry to hear about this! Please try reverting to the 5.6.1 version as per the steps mentioned in the guide, this version should work without this specific issue present. I will also open up support requests on your behalves, so we can help you with reverting successfully. 

0

Same problem here. Still waiting for a fix! Mac OS 10.15.7 on Macbook pro 16" 2019 intel i9

0

Phew lads….Mac mini, OS 10.15.7 logic pro. Long time user. Tried every work around, and still insane CPU usage. Six month in and it's hard not to feel that we've been abandoned on this one. Oy !

Please sign in to leave a comment.