One component can fail while the rest of the system looks healthy. Here, macOS shows microphone activity while the selected meeting app sends no voice. Treat the unaffected path as a control for diagnosis.
Define a reproducible test
Primary symptom. macOS shows microphone activity while the selected meeting app sends no voice. Record the precise point of failure and whether the same input, account or connected device succeeds in another supported mode. That working comparison establishes the scope of the repair.
Likely technical explanations
The first hypothesis is a mismatch in the failing path. Compare the selected input device in macOS Sound and the call app using a local meter. The second is a lower-level state that the interface may not show: check aggregate devices, external interface sample rates and exclusive capture conflicts. A third possibility is a feature or version limitation, which should be checked against supported documentation before a reset.
For this macOS issue, capture macOS version, privacy entitlement, connected hardware and power state and compare the same feature with a second supported user/device configuration. Preserve the last known working configuration so you can tell whether a successful retry came from an actual correction or a temporary recovery.
Test outcomes and next actions
| What you observe | What it suggests | Focused response |
|---|---|---|
| macOS shows microphone activity while the selected meeting app sends no voice | The failure affects the specific workflow described here; the entire system is not necessarily broken. | Compare the selected input device in macOS Sound and the call app using a local meter. |
| The basic comparison exposes a difference between a working and failing configuration. | A local setting, version, account context or device route deserves attention. | Choose the actual microphone and confirm app microphone permission and input gain. |
| The same failure persists after a reversible correction. | A deeper dependency or compatibility issue may remain. | Check aggregate devices, external interface sample rates and exclusive capture conflicts. |
Before changing anything: Never record or share other participants' audio without consent. Save a screenshot or anonymized log line, record the previous setting, and back up relevant user data. Do not reset every related service just because one test fails.
Choose a recovery route. The Beginner path checks compare the selected input device in macOS Sound and the call app using a local meter. The Advanced path investigates check aggregate devices, external interface sample rates and exclusive capture conflicts. They address different evidence; use the path that matches your result.
Step-by-Step Troubleshooting
Choose the Beginner route for reversible checks or Advanced for evidence-driven diagnosis.
Preserve the current working state
macOS shows microphone activity while the selected meeting app sends no voice. Before editing settings, note the exact time, affected account or device, and whether it started after an update, move, hardware change or network change. This is the baseline for the Mac Microphone Indicator Is On but Video Calls Record Silence guide.
Check the selected input device in macOS Sound and the call app
Compare the selected input device in macOS Sound and the call app using a local meter. Observe whether the symptom changes. A clean comparison tells you which part of the process is healthy and avoids unnecessary resets.
Adjust the actual microphone and confirm app microphone
Choose the actual microphone and confirm app microphone permission and input gain. Change only this variable, record its former value, and try the failing action once. If there is no improvement, restore the prior configuration before exploring the Advanced route.
Verify a consenting remote participant hears clear audio through
A consenting remote participant hears clear audio through the intended input. Repeat using the same account, network, file, title or hardware condition that previously failed. Do not count a different test as confirmation.
Correlate the failure evidence
Collect the error text or state relevant to Mac Microphone Indicator Is On but Video Calls Record Silence. Record macOS version, privacy entitlement, connected hardware and power state; anonymize account IDs, public IPs and secret-bearing log fragments before sharing.
Inspect aggregate devices, external interface sample rates and
Check aggregate devices, external interface sample rates and exclusive capture conflicts. Record the difference between successful and failed cases and keep the first meaningful error rather than the last cascade message.
Compare a controlled second condition
Where practical, compare the same feature with a second supported user/device configuration. If the alternate case works, return to the single configuration difference instead of changing multiple services. Use the vendor-supported method for your current version.
Document the regression test
A consenting remote participant hears clear audio through the intended input. Leave the previous value documented for rollback, then monitor one normal operating cycle. If symptoms recur, attach the sanitized evidence to a vendor or administrator support request.
Understand the comparison
After the first corrective action, interpret the result carefully. If the original task now works, leave the other settings unchanged. If it still fails, check aggregate devices, external interface sample rates and exclusive capture conflicts. Compare the same feature with a second supported user/device configuration rather than adding random fixes on top of one another.
For escalation, retain macOS version, privacy entitlement, connected hardware and power state, the original output, and a single before/after comparison. Redact passwords, tokens and personal data. A support agent can then distinguish the same feature with a second supported user/device configuration from a general outage without repeating risky actions.
Verification without guesswork
Pass condition: A consenting remote participant hears clear audio through the intended input. The validation must exercise the same path that failed originally. A successful settings screen, single ping, application homepage or idle system is not enough if the original failure appears during a different action.
Repeat the test under the original conditions once after a safe relaunch, reconnect or new session. For intermittent failures, record the time and the difference between a clean result and a failed one instead of claiming success from a single attempt.
If the first attempt fails
If the problem persists, restore any test-only settings, preserve the evidence and stop before destructive reset, firmware flash or credential recreation. Give official support the exact symptom, the first failing timestamp and what the comparison established. Never record or share other participants' audio without consent.
Prevent recurrence: Document the working correction: Choose the actual microphone and confirm app microphone permission and input gain. Retain the accepted result (a consenting remote participant hears clear audio through the intended input) as a future regression test after configuration, software or hardware changes.
Solution Checklist
Questions specific to this fault
How do I know the symptom is actually resolved?
A consenting remote participant hears clear audio through the intended input. A generic diagnostic test outside the affected workflow is not a substitute.
Should I reset or reinstall everything first?
No. Compare the selected input device in macOS Sound and the call app using a local meter. Then choose the smallest supported intervention: choose the actual microphone and confirm app microphone permission and input gain. Preserve recoverable settings and user data.
What should I include in a support request?
Provide the exact failing action, product and version, time, non-sensitive log evidence, and this deeper observation: Check aggregate devices, external interface sample rates and exclusive capture conflicts. Do not include credentials or private customer data.