jcm93 / jmc

jmc - a new macOS media organizer
Other
497 stars 21 forks source link

jmc activating microphone? #11

Open colin-marshall opened 7 years ago

colin-marshall commented 7 years ago

I have an app (Oversight) that tells me when another app uses my webcam or microphone. Whenever I load jmc and start playing a song on beta 3 I get notified that my mic is being used?

jcm93 commented 7 years ago

jmc doesn't do anything microphone-related at all. There is some code in AudioModule.swift which touches some low-level audio stuff to detect when the system audio output device changes, but I'm not sure why that would cause a program like Oversight to think the microphone is being used.

colin-marshall commented 7 years ago

Well I would suggest looking further into it because it might scare some people away from your software. I have never seen another app do this that wasn't actually using the microphone. I'm sure you're right and it's just a false positive, but it's the first I've ever seen.

https://objective-see.com/products/oversight.html

jcm93 commented 7 years ago

Hmm. I removed the listener block I mentioned but the alert is still triggered for some reason. The rest of the audio pipeline is super simple; it's just an AVAudioPlayerNode hooked up to the system output node through a mixer and an EQ. My money's on this being a bug on Oversight's end that has to do with AVAudioEngine.

I'll leave this open in case I revisit it later.

colin-marshall commented 7 years ago

I emailed the Oversight people in regards to this. I'll let you know what they say.

anderscarling commented 6 years ago

@colin-marshall did you ever get a response from Oversight?

colin-marshall commented 6 years ago

@anderscarling unfortunately I did not.

anderscarling commented 6 years ago

Started to look into it and it definitely is comnected to the use of AVAudioEngine. Basically, commenting out all of the init code in AudioModule stops the warning.

I didn’t have time to find out any details though, maybe I’ll give it another go and see if there is anything we could change that would fix warning without breaking jmc :)