Incorrectly firing off event for bluetooth headset microphone

[aejay-query]

When an application engages the microphone on my headsets (both are Shokz headsets; one is the Aeropex, and the other is the newer Open Run), OverSight fires the "off" event for the microphone. It then fires "off" again once the mic is disengaged.

Switching my input to the built-in mic, I get the events I expect.

I'm very new to the mac world; I tried to look through the source to try to find the source of the issue, but I'm out of my depth. My best guess, though, is that OverSight doesn't like something about how these headsets operate. They show up as a single device in Mac's sound settings, but it actually has two operating modes behind the scenes, and the device acts as kind of a wrapper for two virtual devices:

• Headphones / output-only
• Headset / input and output

I wonder if, by asking for the ID of the device... maybe this utility is getting an ID that corresponds to the headphones device, rather than the headset one? Just a stab in the dark.

I'm happy to help troubleshoot anyway I can, but I might need some guidance on how to be helpful in that regard.

Some system info:

MacOS: Ventura 13.4.1
OverSight: 2.1.6