As I've said, twice before, the microphone input activity indication is showing up in VA in the bottom of the UI.
I asked whether it was
red (rather than gray)
Log entries ? Where would these be located ?
On the main window itself, directly below the "Profile" dropdown. It's not a permanent log file.
Under normal circumstances either a "Recognized" entry should appear when you have finished speaking, if the command is recognized, or an "Unrecognized" entry (with what the speech recognition engine interpreted) if no command is recognized.
Something must have wiped out my previous Win Speech Engine training ...
If you had already trained your speech recognition profile at least three times, in many cases that should be sufficient, but not always, and not necessarily for all words/phonemes.
Normally there would be at least "Unrecognized" entries displayed, however if the speech recognition system was not confident enough in its interpretation, it could have been under the default 50% threshold for displaying it in the log.
That doesn't usually occur unless there are other issues at play. Even untrained, confidence generally shouldn't be that low when speaking clearly, in a quiet environment, using a microphone suitable for speech recognition.
If you are in a noisy environment (including E.G. fan noise from a nearby computer that's picked up by your microphone), you'll want to enable (check) the "Disable Adaptive Recognition (useful for noisy environments)" option on the "Recognition" tab of the VoiceAttack options window.
Also note that any filtering applied to the recording device can impact speech recognition accuracy. It's worth checking the software that came with your device for any filters or "enhancements" that apply to the microphone.
If you do find that recognition accuracy improves by disabling filtering, you'll want to create a new speech recognition profile (instructions can be derived from
this topic) and train that instead.
Speech recognition profiles are speaker (user), microphone and input path, and environment (acoustics and noise) specific.
Lastly, I will mention that some users have reported issues with Logitech headsets where recognition ceases to work entirely either seemingly at random, or after muting and unmuting the microphone.
This is unfortunately an issue with Logitech's driver software (which affects multiple applications, not just VoiceAttack; various people reported this issue to Logitech), which at the time was seemingly only worked around by uninstalling the software entirely.