-
Notifications
You must be signed in to change notification settings - Fork 238
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
Error 7 not reported #527
Comments
@sowens-csd @bsutton Have you found any solution for it? |
I don't remember but this is my final implementation that with reasonable week. https://github.com/bsutton/keiths_list/blob/main/lib/lib/src/speech.dart |
@bsutton It looks like you've set your repository to private. Could you share a screenshot of your speech.dart code in this comment? |
It's now public.
…On Thu, Nov 14, 2024, 11:07 AM Jagaran Maharjan ***@***.***> wrote:
I don't remember but this is my final implementation that with reasonable
week.
https://github.com/bsutton/keiths_list/blob/main/lib/lib/src/speech.dart
@bsutton <https://github.com/bsutton> It looks like you've set your
repository to private. Could you share a screenshot of your *speech.dart*
code in this comment?
—
Reply to this email directly, view it on GitHub
<#527 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAG32OBWXBEPUV3JROMJ2MT2APSTNAVCNFSM6AAAAABJN7W7TOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZVGA3TINJWGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Thank you @bsutton for making your repository public |
On android, if the engine fails to recognize text I'm seeing the following error in the logs:
D/SpeechToTextPlugin(31353): Error 7 after start at 1909 -2.0 / 10.0
My understanding is that this means that the engine was unable to recognize the speech.
The problem is that this error is not reported via the api so the best I can do is report blank text to the user.
I would prefer to be able to trap this error and report something more useful to the user:
e.g. Sorry I didn't understand that.
So is there someway to surface this error via the api?
The text was updated successfully, but these errors were encountered: