this is one of the weird behaviors of my PC, not sure if it VC windows or something else...

sometimes when I put VC into standby or listen mode after extended period of being off, it do not initialize the mic ...

while windows SR can hear, VC do not

this is always resolved after restarting VC

Did you tried this?
http://voxcommando.com/mediawiki/index.php?title=Options#Time_to_Reinitialize_Microphone

Weird.  What kind of sound card / audio input are you using?

Quote from: Kalle on February 02, 2015, 04:28:54 PM
Did you tried this?
http://voxcommando.com/mediawiki/index.php?title=Options#Time_to_Reinitialize_Microphone

I thought about it ...but then I thought that won't solve it, because the audio bar in windows SR setting is moving but not in VC
Unless the Audio Bar is implemented differently between windows control panel and VC

@James
it is mac mini 2006 internal sound card... IDT High Definition Audio CODEC

Kalle's suggestion was a perfectly logical one.  But if turning VC off and on manually does not help, then the mic reset feature will not help either, and that option should normally only be used as a last resort.

Does it happen when you use a "normal" configuration.  Or only with your "crazy" configurations? 

I do see an out of memory exception so it could be related to that.

It could be related to the fact that you are using a Mac, but probably not.

Did this only start to happen recently?

What seems to be happening is that the speech engine is getting frozen and actually can't turn off, and so it also can't turn on again.  I've never seen that happen before though so I assume you have some kind of problem either with your system resources, or with your VC configuration.  It is kind of hard to diagnose from here.

Quote from: jitterjames on February 03, 2015, 08:53:56 AM
Does it happen when you use a "normal" configuration.  Or only with your "crazy" configurations? 

ouch ... my feelings ... my feelings !!!! 

I only have one set of configurations ... and it is crazy   

as for the out of memory exception it is sometimes VC growing to 170MB in memory ... I will try to see if there is a relation ...
as for the Mac I do not think so ... they are best PCs 

and this was not the first time ... but it happens now and then not on daily bases ...

Quote from: jitterjames on February 03, 2015, 08:53:56 AM
What seems to be happening is that the speech engine is getting frozen and actually can't turn off, and so it also can't turn on again.  I've never seen that happen before though so I assume you have some kind of problem either with your system resources, or with your VC configuration.  It is kind of hard to diagnose from here.

is there is a way to "reset" the speech engine without a full restart ? maybe that could be a new command as in Vc.resetSREngine or something like that
I guess for the time being I will just program VC to do full restart once or twice a day ...

I have to say I regularly experience this too. I'm using a normal microphone plugged into the PC's Mic In socket.

When in standby, it usually takes several attempts to wake VC up.  It just doesn't seem to hear.  The Windows mic level meter is continuously moving but VC's meter isn't.

I'll check resource issues but the PC should be fine I think.

This does not sound like the same issue at all.

Feel free to post a log next time it happens.

I too have the same problem tho it only happens in VoxCommandoSP so I don't know if this is a bug or limitation for the SP version.

I have 2 Kinect and only 1 specific one works in SP, even when I mute it in the setting, it will un-mute itself when I restart VC-SP.

I fixed my problem. Someone might want to give this a try.

http://voxcommando.com/forum/index.php?topic=2038.msg17620#msg17620