Title: VoxWav 1.4
Post by: jitterjames on August 08, 2012, 10:45:50 PM
Post by: jitterjames on August 08, 2012, 10:45:50 PM
1.4 attached. More info tomorrow...
note: volume buttons are shown in options, but don't work yet, sorry.
Edit: attachment removed, get the app on the Google Play Store:
note: volume buttons are shown in options, but don't work yet, sorry.
Edit: attachment removed, get the app on the Google Play Store:
Title: Re: VoxWav 1.4
Post by: jitterjames on August 09, 2012, 08:17:45 AM
Post by: jitterjames on August 09, 2012, 08:17:45 AM
If you want to use the tilt feature with the screen off, you may be able to depending on your device. On my tablet with 4.0.3 it works and it uses very little battery.
Go into settings / application settings and enable "keep alive when screen off". On the main screen enable "tilt" and "Bkg Exec".
The app must be in focus. Turn the screen off and it should continue to work using tilt. On my tab I also need to set wifi to "Always on" in android device settings.
Please report if it works for you or not, and what device you have.
On my wife's phone with 2.2 it does not work at all.
Go into settings / application settings and enable "keep alive when screen off". On the main screen enable "tilt" and "Bkg Exec".
The app must be in focus. Turn the screen off and it should continue to work using tilt. On my tab I also need to set wifi to "Always on" in android device settings.
Please report if it works for you or not, and what device you have.
On my wife's phone with 2.2 it does not work at all.
Title: Re: VoxWav 1.4
Post by: Kalle on August 09, 2012, 08:25:09 AM
Post by: Kalle on August 09, 2012, 08:25:09 AM
On "Galaxy S2" it works (android 4.03)
Title: Re: VoxWav 1.4
Post by: ajith on August 10, 2012, 11:11:25 AM
Post by: ajith on August 10, 2012, 11:11:25 AM
Quote from: Kalle on August 09, 2012, 08:25:09 AM
On "Galaxy S2" it works (android 4.03)
I confirm. Everything works on my Galaxy S2 as well (running Android 4.1.1 'Resurrection Remix JB 3.0.1' ).
Also tested on my wife's Google Nexus One (running Cyanogenmod 7). Everything worked there too :)
Title: Re: VoxWav 1.4
Post by: jitterjames on August 10, 2012, 02:05:21 PM
Post by: jitterjames on August 10, 2012, 02:05:21 PM
Cool...
So, does anyone want to offer any observations on the use of the app when the screen is off? Does it use noticeably more battery than when the app is not running, and your screen is off? Does it continue to work, even if you leave your Android idle for a long period of time (for example: about 1 hour) - can you just pick it up, tilt it, and give the command and it works?
This is pretty exciting. The ultimate wifi microphone!
So, does anyone want to offer any observations on the use of the app when the screen is off? Does it use noticeably more battery than when the app is not running, and your screen is off? Does it continue to work, even if you leave your Android idle for a long period of time (for example: about 1 hour) - can you just pick it up, tilt it, and give the command and it works?
This is pretty exciting. The ultimate wifi microphone!
Title: Re: VoxWav 1.4
Post by: Kalle on August 10, 2012, 02:18:06 PM
Post by: Kalle on August 10, 2012, 02:18:06 PM
Quote from: jitterjames on August 10, 2012, 02:05:21 PMYep, it works after a 1 hourwith screen off :)
Cool...
So, does anyone want to offer any observations on the use of the app when the screen is off? Does it use noticeably more battery than when the app is not running, and your screen is off? Does it continue to work, even if you leave your Android idle for a long period of time (for example: about 1 hour) - can you just pick it up, tilt it, and give the command and it works?
This is pretty exciting. The ultimate wifi microphone!
Use 2-3% battery after a hour :clap
And yes, it is a ULTIMATE WiFi-Mic ::bow
Kalle
Title: Re: VoxWav 1.4
Post by: jitterjames on August 10, 2012, 02:24:29 PM
Post by: jitterjames on August 10, 2012, 02:24:29 PM
Quote from: Kalle on August 10, 2012, 02:18:06 PM
Yep, it works after a 1 hourwith screen off :)
Use 2-3% battery after a hour :clap
Thanks Kalle. 2-3% is pretty good. For the purpose of comparison, what kind of battery use would you see after one hour when VoxWav was not running?
On my tablet I use up about 1%-2% per hour whether VoxWav is running or not. I'm sure there is a difference but it is small. Note that I've only done a single 1 hour test. I need to do more testing. I will probably try it overnight soon.
Title: Re: VoxWav 1.4
Post by: Kalle on August 11, 2012, 07:48:45 AM
Post by: Kalle on August 11, 2012, 07:48:45 AM
Quote from: jitterjames on August 10, 2012, 02:24:29 PMVoxWav 1.4 battery consumption test with "Samsung Galaxy S2"
Thanks Kalle. 2-3% is pretty good. For the purpose of comparison, what kind of battery use would you see after one hour when VoxWav was not running?
On my tablet I use up about 1%-2% per hour whether VoxWav is running or not. I'm sure there is a difference but it is small. Note that I've only done a single 1 hour test. I need to do more testing. I will probably try it overnight soon.
WiFi always on, no special tasks in background:
1. Galaxy S2 (Android 4.03) with running VoxWav after 7 hours = 16% battery consumption.
2. Galaxy S2 (Android 4.03) without running VoxWav after 7 hours = 5 % battery consumption.
Conclusion for my Galaxy S2 configuration: VoxWav 1.4 is a perfect WiFi-Mic and the average battery consumption increases by 1.5% per hour - this is a very good value.
Kalle
Title: Re: VoxWav 1.4
Post by: ajith on August 11, 2012, 10:03:23 AM
Post by: ajith on August 11, 2012, 10:03:23 AM
James,
In VC, if the confidence level falls just short of the required value, the command appears in orange at the top of VC. This also appears as a green text label in VW. Could you make it orange also in VW (if confidence is low), and, more importantly, make it tappable, to confirm that command? It will be very useful, as, many a time I find the command is recognized correctly, only to fall a little short in confidence level. VW showing it in green, yet VC not executing it, is all the more frustrating :bonk
In VC, if the confidence level falls just short of the required value, the command appears in orange at the top of VC. This also appears as a green text label in VW. Could you make it orange also in VW (if confidence is low), and, more importantly, make it tappable, to confirm that command? It will be very useful, as, many a time I find the command is recognized correctly, only to fall a little short in confidence level. VW showing it in green, yet VC not executing it, is all the more frustrating :bonk
Title: Re: VoxWav 1.4
Post by: jitterjames on August 11, 2012, 04:19:09 PM
Post by: jitterjames on August 11, 2012, 04:19:09 PM
Yes of course. All in good time my friend :)
I also plan to add popup yes/no buttons for commands that require confirmation. And maybe also a clickable list when there are alternates.
edit: all of these things will require changes to both VC and VW and introduce new complications in terms of potentially needing to add new user preferences.
I also plan to add popup yes/no buttons for commands that require confirmation. And maybe also a clickable list when there are alternates.
edit: all of these things will require changes to both VC and VW and introduce new complications in terms of potentially needing to add new user preferences.
Title: Re: VoxWav 1.4
Post by: ajith on August 12, 2012, 12:14:03 AM
Post by: ajith on August 12, 2012, 12:14:03 AM
Understood :)
Title: Re: VoxWav 1.4
Post by: Siutsch on August 14, 2012, 12:32:11 PM
Post by: Siutsch on August 14, 2012, 12:32:11 PM
Hi,
I have a problem using VoxWav 1.4.
I only can use VoxWav 2 or 3 times, the last command will be processed only after ca. 15 seconds.
During this time VoxCommando (0960b) hangs (has no respond, the Historie is empty) and the green command in VoxWav does not appear if VoxCommando is OK again, after that the command is executed, however, when he was recognized correctly.
After that I can use VoxWav 2 or 3 times again and same thing happened.
Any ideas?
Siutsch.
I have a problem using VoxWav 1.4.
I only can use VoxWav 2 or 3 times, the last command will be processed only after ca. 15 seconds.
During this time VoxCommando (0960b) hangs (has no respond, the Historie is empty) and the green command in VoxWav does not appear if VoxCommando is OK again, after that the command is executed, however, when he was recognized correctly.
After that I can use VoxWav 2 or 3 times again and same thing happened.
Any ideas?
Siutsch.
Title: Re: VoxWav 1.4
Post by: Kalle on August 14, 2012, 01:03:08 PM
Post by: Kalle on August 14, 2012, 01:03:08 PM
Quote from: Siutsch on August 14, 2012, 12:32:11 PMHi Marc, kontrolliere mal dein "wavwatch" Ordner, ob dort nicht noch alte ungelöschte Dateien sind - falls ja - lösche diese per Hand und versuch es nochmal. Du kannst den "wavwatch" Ordner ruhig im Fordergrund behalten und mal beobachten was dort passiert.
Hi,
I have a problem using VoxWav 1.4.
I only can use VoxWav 2 or 3 times, the last command will be processed only after ca. 15 seconds.
During this time VoxCommando (0960b) hangs (has no respond, the Historie is empty) and the green command in VoxWav does not appear if VoxCommando is OK again, after that the command is executed, however, when he was recognized correctly.
After that I can use VoxWav 2 or 3 times again and same thing happened.
Any ideas?
Siutsch.
Gruß Kalle
Title: Re: VoxWav 1.4
Post by: Siutsch on August 14, 2012, 01:37:35 PM
Post by: Siutsch on August 14, 2012, 01:37:35 PM
Hi Kalle,
sind keine alten Dateien mehr drin.
Und den Ordner hab ich während der Tests nat. im Auge behalten.
Das ganze klappt immer wenige Male normal und dann hängt VoxCommando kurz (Keine Rückmeldung oben in der Leiste).
Nach einigen Sekunden geht's dann aber weiter, die Wav-Datei wird verarbeitet, die grüne Rückmeldung kommt in VoxWav an
und die Wav-Datei ist verschwunden.
Der PC hat während dieser Zeit nix großartiges zu tun, der TaskManager zeigt auch nichts auffälliges an.
sind keine alten Dateien mehr drin.
Und den Ordner hab ich während der Tests nat. im Auge behalten.
Das ganze klappt immer wenige Male normal und dann hängt VoxCommando kurz (Keine Rückmeldung oben in der Leiste).
Nach einigen Sekunden geht's dann aber weiter, die Wav-Datei wird verarbeitet, die grüne Rückmeldung kommt in VoxWav an
und die Wav-Datei ist verschwunden.
Der PC hat während dieser Zeit nix großartiges zu tun, der TaskManager zeigt auch nichts auffälliges an.
Title: Re: VoxWav 1.4
Post by: Kalle on August 14, 2012, 01:44:34 PM
Post by: Kalle on August 14, 2012, 01:44:34 PM
Quote from: Siutsch on August 14, 2012, 01:37:35 PMwelche Android Version benutzt Du?
Hi Kalle,
sind keine alten Dateien mehr drin.
Und den Ordner hab ich während der Tests nat. im Auge behalten.
Das ganze klappt immer wenige Male normal und dann hängt VoxCommando kurz (Keine Rückmeldung oben in der Leiste).
Nach einigen Sekunden geht's dann aber weiter, die Wav-Datei wird verarbeitet, die grüne Rückmeldung kommt in VoxWav an
und die Wav-Datei ist verschwunden.
Der PC hat während dieser Zeit nix großartiges zu tun, der TaskManager zeigt auch nichts auffälliges an.
Title: Re: VoxWav 1.4
Post by: Siutsch on August 14, 2012, 01:53:42 PM
Post by: Siutsch on August 14, 2012, 01:53:42 PM
Galaxy S2 mit offiziellem 4.0.3
Noch mal weiter getestet.
Wenn VoxCommando hängt, dann kann ich mit VoxWav währenddessen weitere Eingaben machen,
die werden dann auch immer sofort in den Zielordner geschrieben, das klappt also soweit fehlerfrei.
Ich denke also eher, dass das Problem (bei mir) irgendwie an VoxCommando selbst liegt, das fast jedes 2./3. Mal
ne Denkpause braucht.
Die während dieser Zeit erstellten Wav-Dateien werden dann weder danach verarbeitet, noch gelöscht.
Auch wenn diese weiterhin vorhanden sind, wird eine weitere Eingabe von VoxWav für die dann neue
Wav-Datei durchgeführt, die vorhandenen bleiben unverändert im Ordner.
Ob ich also lösche oder nicht, beeinflusst scheinbar nicht die weitere Arbeit.
Irgendwie komisch ...
Noch mal weiter getestet.
Wenn VoxCommando hängt, dann kann ich mit VoxWav währenddessen weitere Eingaben machen,
die werden dann auch immer sofort in den Zielordner geschrieben, das klappt also soweit fehlerfrei.
Ich denke also eher, dass das Problem (bei mir) irgendwie an VoxCommando selbst liegt, das fast jedes 2./3. Mal
ne Denkpause braucht.
Die während dieser Zeit erstellten Wav-Dateien werden dann weder danach verarbeitet, noch gelöscht.
Auch wenn diese weiterhin vorhanden sind, wird eine weitere Eingabe von VoxWav für die dann neue
Wav-Datei durchgeführt, die vorhandenen bleiben unverändert im Ordner.
Ob ich also lösche oder nicht, beeinflusst scheinbar nicht die weitere Arbeit.
Irgendwie komisch ...
Title: Re: VoxWav 1.4
Post by: Kalle on August 14, 2012, 01:59:46 PM
Post by: Kalle on August 14, 2012, 01:59:46 PM
Quote from: Siutsch on August 14, 2012, 01:53:42 PMTritt das immer bei den gleichen Befehlen auf oder willkürlich? Versuch es doch mal mit einer frischen standard VC installation (basic) in einem neuen Ordner. Ich habe das gleiche Handy wie du und selbst auf meinem HTPC mit Intel Atom läuft es ohne Probleme ::hmm
Galaxy S2 mit offiziellem 4.0.3
Noch mal weiter getestet.
Wenn VoxCommando hängt, dann kann ich mit VoxWav währenddessen weitere Eingaben machen,
die werden dann auch immer sofort in den Zielordner geschrieben, das klappt also soweit fehlerfrei.
Ich denke also eher, dass das Problem (bei mir) irgendwie an VoxCommando selbst liegt, das fast jedes 2./3. Mal
ne Denkpause braucht.
Die während dieser Zeit erstellten Wav-Dateien werden dann weder danach verarbeitet, noch gelöscht.
Auch wenn diese weiterhin vorhanden sind, wird eine weitere Eingabe von VoxWav für die dann neue
Wav-Datei durchgeführt, die vorhandenen bleiben unverändert im Ordner.
Ob ich also lösche oder nicht, beeinflusst scheinbar nicht die weitere Arbeit.
Irgendwie komisch ...
Title: Re: VoxWav 1.4
Post by: Siutsch on August 14, 2012, 02:03:12 PM
Post by: Siutsch on August 14, 2012, 02:03:12 PM
Befehle sind egal, passiert nun auch fast jedes mal, hängt immer einige Sekunden.
Hab noch mal den Freigabeordner gewechselt, diesmal im Hauptverzeichnis (C:\VoxWav), aber
hat auch nichts gebracht, da VoxWav ja soweit seine Arbeit macht.
Läuft ebenfalls auf einem Intel Atom (Acer Revo 3610 für XBMC usw.), VoxCommando generell
läuft auch soweit.
Ich mach gelegentlich noch mal ne Neu-Inst. von VoxCommando, die Befehle kann ich ja sichern,
mal schauen, was da los ist.
Vielen Dank,
Marc.
Hab noch mal den Freigabeordner gewechselt, diesmal im Hauptverzeichnis (C:\VoxWav), aber
hat auch nichts gebracht, da VoxWav ja soweit seine Arbeit macht.
Läuft ebenfalls auf einem Intel Atom (Acer Revo 3610 für XBMC usw.), VoxCommando generell
läuft auch soweit.
Ich mach gelegentlich noch mal ne Neu-Inst. von VoxCommando, die Befehle kann ich ja sichern,
mal schauen, was da los ist.
Vielen Dank,
Marc.
Title: Re: VoxWav 1.4
Post by: Siutsch on August 14, 2012, 03:14:59 PM
Post by: Siutsch on August 14, 2012, 03:14:59 PM
So, hab eben VoxCommando gelöscht und noch mal mit der aktuellsten VC Setup 0960b.exe neu installiert.
Danach, noch vor dem 1. Start, die beiden Dateien options.xml und voicecommands.xml wieder zurückgesichert.
Nach Start von VoxCommando dann mal die Protokollierung aktiviert und mal 4 Befehle getestet, beim 4. hing VC dann wieder einige Sekunden, die Wave-Datei wurde aber wieder gelöscht, nachdem sich VC wieder gefangen hatte, der Freigabe-Ordner war also wieder leer.
Hier der relevante Inhalt der Log-Datei, interessant ist der rot markierte Teil, zwischen "wav rename detected ..." und "trying to open: ..." ist hier ein Zeitspanne von über 30 Sekunden, statt bei den anderen 3 erfolgreichen Versuchen nur 1 Sekunde.
Irgendwas hängt da also scheinbar bei VC, im Taskmanager ist währenddessen absolut nichts auffälliges zu erkennen, die Auslastung bleibt unverändert und auch sonst verhält sich der HTPC normal:
14.08.2012 20:02:31 424 focused: VoxCommando
14.08.2012 20:02:43 928 received udp command:Event&&AV.Resuming
14.08.2012 20:02:45 839 received udp command:Event&&AV.Mic.On
14.08.2012 20:02:48 23 received udp command:Event&&AV.Mic.Off
14.08.2012 20:02:48 210 wav rename detected: C:\VoxWav\android8_4_42.wav
14.08.2012 20:02:48 701 trying to open: C:\VoxWav\android8_4_42.wav
14.08.2012 20:02:49 297 semanticID: 8
14.08.2012 20:02:49 299 kvp: command | 8
14.08.2012 20:02:49 309 semanticID: 8
14.08.2012 20:02:49 312 kvp: command | 8
14.08.2012 20:02:49 315 alternate:lauter
14.08.2012 20:02:49 454 doCommand:Volumeup
14.08.2012 20:02:49 670 action repeat set to: 1
14.08.2012 20:02:49 675 Action: EventGhost - Volumeup
14.08.2012 20:02:49 681 Broadcast:Volumeup
14.08.2012 20:02:49 752 trying to release file
14.08.2012 20:02:51 40 trying to delete file:C:\VoxWav\android8_4_42.wav
14.08.2012 20:02:55 513 received udp command:Event&&AV.Mic.On
14.08.2012 20:02:57 769 semanticID: 9
14.08.2012 20:02:57 772 kvp: command | 9
14.08.2012 20:02:57 776 confidence too low
54,5% - leiser
14.08.2012 20:02:57 782 received udp command:Event&&AV.Mic.Off
14.08.2012 20:02:57 786 wav rename detected: C:\VoxWav\android8_4_51.wav
14.08.2012 20:02:58 201 trying to open: C:\VoxWav\android8_4_51.wav
14.08.2012 20:02:58 412 semanticID: 9
14.08.2012 20:02:58 414 kvp: command | 9
14.08.2012 20:02:58 420 semanticID: 9
14.08.2012 20:02:58 422 kvp: command | 9
14.08.2012 20:02:58 425 alternate:leiser
14.08.2012 20:02:58 540 doCommand:Volumedown
14.08.2012 20:02:58 544 action repeat set to: 1
14.08.2012 20:02:58 548 Action: EventGhost - Volumedown
14.08.2012 20:02:58 551 Broadcast:Volumedown
14.08.2012 20:02:58 746 trying to release file
14.08.2012 20:03:00 20 trying to delete file:C:\VoxWav\android8_4_51.wav
14.08.2012 20:03:03 412 received udp command:Event&&AV.Mic.On
14.08.2012 20:03:05 516 received udp command:Event&&AV.Mic.Off
14.08.2012 20:03:05 724 wav rename detected: C:\VoxWav\android8_4_59.wav
14.08.2012 20:03:06 190 trying to open: C:\VoxWav\android8_4_59.wav
14.08.2012 20:03:06 732 semanticID: 8
14.08.2012 20:03:06 735 kvp: command | 8
14.08.2012 20:03:06 745 semanticID: 8
14.08.2012 20:03:06 749 kvp: command | 8
14.08.2012 20:03:06 752 alternate:lauter
14.08.2012 20:03:06 920 doCommand:Volumeup
14.08.2012 20:03:06 923 action repeat set to: 1
14.08.2012 20:03:06 926 Action: EventGhost - Volumeup
14.08.2012 20:03:06 929 Broadcast:Volumeup
14.08.2012 20:03:07 9 trying to release file
14.08.2012 20:03:08 243 trying to delete file:C:\VoxWav\android8_4_59.wav
14.08.2012 20:03:09 997 received udp command:Event&&AV.Mic.On
14.08.2012 20:03:12 424 received udp command:Event&&AV.Mic.Off
14.08.2012 20:03:12 647 wav rename detected: C:\VoxWav\android8_5_6.wav
14.08.2012 20:03:46 192 trying to open: C:\VoxWav\android8_5_6.wav
14.08.2012 20:03:46 342 semanticID: 9
14.08.2012 20:03:46 345 kvp: command | 9
14.08.2012 20:03:46 352 semanticID: 9
14.08.2012 20:03:46 355 kvp: command | 9
14.08.2012 20:03:46 358 alternate:leiser
14.08.2012 20:03:46 492 doCommand:Volumedown
14.08.2012 20:03:46 494 action repeat set to: 1
14.08.2012 20:03:46 497 Action: EventGhost - Volumedown
14.08.2012 20:03:46 500 Broadcast:Volumedown
14.08.2012 20:03:46 571 trying to release file
14.08.2012 20:03:46 885 received udp command:Event&&AV.Resuming
14.08.2012 20:03:46 891 received udp command:Event&&AV.Resuming
14.08.2012 20:03:47 885 trying to delete file:C:\VoxWav\android8_5_6.wav
Ich bin ratlos ...
Siutsch.
Danach, noch vor dem 1. Start, die beiden Dateien options.xml und voicecommands.xml wieder zurückgesichert.
Nach Start von VoxCommando dann mal die Protokollierung aktiviert und mal 4 Befehle getestet, beim 4. hing VC dann wieder einige Sekunden, die Wave-Datei wurde aber wieder gelöscht, nachdem sich VC wieder gefangen hatte, der Freigabe-Ordner war also wieder leer.
Hier der relevante Inhalt der Log-Datei, interessant ist der rot markierte Teil, zwischen "wav rename detected ..." und "trying to open: ..." ist hier ein Zeitspanne von über 30 Sekunden, statt bei den anderen 3 erfolgreichen Versuchen nur 1 Sekunde.
Irgendwas hängt da also scheinbar bei VC, im Taskmanager ist währenddessen absolut nichts auffälliges zu erkennen, die Auslastung bleibt unverändert und auch sonst verhält sich der HTPC normal:
14.08.2012 20:02:31 424 focused: VoxCommando
14.08.2012 20:02:43 928 received udp command:Event&&AV.Resuming
14.08.2012 20:02:45 839 received udp command:Event&&AV.Mic.On
14.08.2012 20:02:48 23 received udp command:Event&&AV.Mic.Off
14.08.2012 20:02:48 210 wav rename detected: C:\VoxWav\android8_4_42.wav
14.08.2012 20:02:48 701 trying to open: C:\VoxWav\android8_4_42.wav
14.08.2012 20:02:49 297 semanticID: 8
14.08.2012 20:02:49 299 kvp: command | 8
14.08.2012 20:02:49 309 semanticID: 8
14.08.2012 20:02:49 312 kvp: command | 8
14.08.2012 20:02:49 315 alternate:lauter
14.08.2012 20:02:49 454 doCommand:Volumeup
14.08.2012 20:02:49 670 action repeat set to: 1
14.08.2012 20:02:49 675 Action: EventGhost - Volumeup
14.08.2012 20:02:49 681 Broadcast:Volumeup
14.08.2012 20:02:49 752 trying to release file
14.08.2012 20:02:51 40 trying to delete file:C:\VoxWav\android8_4_42.wav
14.08.2012 20:02:55 513 received udp command:Event&&AV.Mic.On
14.08.2012 20:02:57 769 semanticID: 9
14.08.2012 20:02:57 772 kvp: command | 9
14.08.2012 20:02:57 776 confidence too low
54,5% - leiser
14.08.2012 20:02:57 782 received udp command:Event&&AV.Mic.Off
14.08.2012 20:02:57 786 wav rename detected: C:\VoxWav\android8_4_51.wav
14.08.2012 20:02:58 201 trying to open: C:\VoxWav\android8_4_51.wav
14.08.2012 20:02:58 412 semanticID: 9
14.08.2012 20:02:58 414 kvp: command | 9
14.08.2012 20:02:58 420 semanticID: 9
14.08.2012 20:02:58 422 kvp: command | 9
14.08.2012 20:02:58 425 alternate:leiser
14.08.2012 20:02:58 540 doCommand:Volumedown
14.08.2012 20:02:58 544 action repeat set to: 1
14.08.2012 20:02:58 548 Action: EventGhost - Volumedown
14.08.2012 20:02:58 551 Broadcast:Volumedown
14.08.2012 20:02:58 746 trying to release file
14.08.2012 20:03:00 20 trying to delete file:C:\VoxWav\android8_4_51.wav
14.08.2012 20:03:03 412 received udp command:Event&&AV.Mic.On
14.08.2012 20:03:05 516 received udp command:Event&&AV.Mic.Off
14.08.2012 20:03:05 724 wav rename detected: C:\VoxWav\android8_4_59.wav
14.08.2012 20:03:06 190 trying to open: C:\VoxWav\android8_4_59.wav
14.08.2012 20:03:06 732 semanticID: 8
14.08.2012 20:03:06 735 kvp: command | 8
14.08.2012 20:03:06 745 semanticID: 8
14.08.2012 20:03:06 749 kvp: command | 8
14.08.2012 20:03:06 752 alternate:lauter
14.08.2012 20:03:06 920 doCommand:Volumeup
14.08.2012 20:03:06 923 action repeat set to: 1
14.08.2012 20:03:06 926 Action: EventGhost - Volumeup
14.08.2012 20:03:06 929 Broadcast:Volumeup
14.08.2012 20:03:07 9 trying to release file
14.08.2012 20:03:08 243 trying to delete file:C:\VoxWav\android8_4_59.wav
14.08.2012 20:03:09 997 received udp command:Event&&AV.Mic.On
14.08.2012 20:03:12 424 received udp command:Event&&AV.Mic.Off
14.08.2012 20:03:12 647 wav rename detected: C:\VoxWav\android8_5_6.wav
14.08.2012 20:03:46 192 trying to open: C:\VoxWav\android8_5_6.wav
14.08.2012 20:03:46 342 semanticID: 9
14.08.2012 20:03:46 345 kvp: command | 9
14.08.2012 20:03:46 352 semanticID: 9
14.08.2012 20:03:46 355 kvp: command | 9
14.08.2012 20:03:46 358 alternate:leiser
14.08.2012 20:03:46 492 doCommand:Volumedown
14.08.2012 20:03:46 494 action repeat set to: 1
14.08.2012 20:03:46 497 Action: EventGhost - Volumedown
14.08.2012 20:03:46 500 Broadcast:Volumedown
14.08.2012 20:03:46 571 trying to release file
14.08.2012 20:03:46 885 received udp command:Event&&AV.Resuming
14.08.2012 20:03:46 891 received udp command:Event&&AV.Resuming
14.08.2012 20:03:47 885 trying to delete file:C:\VoxWav\android8_5_6.wav
Ich bin ratlos ...
Siutsch.
Title: Re: VoxWav 1.4
Post by: jitterjames on August 14, 2012, 03:28:25 PM
Post by: jitterjames on August 14, 2012, 03:28:25 PM
Are you sending commands very close together without much time in between? If so, please try this:
- Wait a full 60 seconds after a command finishes executing before saying the next command. Now do you still have the same problem?
Does it make any difference if you set VoxCommando to "OFF" mode when using VoxWav? I want to make sure there is not a conflict between the microphone and the wav reader.
Does it behave the same way if you use tilt or the speak button in VoxWav?
Don't view the voxwav folder in explorer, and make sure no other computers have the folder open.
Try setting the sample rate in VoxWav to 22000
Let us know if any of this makes a difference.
- Wait a full 60 seconds after a command finishes executing before saying the next command. Now do you still have the same problem?
Does it make any difference if you set VoxCommando to "OFF" mode when using VoxWav? I want to make sure there is not a conflict between the microphone and the wav reader.
Does it behave the same way if you use tilt or the speak button in VoxWav?
Don't view the voxwav folder in explorer, and make sure no other computers have the folder open.
Try setting the sample rate in VoxWav to 22000
Let us know if any of this makes a difference.
Title: Re: VoxWav 1.4
Post by: jitterjames on August 14, 2012, 03:32:41 PM
Post by: jitterjames on August 14, 2012, 03:32:41 PM
also, you gave the example of having 3 commands work and then one having a delay.
does this always happen this way, or is it random?
In other words, do you get
3 normal
1 with a delay
3 normal
1 with a delay
etc.
or could the delay happen any time, but it's only about 25% of the time?
does this always happen this way, or is it random?
In other words, do you get
3 normal
1 with a delay
3 normal
1 with a delay
etc.
or could the delay happen any time, but it's only about 25% of the time?
Title: Re: VoxWav 1.4
Post by: Siutsch on August 14, 2012, 04:37:20 PM
Post by: Siutsch on August 14, 2012, 04:37:20 PM
I will try all this.
Thankz for these notes. :D
>Are you sending commands very close together without much time in between?
No, I had not waited so long, but I will try.
>Does it make any difference if you set VoxCommando to "OFF" mode when using VoxWav?
I used VC in standby mode, will try off too.
>Does it behave the same way if you use tilt or the speak button in VoxWav?
I only used speak button. Will try tilt too.
>Don't view the voxwav folder in explorer, and make sure no other computers have the folder open.
OK. I had folder open during tests.
>Try setting the sample rate in VoxWav to 22000
I did. But at first tests I had 44000 too.
>Also, you gave the example of having 3 commands work and then one having a delay.
>Does this always happen this way, or is it random?
It is random. Sometimes it works only one time, during my test it was 3 times.
I'll be in touch as soon as I know more (not today). ::zzz
Thankz,
Siutsch.
Thankz for these notes. :D
>Are you sending commands very close together without much time in between?
No, I had not waited so long, but I will try.
>Does it make any difference if you set VoxCommando to "OFF" mode when using VoxWav?
I used VC in standby mode, will try off too.
>Does it behave the same way if you use tilt or the speak button in VoxWav?
I only used speak button. Will try tilt too.
>Don't view the voxwav folder in explorer, and make sure no other computers have the folder open.
OK. I had folder open during tests.
>Try setting the sample rate in VoxWav to 22000
I did. But at first tests I had 44000 too.
>Also, you gave the example of having 3 commands work and then one having a delay.
>Does this always happen this way, or is it random?
It is random. Sometimes it works only one time, during my test it was 3 times.
I'll be in touch as soon as I know more (not today). ::zzz
Thankz,
Siutsch.
Title: Re: VoxWav 1.4
Post by: Siutsch on August 15, 2012, 02:12:16 PM
Post by: Siutsch on August 15, 2012, 02:12:16 PM
After some testing today, it seems, that my problem has gone away ... :bonk
Whether I send commands slow or as fast as yesterday - it works.
I triedup sure up to 15 commandos successively, no problem.
It also has no effect if I view the voxwav folder in explorer, on a laptop, as well as on the VoxCommando PC simultaneously.
I've nothing changed, the VC PC (my Atom HTPC) was in standby during night (as always), no reboot, no new start of VC.
I'll be watching this in the coming days and hope the problem does not recur.
Sorry! ::confused
Siutsch.
Whether I send commands slow or as fast as yesterday - it works.
I triedup sure up to 15 commandos successively, no problem.
It also has no effect if I view the voxwav folder in explorer, on a laptop, as well as on the VoxCommando PC simultaneously.
I've nothing changed, the VC PC (my Atom HTPC) was in standby during night (as always), no reboot, no new start of VC.
I'll be watching this in the coming days and hope the problem does not recur.
Sorry! ::confused
Siutsch.
Title: Re: VoxWav 1.4
Post by: jitterjames on August 15, 2012, 02:53:13 PM
Post by: jitterjames on August 15, 2012, 02:53:13 PM
it's ok. I'm sure there was a reason for it, and it will probably come back, but hopefully not!
Title: Re: VoxWav 1.4
Post by: jitterjames on August 17, 2012, 06:24:40 PM
Post by: jitterjames on August 17, 2012, 06:24:40 PM
latest version is now 1.6, lots of changes!
http://voxcommando.com/forum/index.php?topic=887.0
http://voxcommando.com/forum/index.php?topic=887.0
Title: Re: VoxWav 1.4
Post by: claymic on December 30, 2012, 03:18:58 PM
Post by: claymic on December 30, 2012, 03:18:58 PM
Ok, my pc died :bonk, i have a backup for VoxCommando, but i have to make the training again, then i will test this version.
Thanks for this great job James.
Clayton
Thanks for this great job James.
Clayton
Title: Re: VoxWav 1.4
Post by: jitterjames on December 30, 2012, 03:46:50 PM
Post by: jitterjames on December 30, 2012, 03:46:50 PM
this is an old post. (August)
Title: Re: VoxWav 1.4
Post by: claymic on December 30, 2012, 09:25:33 PM
Post by: claymic on December 30, 2012, 09:25:33 PM
I post in the wrong place James sorry, i am a little tired :bonk
Title: Re: VoxWav 1.4
Post by: jitterjames on December 31, 2012, 08:51:47 AM
Post by: jitterjames on December 31, 2012, 08:51:47 AM
No worries, I just wanted to help avoid any possible confusion for you, or others reading your post.