josh-richardson/cadmus

[Feature Request] Denoised Microphone as selectable Input device

C-512L opened this issue · 11 comments

it have sense that you could just select the Denoised Microphone as an input device in apps like Discord, Skype, etc directly from their settings rather than having to do it manually from pulseaudio settings

I believe this limitation is due to applications like discord excluding virtual outputs from their list of available devices. I'm not sure that this is a problem that Cadmus can solve - however, I'll leave this issue open to see if anyone in the community has ideas.

at least for me, in pavucontrol it shows "Denoised Microphone" as a monitor instead of a virtual device input
image
image

You're right there. As far as I can see in my own testing, Discord only shows physical input devices. However I'll look into the possibility of getting it to show others.

image

So as far as we know... You cannot use this with discord?

@yurgburg You can, you just have to manually set Discord to "record" from the Denoised Microphone. Then it will properly capture.

@thebitstick how would I do that? It doesn't show denoised microphone

At least when testing with Discord's mic check feature, this is what I did.
I first went to the Recording tab in pavucontrol:
image
And then I switched the monitor:
image

I think I got it working thanks bitstick

You can create a virtual input device using

[pacmd] load-module module-remap-source master=mic_denoised_out.monitor source_name=mic_remap source_properties="device.description='DenoisedRemap'"

This redirects mic_denoised_out.monitor to a Virtual Input Device called mic_remap.
Discord can't detect Cadmus because it's only a monitor and not a "proper" input device.

You can create a virtual input device using

[pacmd] load-module module-remap-source master=mic_denoised_out.monitor source_name=mic_remap source_properties="device.description='DenoisedRemap'"

This redirects mic_denoised_out.monitor to a Virtual Input Device called mic_remap.
Discord can't detect Cadmus because it's only a monitor and not a "proper" input device.

I'll certainly look into doing this.

This has been addressed in #26 & can be enabled in Cadmus 0.0.2 and as such I'm closing this issue. Please do re-open it if the new version doesn't fully solve this issue.