Kap: "Select input device" shows a list of undefined or no input devices

[tlystad24]

Platform: macOS 10.13.2
Kap Version: 2.0.0 (2.0.0.681)

Steps to reproduce

Preferences > Advanced > Record Audio - select input device

Current behaviour

Displays a list of "undefined"

Expected behaviour

Should list available input sources

Kapture

[skllcrn]

Are you able to recreate this on the latest version (2.1.2) @tlystad24?

[tlystad24]

I'm no longer seeing the issue on the latest version

[skllcrn]

Thanks for opening #490 @harryfear, could you please see if you're able to replicate using this build: http://kap-artifacts.now.sh/next

[harryfear]

Hi! Sexy new look. Sadly, with this version I get "No input devices", though.

FYI, these are the input devices on the system:

Could this be related to Oversight or Micro Snitch?

[skllcrn]

Can you try disabling only Oversight, only Micro Snitch and then disabling both to nail down if they might be the cause @harryfear? If you're running both, that is. I see that OverSight lets you whitelist applications, so if you're using that you should add Kap to the list.

[harryfear]

Just killed all processes related to Oversight and Micro Snitch (one by one) and neither have made any difference (reloaded Kap each time).

Not sure if either load Kexts though that might be blocking Kap's access.

[skllcrn]

Did you try whitelisting Kap?

[harryfear]

There's no option to whitelist Kap in Oversight because it seems Oversight doesn't even detect Kap trying to access any input.

[skllcrn]

Okay, I'm pretty sure this is an issue with other software you're using. Do you have other Electron apps that use your microphone that you could test, like Skype?

[harryfear]

I understand. I opened up Skype and this happened…

This doesn't happen with Kap.

[skllcrn]

Interesting, thanks for testing. I suggest reporting this to OverSight and we'll see if there's anything we can do on our end.

[sindresorhus]

@tlystad24 Would you be able to try out the latest beta and see if you still can reproduce this issue?

[tlystad24]

@sindresorhus I've not had the issue since since I closed this issue on May 26. I've also tried the latest beta and I have no issue selecting input devices.

[sindresorhus]

Great. Thanks for the update :)

[mmcev106]

I'm seeing "No input devices" in v3.0.0-beta4. The only sound device related app I have installed is Boom, but whether or not it is enabled or it's devices are selected doesn't seem to make a difference. Is there anything I can do to help troubleshoot to pinpoint the cause of this?

[skllcrn]

Which audio devices appears in your system settings @mmcev106? Would also be great if you could test with Boom disabled/uninstalled. I'm guessing you might have virtual audio devices that the app isn't playing nice with.

[mmcev106]

I've uninstalled Boom to make sure it's out of the equation. The only devices I have listed now under System Preferences -> Sound -> Input/Output are "Internal Microphone" and "Internal Speakers". I am still only seeing "No input devices". Is there anything else I can check/test?

[skllcrn]

Damn. Hmm, apps like that often come with a kernel extension. Can you remember having used a kernel extension on your system @mmcev106? Also, to be extra sure: Uninstall Kap, Boom and any kernel extensions, then restart your system before reinstalling Kap. You should also check that there aren't any leftovers in ~/Library/Application Support after uninstalling.

[mmcev106]

Assuming the following command is correct, here are the kernel extensions I have installed:

markbook:~ markmcever$ kextstat | grep -v com.apple
Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>
  154    0 0xffffff7f83548000 0x29000    0x29000    org.pqrs.driver.Karabiner (10.22.0) 75A195F3-FC81-39D0-9040-64D3880249EE <43 5 4 3 1>
  155    0 0xffffff7f83571000 0x1f000    0x1f000    com.intel.kext.intelhaxm (7.2.0) 0E6123B5-EF61-3050-95F1-9BC68008D888 <7 5 4 3 1>
  158    3 0xffffff7f83590000 0x64000    0x64000    org.virtualbox.kext.VBoxDrv (5.2.16) 8F6F825C-9920-39E4-AF20-6DD4F233D4F1 <7 5 4 3 1>
  164    0 0xffffff7f835f4000 0x8000     0x8000     org.virtualbox.kext.VBoxUSB (5.2.16) 1731469A-4A2D-32D4-8F03-4D138AAE1FE9 <163 158 56 7 5 4 3 1>
  165    0 0xffffff7f835fc000 0x5000     0x5000     org.virtualbox.kext.VBoxNetFlt (5.2.16) 59F71856-C064-3B98-A8AD-B2C33164FBC2 <158 7 5 4 3 1>
  166    0 0xffffff7f83601000 0x6000     0x6000     org.virtualbox.kext.VBoxNetAdp (5.2.16) 24514714-1702-3FF6-90F8-8F3E79B4D8A4 <158 5 4 1>
  167    0 0xffffff7f83607000 0x8000     0x8000     foo.tun (1.0) FBA9A61D-E7BB-391C-92E2-C1D85BB065B2 <7 5 4 1>
  168    0 0xffffff7f8360f000 0x7000     0x7000     foo.tap (1.0) FF769517-6401-3F61-9190-B967BF20C0B2 <7 5 4 1>
markbook:~ markmcever$ 

I rebooted after uninstalling Boom, removed Kap's app support dir, and temporarily unloaded the above extensions:

markbook:~ markmcever$ rm -rf ~/Library/Application\ Support/Kap\ Beta/
markbook:~ markmcever$ kextstat | grep -v com.apple
Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>
markbook:~ markmcever$ 

It unfortunately didn't make a difference... If you still think uninstalling the extensions will make a difference, I will, I just wanted to make sure before I went to the trouble. Thanks for the feedback so far regardless.

[skllcrn]

Thank you for taking the time @mmcev106, re-opening the issue so we can take a closer look at this.

[skllcrn]

Linking issues relating to audio and input devices: #489

[IssueHuntBot]

@issuehunt has funded $80.00 to this issue.

---

• Submit pull request via IssueHunt to receive this reward.
• Want to contribute? Chip in to this issue via IssueHunt.
• Checkout the IssueHunt Issue Explorer to see more funded issues.
• Need help from developers? Add your repository on IssueHunt to raise funds.

[skllcrn]

Closing this as we have not had additional reports of the issue, however don't hesitate to open a new issue – thank you!