-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Support alternative audio input source (Bluetooth adapter) #2481
Labels
Comments
corinagum
added
area-speech
backlog
Out of scope for the current iteration but it will be evaluated in a future release.
Triage-E
front-burner
blocked
currently prevented from making progress
and removed
Pending
labels
Oct 17, 2019
Sample: https://github.com/corinagum/audioconfig-to-ponyfill-webchat |
This is going to be fixed in Speech Services SDK of |
Re-opening until we bump SDK to 1.10.0. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Request
Some browsers may not select the correct audio input source for speech recognition. For Cognitive Services, it support alternative audio input source by specifying the device ID (
navigator.mediaDevices.enumerateDevices
).Implementation details
audioConfig
is already supported in the Cognitive Services adapteraudioConfig
object. And it will hitSpeechServices.js:17
, then hitcreateSpeechRecognitionPonyfill:92
audioConfig
objectaudioConfig
on-the-flyAudioConfig.fromMicrophoneInput(deviceId)
to create theAudioConfig
object with a specific device, https://github.com/microsoft/cognitive-services-speech-sdk-js/blob/master/src/sdk/Audio/AudioConfig.ts#L38[Enhancement]
The text was updated successfully, but these errors were encountered: