Author Topic: Version 0.86 (Read 27599 times)

Kalle · « **Reply #60 on:** December 19, 2010, 03:08:00 PM »

digg it

Kalle

Wanilton · « **Reply #61 on:** December 20, 2010, 05:13:15 AM »

Digg it, too

Diabl0570 · « **Reply #62 on:** December 20, 2010, 03:53:58 PM »

Same here !xD
Digg it

DHHJ · « **Reply #63 on:** December 20, 2010, 04:28:05 PM »

Digg it too and

sitterjames: just donated as well!!

jitterjames · « **Reply #64 on:** December 20, 2010, 04:31:35 PM »

It looks like everyone is in the Christmas spirit

Thanks Everyone.

painy · « **Reply #65 on:** December 20, 2010, 05:22:39 PM »

I tried getting this article updated on lifehacker.com a while back to work with voice control, but I've gotten no respsonse to my email

jitterjames · « **Reply #66 on:** December 29, 2010, 11:10:56 AM »

Derelict discovered a bug in version 0.86. (Thank you for catching it when you did Derelict!

) I have not been able to find the bug and I don't understand where it is coming from. It is possible that one or more files in my dev folder became corrupt somehow. Anyway, I have been forced to go back to code from version 0.85 (which is almost 2 months old) and rebuild my new features from that, piece by piece, and testing along the way to make sure the bug doesn't come back.

This is taking a long time, but I am making good progress so far...

I will release 0.87 soon, but it is possible if I miss something that it will be missing features or fixes that were in 0.86. I will be happy to receive reports on any bugs or missing features.

I just wanted to explain why it is taking so long. Hopefully I will also be able to offer a new feature or two while I am at it.

Also, there is a lot of eggnog here that I need to take care of which requires time and dedication...

jitterjames · « **Reply #67 on:** January 01, 2011, 10:07:58 PM »

Here is version 0.868 (patch your existing installation).

Moving towards version 0.87, there are a few things that I am working on.

One of them is the ability to rebuild the command grammars in the background whenever commands are changed or payloadXML files are updated. The rebuild button at the top is a test. It works, in that it does rebuild the grammars and allows you to restart quickly. It is not finished yet. More tools are needed to support it and make it useful, like the option to automatically restart after rebuilding.

Another thing I am working on (this is new) is a much more detailed command history. I am working on consistency so that all commands will return some kind of useful information and make it clear if they succeeded. If there is a result returned from a query (i.e. getArtist, or getVolume) or an error message, it will be possible to see it in the history by rolling over the action. I am also using icons to show different types of events.

Here is what I have so far for icons:
- blue circle with 'i' : system information (i.e. what language is being used for speech)
- a megaphone : speech was interpreted successfully as a command
- a question mark : speech was interpreted successfully as a command, but confidence was too low
- green gear: an action was executed (corresponds to actions in the command builder)
- radio signals : a udp (network broadcast) command has been received from tellvox (or eventghost, or some other program)

if an action (green gear) generates an error, it will be highlighted with an orange background.

I am also working on multiple interface languages for the main page, the options pages, and the GenXML page. This version has been mostly translated for PT-BR thanks to Wanilton. If anyone wants to contribute for other languages please let me know. Wanilton sent me screen captures of the different pages with the Portuguese-Brazil text on top. This was a good way to show the translations, but it was difficult for me to use because I could not cut and paste the text. If I am required to re-enter the text it is a problem for me because I don't normally use accents. So if you send translations, please provide a format that I can cut and paste from.

I am not translating the tree editor, group properties, and command builder pages yet. The language that you will see will depend on the display language used by Windows. It does not need to be the same language as the speech language that you select on the options page. This way you can use the English speech recognition engine (good for English media) but still see an interface in your preferred language.

Happy New Year Everyone. Thanks for all your support so far. I hope that 2011 will bring more good things to VoxCommando!

Attachments removed... there is a newer version

Kalle · « **Reply #68 on:** January 02, 2011, 05:11:42 PM »

Hi James,

here is it, the "interface language" translate in german for Main-, Option and so on Page

Greetings Kalle

jitterjames · « **Reply #69 on:** January 02, 2011, 06:25:32 PM »

Perfect Kalle, now I have no excuse not to do it!

Kalle · « **Reply #70 on:** January 02, 2011, 07:23:47 PM »

Quote from: jitterjames on January 02, 2011, 06:25:32 PM

