Microphone starts and stops responding at random

[Kalle]

Thanks...  That was by design... I was under the impressions that sub-phrases are not included in the potential variables.  Also the system has no problem distinguishing between commands, the natural language works really well.  It's just some times when I restart and rer-render my Grammer engine the system times out on the microphone.  As I said it doesn't do this all the time. 

I have addressed this idea of having more natural language integrated in a more efficient way in the forums, I hope this is addressed as it allows for remembering and acting on commands a whole lot more fluent not to mention I don't like being rude to my computer, and especially at front of my four year old daughter..  Please and thankyou are a prerequisites of living in this household LOL...

Thanks again...

I welcome this polite attitude  What I mean is - the "payloadDictation" phrase at the first, can you remove a lot of work with the phrases and does not restrict you to a phrase - only the trigger phrase is need.

sorry for my bad english   

Kalle

[jitterjames]

If you use an optional payloadDictation then you will not know which payload to use for the subsequent actions which load music / video etc.  (i.e. {1} or {2}

You could get around this using a logic block but it seems like more trouble than it is worth.

If you want to use a wildcard in the phrase, I believe you can use * however this will obviously make it harder for VoxCommando to differentiate commands efficiently so I don't recommend it.

[jitterjames]

...  It's just some times when I restart and rer-render my Grammer engine the system times out on the microphone.  As I said it doesn't do this all the time. 

I don't really know what you mean by this.  At this point, I'd like to try to help you with your microphone issues but don't understand what is actually going on.  If you could describe your symptoms as precisely as possible and try to use unambiguous language (think legal documents) then I'll see if I can figure something out.  Try to give me some step by step cause and effect and include the log file, and/or a snapshot of the history window.

I also suggest you disable the "timer to reinitialize microphone" by setting the value to 0 in advanced options.  There is also a setting in mobiola to substitute another microphone when mobiola is off.  I haven't found this to work very well but you should experiment with different settings on that.  Probably best to disable it.

[thesystemera]

Let me try and explain better... 

When editing my XML and then applying settings [as in saving and rebooting voxcommander, Voxcommander [not always but most of the time] will not respond to any of my commands.  I will do a grammer rebuild and then another reboot [and still the same thing].    The error "time since mic event, trying to reset, mic reset" comes up and after a while VoxCommander comes back on-line. 

To get VoxCommander responding again, it is hit and miss.  Some times a full reboot of VoxCommander willl do it, some times a re-render of "missing grammar".  It seems to be pretty random.  What I have noticed is that when the rebuilding of the grammar file takes a short period of time it will not work yet when rebuilding takes a while it generally seems to work..  Once again I appear to have none of these issues when using a standard config...

As I have stated, when using the standard XBMC.Zip that comes with software as standard, I do not have these mic issues.  The issues have most definitely arisen as a result to changes I have made to my xml.  But as I"ve stated, when it works, it works great.  It seems to be an issue with initialisation of the revised XML but when it goes, it goes great...

[Kalle]

Let me try and explain better... 

When editing my XML and then applying settings [as in saving and rebooting voxcommander, Voxcommander [not always but most of the time] will not respond to any of my commands.  I will do a grammer rebuild and then another reboot [and still the same thing].    The error "time since mic event, trying to reset, mic reset" comes up and after a while VoxCommander comes back on-line. 

To get VoxCommander responding again, it is hit and miss.  Some times a full reboot of VoxCommander willl do it, some times a re-render of "missing grammar".  It seems to be pretty random.  What I have noticed is that when the rebuilding of the grammar file takes a short period of time it will not work yet when rebuilding takes a while it generally seems to work..  Once again I appear to have none of these issues when using a standard config...

As I have stated, when using the standard XBMC.Zip that comes with software as standard, I do not have these mic issues.  The issues have most definitely arisen as a result to changes I have made to my xml.  But as I"ve stated, when it works, it works great.  It seems to be an issue with initialisation of the revised XML but when it goes, it goes great...

Ok, I've tested your "voicecommands.xml" without any problems. I've used the follow settings:

1. Windows7-32bit-Ultimate
2. VoxCommando Ver.0.950 from here: http://voxcommando.com/forum/index.php?action=dlattach;topic=797.0;attach=1427
3a. AKG WirelessPro-System with a t.bone earmic 500
b. ASUS Wireless Headset HS1000W
c. Mobiola Headset with iPad2
4. In VC Options/Advanced: timer to reinitialize microphone disable (0)

After editing your commands or changing any settings, it is better you make always a full restart.

All commands work fine, no mic problems.

Kalle

[thesystemera]

Interesting.  I'm running under Windows 64bit Premium.  Using your latest Beta 9.50.  Grr...

Could possibly be a network issue.  This is strange..  Well it's kind of good to know it is not my xml. 

[Kalle]

Interesting.  I'm running under Windows 64bit Premium.  Using your latest Beta 9.50.  Grr...

Could possibly be a network issue.  This is strange..  Well it's kind of good to know it is not my xml. 

Do you have a chance to test it with a "normal" mic - not mobiola headset?
If you have a notebook or other pc, test your configuration on this devices (not over network)

[thesystemera]

That is the next logical step..  Will attempt that today..  I'm an audio-engineer so I will be testing with the only dedicated mic I have  A Rode NT2 Condenser Mic..  Pretty good studio quality.. LOL...

Thanks, will get back to you guys...

[thesystemera]

Have not tested with a normal mic yet...

Will do soon...  worth noting that when voxcommando has issues, no other apps seem to..  Windows speech continues to work, I can record using sound recorder just fine with no artefacts and al levels are showing in 'recording devices'.. 

I am a little confused, I was under the impression that windows managed the speech recognition and just passed on the speech recogntion data to voxcommando...  I am under the belief this is not a network issue as there are no artefacts in the audio, no dropout, nothing.    I am about to try using Mobiola headset on my iPad 2....  and only after this will I lug out my mixer and studio mic....

LOL....

[thesystemera]

Tried the iPad 2... Once again, Windows and sound recorder have a great sound.  Levels are showing but VoxCommando is showing blank..

Are there logs I can access that might give me a clue?  I'm' going bonkers here....

[thesystemera]

What I have also noticed is that it always seems to happen when I restart VoxCommando...  It's never just half way through, as when it starts going it seems to be fine for hours...  As far as I can recall..  I was also wrong earlier, it appears to have little to do with my XML.  I think I came to this conclusion because that is when I was restarting VoxCommando the most...

Hahahaha... I think I have just discovered the problem..  AARRGG

I had changed my port from 8080 to 8081 because of an earlier issue with the iPhone remote control and it seems this port has been pausing VoxCommando.  I noticed this when VoxCommando would read back sypnopsis to me, I changed back to 8080 which no longer has issues and the system seems to not be flaking out..

Let me continue trying for some more time... I'm sorry to have wasted every one's time, I'm rather embarrassed if this is the case...

[thesystemera]

Well so much for that... I am wrong, I give up....

AARRGG... It is like it just looses the power to recognise.  When it was spazzing I decided to try recording, and yet the voice is coming through loud and very clear...  I don't understand it.  Says nothing in the logs either, just that it is timing out...  I have spent too long on this...  I wil try with my other mic, but the point is I want to use this with my cellphone and if I can't do that, then there is no real point...

any way lets test the mic array...

[Kalle]

Let me continue trying for some more time... I'm sorry to have wasted every one's time, I'm rather embarrassed if this is the case...

Please don't give up and nobody wasted our time if we can help a VC member  

You said the standard XBMC config of VC run without this problems  
You can disable for first all XBMC commands that you have edited with a right mouse click and activate it step by step, perhaps you can find the issue in this case. Make a full restart after each change and test it.
It is nice to know we have an audio-engineer as a member  .

Kalle

PS: you can install a second instance of VC in a other folder with the standard XBMC configuration, open both VC, so you can drag'n drop and exchange each command step by step. How you can start a second instance of VC find here.
http://voxcommando.com/forum/index.php?topic=797.msg6400#msg6400

[Kalle]

Well so much for that... I am wrong, I give up....

AARRGG... It is like it just looses the power to recognise.  When it was spazzing I decided to try recording, and yet the voice is coming through loud and very clear...  I don't understand it.  Says nothing in the logs either, just that it is timing out...  I have spent too long on this...  I wil try with my other mic, but the point is I want to use this with my cellphone and if I can't do that, then there is no real point...

any way lets test the mic array...

If you want use VC without a Wireless headset and the cellphone option is waste, you can invest in a Wireless Audiobox.
http://voxcommando.com/forum/index.php?topic=595.0 this small box is a bit bigger as a matchbox and works great in a range from 8-10 meters. This one is my favorite after the amulet and AKG miniPro mic and it cost 40$.

[jitterjames]

Why don't you send us your log file?

I don't think this is a microphone problem.