Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

jmc activating microphone? #11

Open
colin-marshall opened this issue Aug 10, 2017 · 7 comments
Open

jmc activating microphone? #11

colin-marshall opened this issue Aug 10, 2017 · 7 comments

Comments

@colin-marshall
Copy link

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
Copy link
Owner

jcm93 commented Aug 15, 2017

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.

@jcm93 jcm93 closed this as completed Aug 15, 2017
@colin-marshall
Copy link
Author

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
Copy link
Owner

jcm93 commented Aug 15, 2017

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.

@jcm93 jcm93 reopened this Aug 15, 2017
@colin-marshall
Copy link
Author

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

@anderscarling
Copy link

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

@colin-marshall
Copy link
Author

@anderscarling unfortunately I did not.

@anderscarling
Copy link

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 :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants