You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi all. This is more of an "is this normal behavior" question, so apologies if it's the wrong forum...
I'm getting very frequent OverSight notifications that the internal mic in my MacBook Pro is becoming active, attributed to the Zoom process. I'm also seeing the (macOS feature) orange dot pulse, just before the notification. Perhaps this is normal, but I didn't get such frequent notifications on Catalina (I updated to Ventura fairly recently) - I only used to get one notification when Zoom first activated the mic (and the deactivation one, when the call ended, etc.). I'll be sitting there on a zoom call, muted, with notifications popping up every ten seconds or so.
I could add Zoom to the allow list, I know, but I want to get notifications (just not constantly).
Are others experiencing this, please?
Editing to add version - I'm on Oversight v2.1.5
The text was updated successfully, but these errors were encountered:
Hi all. This is more of an "is this normal behavior" question, so apologies if it's the wrong forum...
I'm getting very frequent OverSight notifications that the internal mic in my MacBook Pro is becoming active, attributed to the Zoom process. I'm also seeing the (macOS feature) orange dot pulse, just before the notification. Perhaps this is normal, but I didn't get such frequent notifications on Catalina (I updated to Ventura fairly recently) - I only used to get one notification when Zoom first activated the mic (and the deactivation one, when the call ended, etc.). I'll be sitting there on a zoom call, muted, with notifications popping up every ten seconds or so.
I could add Zoom to the allow list, I know, but I want to get notifications (just not constantly).
Are others experiencing this, please?
Editing to add version - I'm on Oversight v2.1.5
The text was updated successfully, but these errors were encountered: