Problems with VoxWav Free 2.1

[DHHJ]

I've been away for awhile and just updated to 968 and VW Free 2.1- great progress! Can't get it to work- no recognition of any loaded commands.

I have kept the default TCP settings in VW and enabled TCPMIC to listen to 33339. I am using d:\wavwatch as my share in VC. I can access the folder from my tablet from a File Explorer- no firewall issues.

The History pane shows:

Events&&AV.Mic.On
AV.Mic.On
Events&&AV.Mic.On
AV.Mic.Off
TCPWav.Open
no sox processing
Wav.Reco.Complete

Here are the last few pertinent lines from the log file ( I think!)
12/12/2012 10:17:08 PM   21   TcpMic: C:\Users\Dad\AppData\Local\Temp\TcpMicTmp1611.wav (563) read bytes: 8192
12/12/2012 10:17:08 PM   22   TcpMic: Clipping count: 0
12/12/2012 10:17:08 PM   23   TcpMic: C:\Users\Dad\AppData\Local\Temp\TcpMicTmp1611.wav (564) read bytes: 7976
12/12/2012 10:17:08 PM   25   TcpMic: Clipping count: 0
12/12/2012 10:17:08 PM   27   TcpMic: C:\Users\Dad\AppData\Local\Temp\TcpMicTmp1611.wav (565) read bytes: 0
12/12/2012 10:17:08 PM   28   TcpMic: disconnected
12/12/2012 10:17:08 PM   31   TcpMic: total bytes: 4587528
12/12/2012 10:17:08 PM   32   TcpMic: wav header OUT
12/12/2012 10:17:08 PM   36   TcpMic: creating fileinfo for: C:\Users\Dad\AppData\Local\Temp\TcpMicTmp1611.wav
12/12/2012 10:17:08 PM   37   TcpMic: setting fileinfo attributes to temporary
12/12/2012 10:17:08 PM   911   trying to open: C:\Users\Dad\AppData\Local\Temp\TcpMicTmp1611.wav
12/12/2012 10:17:08 PM   945   TcpMic: Closing TcpClient
12/12/2012 10:17:10 PM   479   trying to delete file:C:\Users\Dad\AppData\Local\Temp\TcpMicTmp1611.wav
12/12/2012 10:17:10 PM   482   DELETED wav file:C:\Users\Dad\AppData\Local\Temp\TcpMicTmp1611.wav


What am I missing?!

[Kalle]

I've been away for awhile and just updated to 968 and VW Free 2.1- great progress! Can't get it to work- no recognition of any loaded commands.
...

Hi DHHJ, you can try different mic settings in VoxWav. Settings->Audio settings->Mic input: set first to "mic" and tried again.

I hope this help  
Kalle

[jitterjames]

Hi DHHJ.  Welcome back.

A few things.

1 - you don't need to configure a shared folder any more so no need for d:\wavwatch
2 - Kalle's suggestion is good.  You can also try setting the "Mic Source" in VoxWav settings to "VOICE_RECOGNITION"

Based on the log, I would say it looks like the information is getting transferred from VoxWav to VC OK.  The problem may be with the quality of the signal, or the level.

In the TcpMic plugin settings do the following:

- place a checkmark next to "Save a copy of the Wav file in .\Wavs
- place a checkmark next to "Show most recent waveform"
-click "Save Options"

then try to issue a voice command from VoxWav

- send us a snapshot of the image of the waveform that appears in the plugin settings window
- send us the wav file which is saved in your VC folder\Wavs\TcpMic####.wav

the waveform should be well within the two black lines.  See a sample of what mine looks like attached.

If the waveform is too large you can try to place a checkmark next to "Adjust Volume (%)" and try  a number less than 100 to reduce the volume.  You can also try holding the microphone on your Android further from your mouth.

It can also help to create a blank speech profile with no training, if the speech engine is too well trained for your other microphone and expects your voice to sound a certain way.

Hope this helps.

[DHHJ]

Thanks Kalle, James.

I changed the Mic Source to Mic and that helped considerably!  The TCPMic plug in is a great addition- no more wav folder! I assume the change is to transmit the voice right over the UDP port?

James, I just switched over to the Bell FibeTV service and will now work on integrating VC/VW with it- I'l hopefully post a video when its ready- probably take a couple of weeks or so due to XMAS priorities!

I would also suggest looking at putting an install pdf, wiki or training video together as there have been significant changes to how VC works and integrates with Android. Just suggesting.......

Great app and integration work. What's next?!

[jitterjames]

Actually it is transmitted using TCP but the messages other than the actual sound data are still  on UDP (for now anyway).  Using a TCP socket is much better for a number of reasons.  Mainly it's easier to set up, and much faster.

Yeah, I'm currently working on this guide for VoxWav:

http://voxwav.wikispaces.com/ [No longer valid. See the voxwav pages on our main wiki. 06-2015]

I am currently re-writing the tree editor.  I have already spent about 4 solid days writing code and I hope to release a beta of it very soon.  it may not look that different at girst glance, but for people like me that use the editor a lot, it is actually a significant upgrade.

It will be much better for copy/paste and drag/drop, and working on multiple trees etc.  We will be able to drag xml directly from the tree to the forum and back again.  You can also drag a group directly to a file folder or your desktop.  copy / paste / delete will be improved. 

You will be able to edit and test commands that are not in the main tree etc.  There is no more Bin, but you can open multiple tree windows if you want.

It's going to be good...

I've got lots of other stuff I want to do but I don't want to say anything until I decide what I want to spend time on next. 

[Kalle]

James, the Wiiki for VoxWav looks beautiful. I like the blue color