Perfect Kalle, now I have no excuse not to do it!

That's right

Kalle

Kalle · « **Reply #71 on:** January 03, 2011, 06:23:55 PM »

Quote from: jitterjames on January 01, 2011, 10:07:58 PM

Here is version 0.868 (patch your existing installation).

Moving towards version 0.87, there are a few things that I am working on.

One of them is the ability to rebuild the command grammars in the background whenever commands are changed or payloadXML files are updated. The rebuild button at the top is a test. It works, in that it does rebuild the grammars and allows you to restart quickly. It is not finished yet. More tools are needed to support it and make it useful, like the option to automatically restart after rebuilding.

Another thing I am working on (this is new) is a much more detailed command history. I am working on consistency so that all commands will return some kind of useful information and make it clear if they succeeded. If there is a result returned from a query (i.e. getArtist, or getVolume) or an error message, it will be possible to see it in the history by rolling over the action. I am also using icons to show different types of events.

Here is what I have so far for icons:
- blue circle with 'i' : system information (i.e. what language is being used for speech)
- a megaphone : speech was interpreted successfully as a command
- a question mark : speech was interpreted successfully as a command, but confidence was too low
- green gear: an action was executed (corresponds to actions in the command builder)
- radio signals : a udp (network broadcast) command has been received from tellvox (or eventghost, or some other program)

if an action (green gear) generates an error, it will be highlighted with an orange background.

I am also working on multiple interface languages for the main page, the options pages, and the GenXML page. This version has been mostly translated for PT-BR thanks to Wanilton. If anyone wants to contribute for other languages please let me know. Wanilton sent me screen captures of the different pages with the Portuguese-Brazil text on top. This was a good way to show the translations, but it was difficult for me to use because I could not cut and paste the text. If I am required to re-enter the text it is a problem for me because I don't normally use accents. So if you send translations, please provide a format that I can cut and paste from.

I am not translating the tree editor, group properties, and command builder pages yet. The language that you will see will depend on the display language used by Windows. It does not need to be the same language as the speech language that you select on the options page. This way you can use the English speech recognition engine (good for English media) but still see an interface in your preferred language.

Happy New Year Everyone. Thanks for all your support so far. I hope that 2011 will bring more good things to VoxCommando!

Hi James,
today I had a little time to test the new version (0.868), and it works perfect, no problems. In version 0860 I had the problem, VC performs in the off-mode commands. In 0868 everything works fine and the small icon in the history are great. Do you have the Kinect?

Kalle

jitterjames · « **Reply #72 on:** January 03, 2011, 07:02:52 PM »

I'm glad to hear it is working well. I'm happy about the new History concept, though it still needs work.

Yes I've got the Kinect and I have done some initial testing. See my post here:
http://voxcommando.com/forum/index.php?topic=355.msg1861#msg1861

I will post a new Version of VC with the german interface elements tomorrow if I can.

I need to go feed myself now! Cheers.

Wanilton · « **Reply #73 on:** January 03, 2011, 07:41:03 PM »

Well my impressions were also good in using this new version, the history helps a lot, on the other hand if I leave the voxcommando superimposed on XBMC to be able to track the history and give a scroll command for example, instead of the scroll work on XBMC, it vox works in history (the scroll), where he sometimes gets the focus, what can I do in these cases, to avoid this kind of situation?
One last question, any release date for the translated version of PT-BR?

jitterjames · « **Reply #74 on:** January 03, 2011, 10:27:12 PM »

the scroll commands use keyboard emulation of the arrow keys so it will get sent to whatever program has focus. There isn't really anything you can do about that. The history window is not really intended to be used all the time, just when you are "debugging" and getting things set up or working on new commands.

If you really want to you can change the scroll commands to use xbmc commands "up" "down" etc. using actions. You can do a command xbmc.send action(1) etc., but it will be much slower I think. I dont' know how well you will be able to scroll.

If you are just testing, you can run xbmc in a window next to VC so that xbmc can still have focus.

I am probably going to add some button commands for xbmc using the eventserver / eventclient for xbmc. I have been writing some test code for it. It should be faster than using the http interface. Also as far as I know, it is not deprecated like the http api., but it is only good for simple commands.

PT-BR and German will be in the next version which I will try to release tomorrow. Neither one will be 100% complete. For now it will show in whatever language you have set as the display language for windows. Later I will try to make an option to override the display language to anything you want.