You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the client side (Electron/browser) our WebHID lib supports various dictation microphones.
When one of these devices is available as an audio source we should enforce/select usage of it for audio input.
Because we initialize the lib early and know if we have a supported device we can probably use that supported device type to select the audio source device (or even just regex match SpeechMike or PowerMic).
The text was updated successfully, but these errors were encountered:
A poor-man's approach to this, which would support more devices, would be to allow for listening to the mic full-time, and only enabling transcription when a certain volume threshold is reached. Maybe this is already supported by default - I think the trick would be having a timeout where after some configurable timeout (1 second)? willow would segment the recording.
The reason I call this a "poor man's dictation microphone" is that many mics have a Mute button which should drop the noise floor darn close to zero. In that case, this could be used as a proxy for the Enable button on a "real" dictation microphone.
Apologies if my suggestion lacks context - I'm brand new to the project and still brushing up on its capabilities. I'm very excited about this project!
This issue is intended for specific applications where users already have dedicated dictation microphones from Philips, Nuance, etc.
We have an internal desktop application that binds to a global hotkey in the OS for (basically) push to talk on any hardware. I'm not sure when (or if) we'll ever release it but one of our devs worked on it for another project and it is powered by the WebRTC support in WIS.
On the client side (Electron/browser) our WebHID lib supports various dictation microphones.
When one of these devices is available as an audio source we should enforce/select usage of it for audio input.
Because we initialize the lib early and know if we have a supported device we can probably use that supported device type to select the audio source device (or even just regex match SpeechMike or PowerMic).
The text was updated successfully, but these errors were encountered: