Post Registration -> Vox Still tuns itself off

[lightshow]

So I just got a registration key and registered VoxCommando.

Now, in the program it still says that it is registered.

When I first open it, I can put it in listen mode and go thorugh a few commands.  After about 10-15 seconds, Vox gives itself the command to turn itself off.

Then if I try to put it in the active (green) mode again, it will take about 10-15 seconds and tell itself to turn off.

What can I do?


Thanks,

[Kalle]

So I just got a registration key and registered VoxCommando.

Now, in the program it still says that it is registered.

When I first open it, I can put it in listen mode and go thorugh a few commands.  After about 10-15 seconds, Vox gives itself the command to turn itself off.

Then if I try to put it in the active (green) mode again, it will take about 10-15 seconds and tell itself to turn off.

What can I do?


Thanks,

Hi lightshow,

go to "options" menue and look for "set idle time out after sec". Set to 0 (zero) and full restart Voxcommando

Kalle

[jitterjames]

Is VoxCommando going into standby mode (turning yellow), or is it telling you that the trial mode only allows 25 commands and that you need to restart?

If it is going into standby mode, the Kalle is probably correct and you need to disable the "Idle Timeout" which is on the "General" tab of the options page.

[lightshow]

I checked the timeout value and it was already 0.

Today I launched VoxCommando v. .875 and told it a few commands to control XBMC (which were sucessful), then after about 45 seconds this time of idle, voxcommando goes into vox off mode.

Then I manually clicked into into green on mode. and after 15 seconds of idling, it goes into vox off (red mode).


My General Options page shows Idle Timeout as 0.

Nothing else is modified except the http ports to control xbmc and the login pass for xbmc control (which works since it does the voice commands to xbmc actions just fine).


Also, I do NOT have the checkbox checked by the green Mic picture that turns it to standby after each command.   What I'm seeing is it going from Green Active mode straight to Red Vox Off mode after 15 sec of inactivity.

[jitterjames]

First of all, I want to make it clear that this has nothing to do with registration or activation, because trial accounts don't go into red mode, they pop up a window telling you to restart.

Something else must be turning it off.  Either a network message (like from Amulet) or a voice command that is being triggered by accident, or... something.  Are you using eventGhost?

Please do another test and immediately after it turns itself off make a copy of voxLog.txt

then send me the voxLog.txt

also you can try

- zip your whole folder and send it to me.  (it should still be pretty small)
- make a video showing what happens so we can see the history window.

I'm sorry you are having this problem. I've never seen it before.  I'm pretty sure we can sort it out but if not you can have a full refund if you want.

[lightshow]

I posted to voxlog on pastebin (since I didn't see anything like license keys or anything in it)

http://pastebin.com/LRPC8gJf


It seems something is sending the Vox Off message:

3/9/2011 6:56:08 PM   365   doCommand:Play, Pause
3/9/2011 6:56:08 PM   366   execute:  XBMC.Send - Action(12)
3/9/2011 6:56:08 PM   386   sending this command to xbmc: http://127.0.0.1:8080/xbmcCmds/xbmcHttp?command=Action(12)
3/9/2011 6:56:08 PM   394   received udp command:OnPlayBackResumed;1
3/9/2011 6:56:11 PM   514   alternate:vox off
3/9/2011 6:56:11 PM   515   alternate:pause
3/9/2011 6:56:11 PM   544   doCommand:Vox Off
3/9/2011 6:56:11 PM   545   execute:  VC.Off -
3/9/2011 6:56:21 PM   710   received udp command:OnPlayBackStopped;1
3/9/2011 6:56:21 PM   719   received udp command:OnPlayBackStopped;1


Also, I don't mind doing a fresh installation if you think that'd help me.   Oh, and I don't have event ghost running on my machine.

Also, I can send you the rar file of my install via email in a sec

[jitterjames]

I am the first to admit that the log itself could be better.  It is hard to be sure, but it seems like VC thinks it is hearing the vox off command.

As a test, could you please edit your command tree and delete the VoxOff command completely.  You will find it in the first group called "Vox Commands"

I don't know what your microphone setup is, but it really looks like it is just hearing the command.  I notice that it happened right after a movie started playing so maybe the microphone is picking something up and getting confused.  Also, if you have "accoustic echo cancellation" enabled on your windows recording device this can sometimes lead to problems so you might try turning that off.

The reason accoustic echo cancellation can cause problems is that it will try to subtract the sound being output (by a movie) from what is coming in through the microphone.  If the microphone is quiet, the subtraction creates a negative sound with is effectively the same as the sound itself... it's stupid I know, but it can happen.

Anyway, I tested the rar that you send me and it seems fine so I think it is just a case of it thinking that it hears the Vox Off command.

Please let us know if this helps at all.  If not, maybe I can connect to your computer using Team Viewer to try to diagnose the problem.

[lightshow]

So I've gone into the command tree and deleted the Vox Off command.

What you suggested is indeed what is happening.  The Laptop is using its built in mic to receive voice commands and it can also hear the laptop's speakers.

It assumes that the first words (or loud music) it hears is for the command vox off.  I put it in standby mode and just see it keep repeating the command vox off from any sound it hears from my laptop speakers (watching a tv espisode of house).   But since it's in standby, it won't execute the command...

So I watch it ramp up and down from 78% -> 95% and up with the vox.. vox off command.  That is the only word/phrase it ever thinks it is hearing by picking up the laptop's speakers.


Now, after I did delete the Vox Off command from the command tree, is there somewhere else I can go into to delete any more instances of Vox Off that would trigger the Vox Off process?  This is the first time I even knew about the tree (which is pretty cool!).

I will be using ignore me rather than Vox Off in normal use, so removing all Vox Off voice recognition is what I would go for.


Also, I'm in and out a lot this week, so I apologize if I am late at testing / responding over the next few days.


Thanks James.


Edit:  acoustic echo cancellation is not enabled on the mic.

[jitterjames]

the best advice that I can give is to separate your microphone from your speakers as much as possible.  A cheap usb microphone on a 10 foot usb cable might make a better choice.

Check your sound settings to see if you get better results with  acoustic echo cancellation on , or off.  It varies from one computer to another.  Also usually noise cancellation is better turned off.

You can try training your computer to your voice by using windows speech training utilities.

You can try reducing the input level of your microphone.

If you see commands that are being triggered accidentally you can change the phrase.  You can also try using Honey-Pot phrases that do nothing, but sound similar to the commands that are being triggered accidentally.

the list goes on.  Having something like the Amulet Remote makes most of these types of problems go away.  Alternatively having a remote button that turns VC on and off can help.  I don't generally find leaving a microphone running all the time listening is a good idea, unfortunately.

[jitterjames]

Now, after I did delete the Vox Off command from the command tree, is there somewhere else I can go into to delete any more instances of Vox Off that would trigger the Vox Off process?  This is the first time I even knew about the tree (which is pretty cool!).

I will be using ignore me rather than Vox Off in normal use, so removing all Vox Off voice recognition is what I would go for.

by default there is only one "vox off" command in the tree so you would only need to delete the one command.

[Kalle]

by default there is only one "vox off" command in the tree so you would only need to delete the one command.

Why delete the command? renamed the phrase to "please Vox off" and test it.