Author Topic: [[ critical ]] if i stop using command for a long while the mic goes orange.  (Read 3208 times)

axonMagnus

  • Jr. Member
  • **
  • Posts: 62
the only fix i can do is restart voice attack. then it just works as normal
i thought is was my profile but i very recently trained a new one and deleted the old one still same problem :(



 :'(

Gary

  • Administrator
  • Hero Member
  • *****
  • Posts: 2827
Hi, axon.  Been a while :)

If your mic icon is turning red, that means that the speech engine is telling VA that it is not receiving any audio at all.  VA only communicates what it is receiving from the speech engine in regards to that icon, so, there is something amiss in your speech profile or in some component.  There could also be an issue in your recording chain (mic, sound card, cables, driver, etc.).  You'll want to update your drivers and maybe even try a different headset if you can.  A system scan wouldn't hurt either (it seems like I say that a lot, but it does help... in and out of VA):  https://support.microsoft.com/en-us/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system

Hope you can get that sorted out!

axonMagnus

  • Jr. Member
  • **
  • Posts: 62
it sure has been a while :) am trying out the suggestions :) thank you sir brb :)

axonMagnus

  • Jr. Member
  • **
  • Posts: 62
i forgot to add that my voice attack is on push to listen.i would expect it to be like that when its not pushed or am i wrong ? after a while of not push to listen commands not being done it seems to mute out till i have to restart VA sorry if am confusing things

Gary

  • Administrator
  • Hero Member
  • *****
  • Posts: 2827
VoiceAttack's interface never mutes your mic.  Push to listen/not listen simply indicates when to ignore a speech event (the speech engine is on all the time).  This is so you can have actual voice commands that turn, 'listening' on and also allow for listening overrides.   

While the speech engine is always on, it constantly tells VoiceAttack about its state.  If the speech engine is not receiving any audio (dead signal) from your system, it tells VoiceAttack.  VoiceAttack then shows the red icon.  If the audio comes back, the speech engine tells VoiceAttack that there is audio and VoiceAttack turns the red icon off.

axonMagnus

  • Jr. Member
  • **
  • Posts: 62
VoiceAttack's interface never mutes your mic.  Push to listen/not listen simply indicates when to ignore a speech event (the speech engine is on all the time).  This is so you can have actual voice commands that turn, 'listening' on and also allow for listening overrides.   

While the speech engine is always on, it constantly tells VoiceAttack about its state.  If the speech engine is not receiving any audio (dead signal) from your system, it tells VoiceAttack.  VoiceAttack then shows the red icon.  If the audio comes back, the speech engine tells VoiceAttack that there is audio and VoiceAttack turns the red icon off.

ah i see i understand :) .i made a video to show you :) https://www.youtube.com/watch?v=iFIlpJoTQAo


https://www.youtube.com/watch?v=iFIlpJoTQAo

Gary

  • Administrator
  • Hero Member
  • *****
  • Posts: 2827
Thanks for the video.  This is not VoiceAttack doing something to your system or malfunctioning.  Whether or not your mic (on the channel that it is using for the video) is active or not, your speech engine is no longer getting any audio.  It could be bombing out on its own, or it could be a channel issue (hardware (headset, soundcard)/drivers) causing it to bomb out.  When you restart VoiceAttack, you are re-instantiating the speech engine.  VoiceAttack is only reporting what the speech engine is reporting to it.  There is something amiss on your system.  It could be hardware, driver or software (including your speech engine).  If it is your speech engine and you cannot get it back into line, you should create yet another speech profile just to see if it works:  https://voiceattack.com/SMF/index.php?topic=64.0.  Also, there are alternate speech engines available for use:  http://www.voiceattack.com/alternate


axonMagnus

  • Jr. Member
  • **
  • Posts: 62
indeed it appear you are right. i looked at your documention about using alternative recognition engines and that is just what i did and it appears the problem is not happening anymore :). but like you said on the documention i do lose some functionality :) .especially the all important feed back of feedback when the phrase is not dectated right. either way it fixes it even just a bit . thats fine :)