Voice search is too sensitive, will not detect when speaking is finished when in a moderately noisy environment like a car or restaurant.
Reported by
markfior...@gmail.com,
Nov 8 2017
|
|||
Issue descriptionSteps to reproduce the problem: 1. Be in a moving vehicle or anyplace with background noise 2. Tap voice search button 3. Speak your search terms 4. Stop talking 5. Wait indefinitely while Chrome continues to listen to background noise, giving you no option to manually stop listening mode 6. Give up and type your search What is the expected behavior? Either improve ability to ignore background noise, or provide a button for the user to indicate that he/she is finished speaking (or both!) What went wrong? The voice search never stops listening when anywhere that has even a low level of background noise, and the system provides no manual means of stopping the process. This causes frustration. Did this work before? N/A Chrome version: 62.0.3202.70 Channel: n/a OS Version: 11.1 Flash Version:
,
Nov 10 2017
This isn't handled internally within chrome, but uses the Google-wide voice recognition system (also used in the Google app, assistant, etc). There is already a bug in that system's internal tracking system to improve detection of the end of voice search queries. I will update that bug to mention the possibility of adding a "finished" button, and will mark this Chrome-specific bug as ExternalDependency. markfiore80: If you continue experiencing issues with this, one way to deal with it is to cover up the microphone on your iPhone by holding the phone near the home button when you finish your query.
,
Nov 21 2017
Does the YouTube app for iOS use the same Google-wide voice recognition system? That app places a microphone button on the screen while it is listening to voice searches, and if you tap that button it will stop listening and conduct your search. If the YouTube app can do it, I would imagine a similar (if not identical) button could be implemented in Chrome.
,
Nov 21 2017
It looks like the YouTube app is using the legacy voice search UI implementation from before Google's rebranding (https://design.google/library/evolving-google-identity/). Moving back to this UI experience is unfortunately not an option in Chrome, but I will escalate the issue with UX and try to come up with a better solution within the new voice search UI.
,
Nov 21 2017
I've created an internal bug with the voice search team to fix this issue, thanks for your report!
,
Dec 17
|
|||
►
Sign in to add a comment |
|||
Comment 1 by olivierrobin@chromium.org
, Nov 10 2017Owner: kkhorimoto@chromium.org
Status: Assigned (was: Unconfirmed)