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

Cognitive Speech Services sample closes the microphone before human can speak. #2469

Closed
corinagum opened this issue Oct 14, 2019 · 7 comments
Assignees
Labels
area-speech Bot Services Required for internal Azure reporting. Do not delete. Do not change color. bug Indicates an unexpected problem or an unintended behavior. customer-replied-to Required for internal reporting. Do not delete. customer-reported Required for internal Azure reporting. Do not delete. needs-repro Waiting for repro or investigation

Comments

@corinagum
Copy link
Contributor

corinagum commented Oct 14, 2019

Note: customer-reported label is accurate, and I'm just bringing the comment to a newly filed bug.

Originally brought to our attention by @alokraj68 on issue #1848

Screenshots

microphone

Note that when clicked, the microphone almost immediately disables.

Version

latest bits (4.5.4/master)

Describe the bug

When clicked, the microphone button appears to enable speech detection very briefly, but not long enough for a user to say anything, then immediately disables. There is no apparent way to keep speech detection open longer. Holding down the microphone button does not change behavior.

To Reproduce

Steps to reproduce the behavior:

  1. Go to https://microsoft.github.io/BotFramework-WebChat/06.c.cognitive-services-speech-services-js/
  2. Click on the microphone button
  3. Attempt to say 'help'
  4. Notice that the microphone almost immediately closes.
  5. Note that there are no console errors.

Expected behavior

Speech detection should be available long enough for the user to say something.

Additional context

I am assigning this bug to @compulim for investigation.

[Bug]

@corinagum corinagum added bug Indicates an unexpected problem or an unintended behavior. Pending customer-reported Required for internal Azure reporting. Do not delete. Bot Services Required for internal Azure reporting. Do not delete. Do not change color. needs-repro Waiting for repro or investigation customer-replied-to Required for internal reporting. Do not delete. labels Oct 14, 2019
@alokraj68
Copy link

Hi, to add up,
am doing speechServicesPonyfill.speechSynthesis.cancel(); to stop the speech when the user is clicking a button. after sometime when the user try to resume speech I want to clear any pre-existing ones in the queue and activate speech recognizer. But once this cancel is called, after some seconds I get this Log message and the mic becomes not responding.

@corinagum
Copy link
Contributor Author

Hi @alokraj68, thanks for your patience!

I'm sorry to say that the issue I filed above was a dev error on my part. Our team's bot's speech token had expired which is why I was unable to use speech with Web Chat.

However, I investigated your issue using Web Chat's latest bits (and a non-expired token!) and I believe the issue you are reporting is fixed, meaning that the fix will be available after our release at the beginning of November.

Could you try your scenario using Web Chat's latest bits? Please see our documentation on pointing to our MyGet feed for latest bits.

I am going to close this issue because the bug I filed and what you are experiencing are different. However I am still happy to investigate this with you. After you test MyGet bits, if you are still having problems, could you please:

  1. File a new issue
  2. Include a video reproducing your error, and also provide your console errors

If testing on latest bits fixes your problem, please feel free to leave a comment on this thread and I will see your update. Thank you!

@alokraj68
Copy link

alokraj68 commented Oct 17, 2019

Hi @alokraj68, thanks for your patience!

I'm sorry to say that the issue I filed above was a dev error on my part. Our team's bot's speech token had expired which is why I was unable to use speech with Web Chat.

However, I investigated your issue using Web Chat's latest bits (and a non-expired token!) and I believe the issue you are reporting is fixed, meaning that the fix will be available after our release at the beginning of November.

Could you try your scenario using Web Chat's latest bits? Please see our documentation on pointing to our MyGet feed for latest bits.

I am going to close this issue because the bug I filed and what you are experiencing are different. However I am still happy to investigate this with you. After you test MyGet bits, if you are still having problems, could you please:

  1. File a new issue
  2. Include a video reproducing your error, and also provide your console errors

If testing on latest bits fixes your problem, please feel free to leave a comment on this thread and I will see your update. Thank you!

Hi,
I could see the latest bits documentation. But is it available for CDN? its only telling how I can install it, but not how I can consume the same.
Could you please add it? #2479

@alokraj68
Copy link

alokraj68 commented Oct 23, 2019

Hi @alokraj68, thanks for your patience!

I'm sorry to say that the issue I filed above was a dev error on my part. Our team's bot's speech token had expired which is why I was unable to use speech with Web Chat.

However, I investigated your issue using Web Chat's latest bits (and a non-expired token!) and I believe the issue you are reporting is fixed, meaning that the fix will be available after our release at the beginning of November.

Could you try your scenario using Web Chat's latest bits? Please see our documentation on pointing to our MyGet feed for latest bits.

I am going to close this issue because the bug I filed and what you are experiencing are different. However I am still happy to investigate this with you. After you test MyGet bits, if you are still having problems, could you please:

  1. File a new issue
  2. Include a video reproducing your error, and also provide your console errors

If testing on latest bits fixes your problem, please feel free to leave a comment on this thread and I will see your update. Thank you!

Hi @corinagum ,

I tired out the latest bits and the issue is not coming in it. but I am not able to cancel the pending speech. The speech synthesis is working for every message after I give the cancel. Is the clear all method missing for speech synthesis?

Expected: Speech synthesis should not speak out once the cancel or stop is called.

Actual: It continued to work for every subsequent messages. Also, the pending queue is also played.

@alokraj68
Copy link

@corinagum, the issue I was saying is still there in 4.6 Version.

Hi @alokraj68, thanks for your patience!
I'm sorry to say that the issue I filed above was a dev error on my part. Our team's bot's speech token had expired which is why I was unable to use speech with Web Chat.
However, I investigated your issue using Web Chat's latest bits (and a non-expired token!) and I believe the issue you are reporting is fixed, meaning that the fix will be available after our release at the beginning of November.
Could you try your scenario using Web Chat's latest bits? Please see our documentation on pointing to our MyGet feed for latest bits.
I am going to close this issue because the bug I filed and what you are experiencing are different. However I am still happy to investigate this with you. After you test MyGet bits, if you are still having problems, could you please:

  1. File a new issue
  2. Include a video reproducing your error, and also provide your console errors

If testing on latest bits fixes your problem, please feel free to leave a comment on this thread and I will see your update. Thank you!

Hi @corinagum ,

I tired out the latest bits and the issue is not coming in it. but I am not able to cancel the pending speech. The speech synthesis is working for every message after I give the cancel. Is the clear all method missing for speech synthesis?

Expected: Speech synthesis should not speak out once the cancel or stop is called.

Actual: It continued to work for every subsequent messages. Also, the pending queue is also played.

@corinagum
Copy link
Contributor Author

@alokraj68, unfortunately I am not able to reproduce your issue on latest bits using one of our speech samples.

@alokraj68
Copy link

Hi, I will open this as a new issue since it seems different from this one. #2568

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-speech Bot Services Required for internal Azure reporting. Do not delete. Do not change color. bug Indicates an unexpected problem or an unintended behavior. customer-replied-to Required for internal reporting. Do not delete. customer-reported Required for internal Azure reporting. Do not delete. needs-repro Waiting for repro or investigation
Projects
None yet
Development

No branches or pull requests

3 participants