Hello everyone.
Since the beginning of April, the UnityEngine.Windows.Speech response that used to work has stopped working altogether.
I have confirmed that the DictationComplete and DictationError events included in this script are working, but after inputting voice, the DictationResult does not respond (freeze internally?).
This situation is happening here in Japanese, but is it working properly in your environment?
Hi Keikinui,
Same Problem from India, I’m also facing the Same Issues past two days. is there any Solution did you find? let me know
1 Like
Hi kpbind.
Unfortunately may be better to consider other methods (e.g. Whisper) at this point.
WindowsSpeech isn’t a problem that can be solved by scripting alone, but by either Microsoft (who provides NET) or Unity (who knows the API situation very well).
It seems to me that the only thing left to do is to wait for these both companies to realize the problem with Windows.Speech and fix it.
1 Like
hi keikinui, Its working now today here. they fixed the bug from Microsoft
1 Like
Hi kpbind.
I have confirmed that it is back in operation in the Japanese environment here! Thank goodness!
But the fact that it came back into operation with no Windows Update, no UnityEditor update, no source code modification, and no audio clip submission in the privacy and security settings suggests that Windows is (secretly) sending audio data to the MS server?
In any case, as long as you are using an external service, It might want to keep in mind that it may suddenly stop working as it did this time.