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, the CPU view of macOS Activity Monitor, or your Linux system 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.

Using Dictation in 0.29.6?

Local Whisper can use CPU or supported GPU resources while loading its model, checking setup performance, generating a live draft or transcribing your finished recording. Compare usage during those tasks with usage after processing finishes. Built-in Windows or macOS dictation uses the operating system’s own recognition processes.

A loaded Whisper model can retain several hundred MB of RAM, plus GPU memory where applicable, between sessions. Keeping it ready does not keep the microphone recording or continuously transcribe audio.

  1. Separate processing from idle memory.

    Open MuteMe+ → Not in Meeting Actions → Dictation and note the processing mode and model status. A loaded model in memory is different from sustained CPU use when no recording or transcription is running.

  2. Adjust the settings you need.

    Turn off Live preview to reduce draft processing, or choose a shorter Unload model after duration to release idle memory sooner. Turning off local dictation or quitting MuteMe unloads the model without deleting its downloaded file. The next use may need time to load it again.

See the 0.29.6 Dictation settings guide. If CPU use stays high after processing ends, include the chosen engine, model status and whether a live draft or final transcription was active in your support report.

Review microphone polling

  1. 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.

  2. 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.

Reference links