Author Topic: TCP error  (Read 4947 times)

0 Members and 1 Guest are viewing this topic.

litfoo

  • Jr. Member
  • **
  • Posts: 10
  • Karma: 0
    • View Profile
TCP error
« on: January 07, 2014, 06:29:35 PM »

Hi guys,

Was wondering if anyone could share some light.

When pressing and holding button on my phone, I get a pop-up saying ' TCP Error - Could not establish connection to 192.168.1.xx:33339 failed to connect to /192.168.1.xx(port 33339) after 6000ms

Am running VoxWav Free v 2.1 on a Nexus 5 smartphone running Android Kit v 4.4.2

VoxCommando is running on same network and can the IP/Host can be seen in the VoxWav app when clicking on the radio tower icon

TCP Plugin settings have been set under 'Defaults for Set Single' with my IP address of machine running VC and the port no. 33339

In VC History tab, I can see the wireless symbol and ' Event&&AV.Mic.On' which I assume means they are connected.

Not sure why I am getting these TCP errors though

Any advice appreciated

litfoo

jitterjames

  • Administrator
  • Hero Member
  • *****
  • Posts: 7714
  • Karma: 116
    • View Profile
    • VoxCommando
Re: TCP error
« Reply #1 on: January 07, 2014, 06:33:17 PM »
Hi litfoo

Did you follow the installation instructions from this link?  http://voxwav.wikispaces.com/Installation

In particular, did you enable the tcpmic plugin?

Quote
In VC History tab, I can see the wireless symbol and ' Event&&AV.Mic.On' which I assume means they are connected.
Actually, that just means that UDP messages are getting from VoxWav to VC, not that the TCP connection for audio is working.

litfoo

  • Jr. Member
  • **
  • Posts: 10
  • Karma: 0
    • View Profile
Re: TCP error
« Reply #2 on: January 08, 2014, 05:03:21 AM »
Hi James,

Yes, followed those wiki instructions and enabled/installed the tpmic plugin

It is showing under my 'Active plugins' under the Plugins tab within VC

1 note - in the Wiki it states "You do not need to adjust any settings to get the plugin to connect and work"

I remember I manually added the  IP address of machine running VC and the port no. 33339 to the  'Defaults for Set Single'  - I did this because I recall the default details appeared incorrect.

And my 'Simple Web Sever' is not enabled/unticked

Thanks

litfoo


Kalle

  • $upporter
  • Hero Member
  • *****
  • Posts: 2320
  • Karma: 47
    • View Profile
Re: TCP error
« Reply #3 on: January 08, 2014, 06:26:12 AM »
Hi litfoo, did it work now?

Check the send Port settings in VoxWav (default: 33339), check the Listen-Port in TcpMic plugin settings (default: 33339). Make sure that VoxWav is connected to the IP of your VC machine.
If it works, you can play a bit with the "adjust volume (%)" settings in the TcpMic (in my case 20-25% works at best with all my android devices).

Kalle
***********  get excited and make things  **********

jitterjames

  • Administrator
  • Hero Member
  • *****
  • Posts: 7714
  • Karma: 116
    • View Profile
    • VoxCommando
Re: TCP error
« Reply #4 on: January 08, 2014, 09:01:46 AM »
Hi James,

Yes, followed those wiki instructions and enabled/installed the tpmic plugin

It is showing under my 'Active plugins' under the Plugins tab within VC

1 note - in the Wiki it states "You do not need to adjust any settings to get the plugin to connect and work"

I remember I manually added the  IP address of machine running VC and the port no. 33339 to the  'Defaults for Set Single'  - I did this because I recall the default details appeared incorrect.

And my 'Simple Web Sever' is not enabled/unticked

WRONG PLUGIN!

You need to enable the TcpMic plugin not the TCP plugin.

http://voxcommando.com/mediawiki/index.php?title=Plugin_TcpMic

litfoo

  • Jr. Member
  • **
  • Posts: 10
  • Karma: 0
    • View Profile
Re: TCP error
« Reply #5 on: January 08, 2014, 10:04:27 AM »
 :bonk  :bonk

shocker on my front

will install TcpMic and try this evening

Thanks James.

litfoo

  • Jr. Member
  • **
  • Posts: 10
  • Karma: 0
    • View Profile
Re: TCP error
« Reply #6 on: January 08, 2014, 06:31:27 PM »

OK - so have installed TcpMic plugin now and it is starting to work.

First impressions were

- extreme lagtime to accept and process commands
- a fairly low level % accuracy for command acceptance

tried with pressing button down and also with the tilt

Any advice as how to improve the points above?

cheers

litfoo


Kalle

  • $upporter
  • Hero Member
  • *****
  • Posts: 2320
  • Karma: 47
    • View Profile
Re: TCP error
« Reply #7 on: January 08, 2014, 06:54:38 PM »
Did you read my post above?
Check the TcpMic setting - you can adjust the volume to 20 or 25% for first and enable the wavform.
Take care that the waveform after a command looks like (a bit more or less) the pic which I attached. Take also a look in the VoxWav settings and you can choose a other mic source.

http://voxwav.wikispaces.com/Other+Settings
***********  get excited and make things  **********

jitterjames

  • Administrator
  • Hero Member
  • *****
  • Posts: 7714
  • Karma: 116
    • View Profile
    • VoxCommando
Re: TCP error
« Reply #8 on: January 08, 2014, 07:25:28 PM »
It is not going to do anything until you let go of the button, (or lower the phone if using tilt).

Hold the phone at least a few inches from your mouth.

Also check which mic source you have selected in VoxWav settings.  Try with "VOICE_RECOGNITION" first.  Adjust level in TcpMic settings if necessary, as Kalle suggests.

If that doesn't work well then try with "MIC", or other mic sources.

It is possible you just have a really crappy microphone on your phone, but most likely it is a settings or method of use problem.

On my tablet and on my wife's super cheap phone, I get virtually instant recognition when I let go of the speak button.  Neither works well in a noisy environment though since they have no noise cancelling on them.

litfoo

  • Jr. Member
  • **
  • Posts: 10
  • Karma: 0
    • View Profile
Re: TCP error
« Reply #9 on: January 10, 2014, 09:53:50 AM »

Thanks for the advise Kalle and James

I managed to get some time to test and it seems to be working much better with the suggestions you have made

Volume currently set to 25% and source as VOICE_RECOGNITION

am awaiting a new HTPC that I am going to install Openelec/XBMC on - will do some more testing then

thanks for the help to date.