AVS response is not expected one when more silence at end
The AVS response is varying based on silence duration after speech end for same audio/speech data. Is it expected behaviour. If so, we have to cut the silence. Is there any limitation of silence duration before speech start and after speech end.
I'm referring to the request IDs. When you get a response back from AVS, the HTTP header information will have a header with "x-amzn-requestid: 123b76fffeb7c361-00000264-00000641-17ff9ec37c763ce0-5795db7b-21" (but with some other request ID). We can use that to help debug what's going on. Additionally, what audio are you sending to AVS? Can you send that to us as well? Thanks, Eric
Thanks for sending those! They'll be very helpful as we try to improve Alexa. I was able to duplicate the problem, and I've forwarded the information to the right people. The problem seems to be that Alexa didn't quite understand what was being said. If you go to
https://alexa.amazon.com, you should be able to see what Alexa heard (click 'more' on an information card). For now, you can try other variations on your question until you get a more consistent response. The silence at the end of the audio file shouldn't make a difference. Thanks again for bringing this to our attention!
Thank you so much.... We are not using Amazon Echo device.We have ported AVS on Linux PC and testing the performance. Still we are able to look what Alexa heard in "
https://alexa.amazon.com" ?. If so how? Please