Thanks for checking. There are probably a few things going on.
First, the speech recognition only fires the LDSpeech.Listen event when a match is found., not when it detects speech. This requires that the word/phrase is resent in LDSpeech.Vocabulary and that the same locale is used to initialise the speech recognition engine and the vocabulary. In the past I found the default vocabulary pretty poor so it should be set with LDSpeech.Vocabulary. At present, both locales can only be the same when it is the OS setting locale with same speech recognition locale installed (I don't think using LDUtilities.CurrentCulture will fully work - only being applied to vocabulary with the mismatch maybe being the issue for Scout), so trying to mix or fix locale settings is going to be tricky and I don't want to tackle that till I understand the second issue.
The second issue for me and JR is that it fails on Windows 11 (I always save a SB file to test rather than just running unsaved code that then executes in %temp%). My sample does work nicely for me using Windows 10. I tried a simple Console test project on Win 11 and that also worked fine. However, with the exact same test code copied into LitDev extension and run from SB it fails. There may be some security/anti-virus issue or something else, but this will require more work on my part to try to determine the cause. If/when I can get this working I will probably also make it easier to change locales to make it more generic.
Hopefully I will have updated version to test at some point...
First, the speech recognition only fires the LDSpeech.Listen event when a match is found., not when it detects speech. This requires that the word/phrase is resent in LDSpeech.Vocabulary and that the same locale is used to initialise the speech recognition engine and the vocabulary. In the past I found the default vocabulary pretty poor so it should be set with LDSpeech.Vocabulary. At present, both locales can only be the same when it is the OS setting locale with same speech recognition locale installed (I don't think using LDUtilities.CurrentCulture will fully work - only being applied to vocabulary with the mismatch maybe being the issue for Scout), so trying to mix or fix locale settings is going to be tricky and I don't want to tackle that till I understand the second issue.
The second issue for me and JR is that it fails on Windows 11 (I always save a SB file to test rather than just running unsaved code that then executes in %temp%). My sample does work nicely for me using Windows 10. I tried a simple Console test project on Win 11 and that also worked fine. However, with the exact same test code copied into LitDev extension and run from SB it fails. There may be some security/anti-virus issue or something else, but this will require more work on my part to try to determine the cause. If/when I can get this working I will probably also make it easier to change locales to make it more generic.
Hopefully I will have updated version to test at some point...