MuteMe
High Processor Usage
Check the process and the circumstances first, then reduce unnecessary microphone polling and send a useful report if the problem continues.
Identify the process
Check CPU use in Windows Task Manager or the CPU view of macOS Activity Monitor. Note whether the busy process is MuteMe, a meeting app or a system audio process. Compare the same setup while idle and during a private test call.
After leaving the call, quit MuteMe from its tray or menu-bar menu and observe whether the usage changes. Closing the app window may only minimize it. Reopen MuteMe after the comparison.
Review microphone polling
Open Microphone Settings
Expand the microphone entries you control. The options Sync MuteMe with mute status changes to this microphone and Revert mute status changes to this microphone periodically check state and use additional resources.
Change only the options you do not need
Temporarily turn off unnecessary Syncing or Reverting behavior, leaving Control this microphone with MuteMe enabled for the input you use. Test one change at a time and restore any behavior you rely on.
Capture a repeatable example
Use the current MuteMe app and record the app/OS versions, microphone model, meeting app, process name and whether the issue occurs while idle or in a call. Send a report using the app’s log-reporting steps.
The original page discussed a problem in MuteMe 0.5.1 and earlier. Its experimental beta, audio-service reset and system-folder commands are not current troubleshooting steps.
We’re here to help
Still need a hand?
The best way to contact us is through the Support tab in the MuteMe app. Include your device, operating system, app version and what you have already tried.