Voxwav 2.2.1

[painy]

James. I've found 2 'bugs' after playing with voxwav for some time.
- Hard thumps on my phone (like tapping it hard) or sudden very quick movements (e.g. sideways, not necessarily tilting the device 90 degrees around the x-axis like one normally does to activate the mic) activates the microphone a couple of seconds. The mic automatically deactivates without me moving my phone or pressing any buttons. Phone: galaxy S2, cyanogenmod 10 (jelly bean).
- voxcommando regularly crashes when using voxwav. Windows shows a VC error message (but VC keeps working if I ignore the warning every-time i think). I'm not sure what triggers the crash. I'll keep you updated!

Any other users who experience this behaviour?

[jitterjames]

James. I've found 2 'bugs' after playing with voxwav for some time.
- Hard thumps on my phone (like tapping it hard) or sudden very quick movements (e.g. sideways, not necessarily tilting the device 90 degrees around the x-axis like one normally does to activate the mic) activates the microphone a couple of seconds. The mic automatically deactivates without me moving my phone or pressing any buttons. Phone: galaxy S2, cyanogenmod 10 (jelly bean).

Hi Painy,  Thanks for the update.  I've got some questions though.

For the first thing, I'm not too clear on why you consider this a bug.  The accelerometer is reacting to an extreme acceleration when you bump it.  If it is gracefully turning itself off again I'd say this is the best behaviour one could hope for. Maybe I'm not understanding you correctly.

For the second thing, if VC continues to work then crash is not the word I would use. I guess VC is actually throwing an error message?  If so please tell me what the error message says, if anything.  If you are able to make a connection between something specific happening in VoxWav that might be happening at the same time as, or just before this error please let me know.

[LOCOSP]

Hi, any chance for iOS app ?

[jitterjames]

No. No chance.

[ajith]

I too experienced the "second thing" that painy reported above. There is no error message from VC, but Windows reports that "This application has stopped. Do you want to close it?" or something to that effect. I'm afraid I haven't observed any pattern to this behavior. One difference I noted from painy is that, for me, VC also stops responding when this happens. I need to do a full restart of VC to recover from this condition. So maybe it is not exactly the same issue I am facing. I'd be glad to test anything specific and report. Do let me know.

[painy]

My error message is Voxcommando has stopped working. A problem has caused the program to stop working correctly. Windows will close the program and notify you when a solution is available. The only button says close program. If i ignore the warning, the program continues to work (the voice commands, i can no longer use the VC program interface)

[xtermin8r]

My error message is Voxcommando has stopped working. A problem has caused the program to stop working correctly. Windows will close the program and notify you when a solution is available. The only button says close program. If i ignore the warning, the program continues to work (the voice commands, i can no longer use the VC program interface)

Does anything strange appear in the system tab window of vc ?

[Kalle]

Does anything strange appear in the system tab window of vc ?

No, I'm sure it comes from the android device (jelly bean). It seems like the wav file is not written in the windows temp folder only the tmp file.

[jitterjames]

Does anything strange appear in the system tab window of vc ?

What is that xtermin8r ?  Do you mean the history tab of the main window in VC?

Is this error only happening when using the evil "jellybean" OS?

Please send me some VC logs when you get a chance.  I have no idea what this could be.

[Kalle]

What is that xtermin8r ?  Do you mean the history tab of the main window in VC?

Is this error only happening when using the evil "jellybean" OS?

Please send me some VC logs when you get a chance.  I have no idea what this could be.

Yes it looks like the jelly bean is the problem. I used the same VW and VC with Ice cream and has no problems.
What I can say is: VW send a file to the temp folder in Windows and it has only a tmp extention and not a wav.
Is it possible the JB send a wrong audio format?

Kalle

update: I have no JellyBean - it is the last IceCream update from 4.0.3 to 4.0.4 it looks like Samsung ahs touch the audio-quality problem and the mic gain is much higher.

[bodiroga]

Yes it looks like the jelly bean is the problem. I used the same VW and VC with Ice cream and has no problems.
What I can say is: VW send a file to the temp folder in Windows and it has only a tmp extention and not a wav.
Is it possible the JB send a wrong audio format?

Kalle

I can also confirm that it's happening with my Jelly Bean device.

[Kalle]

I can also confirm that it's happening with my Jelly Bean device.

@bodiroga

Can you try a test with VoxWav?

please whisper a command to VoxWav and let us know if VC understand the command (I mean really whisper)

Thanks
Kalle

[bodiroga]

@bodiroga

Can you try a test with VoxWav?

please whisper a command to VoxWav and let us know if VC understand the command (I mean really whisper)

Thanks
Kalle

WTF!!!! 

If I whisper or shout to VoxWav (I'm using the free version now but I will buy the pro version when this problem is fixes ) then VoxCommand crashed automatically.

Does this only happen with Jelly Bean? My Galaxy Nexus, SII and Nexus 7 all have JB installed so I can't test with ICS or GB...

Best regards,

Aitor

[Kalle]

WTF!!!!  

If I whisper or shout to VoxWav (I'm using the free version now but I will buy the pro version when this problem is fixes ) then VoxCommand crashed automatically.

Does this only happen with Jelly Bean? My Galaxy Nexus, SII and Nexus 7 all have JB installed so I can't test with ICS or GB...

Best regards,

Aitor

To fix the problem with JellyBean - go to TCPplugin settings in VoxCommando and set the TCP volume to 25% and set a checkmark on "show most rescent wav" and test it (don't forget to click on "save option" after change a setting). You can try different volume settings, but for me is 25% the best.

[attachment=1]

Let us know if this solve the problem.

Kalle

[jitterjames]

Hi Everyone.

Version 2.3 of VoxWav should be available on Google Play now.

Please update your tcpMic plugin with this .dll file (see attached).

If you experience crashing still please let me know.

If you experience poor recognition please go into VoxWav settings and select "Mic Source", then try "MIC" or "VOICE_RECOGNITION".

You can try others but one of these two will usually work best, depending on the phone, and some others won't work at all.