Work on the Wiki

[jitterjames]

I have been trying to put together a detailed manual on the VoxCommando wiki site.  I am using images with simple letters to mark items of interest so that the pages can be translated into other languages.

It is a lot of work.  Just trying to describe all the elements of VoxCommando really makes me realize how much I have put into this beast!  And it is still hungry for more...

Anyway, take a look at what I have done so far if you are interested.  If anyone thinks they could help, that would be great.  I don't really have the time for it.

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

Feel free to re-use or link to the images form the wiki if they can help you to describe a problem, or a solution...

example image:

[Wanilton]

Wow great work, vou traduzir para pt-br com certeza talvez leve um tempo...mas farei,

[Wanilton]

James, qual a finalidade do checkbox, próximo a letra A?

[jitterjames]

if you use a remote with eventghost you can request to do  a single command and then automatically go back into standby. (In this case the checkbox would be checked until it recognized a command).  VC is also supposed to send a signal that the command was complete.  In this manner you could push a button, have eventghost mute, or reduce the volume of your system, issue one command, and then automatically restore the volume and do the command.  Useful if you use an open microphone with loud music or video.

I haven't used it for a while and honestly I don't even know if it really works anymore... if this is a feature that people are interested in I will look into it.

[derelict]

smile.... i was wondering about that checkbox myself some time too.

the idea is nice... and i "could" have a use for it.... but that "process" could be achieved by using eventghost alone... and the vox:on/off/standby broadcast messages to vc... not ?

marcel

[jitterjames]

Yes, you could.  But set up properly this would be more efficient and faster.

For one thing, eventGhost would not have to use an event like broadcast.* that was checked every single time a command was sent.  Also, VC will turn itself off immediately upon recognizing any command rather than the message having to be sent to EG, then processed and then sent back as a "vox standby" command.

[derelict]

yes... that's a valid point.... so how can i implement this ? :-)

[jitterjames]

I'll be uploading a new version within the next week and I'll be sure that everything is working.  We can discuss how to implement it then.  I think for it to be flexible enough, I need to have a field under triggered speech emulation, where you can choose what even gets fired in VC when the single command is recognized, with that you'll be able to set it to send an EG command, and then either switch off, or switch to standby etc.  The way it was originally was not very flexible.  I have another user who wants to do this with mediaMonkey and intelliremote so I'll try to make something that works for everyone.  My next release will include a variety of new stuff...

[derelict]

ok.... let's give it a shoot as soon as that version is ready :-)

you made me wondering now.... what else will be in that new version ?

marcel

[jitterjames]

heh heh.  Well it's not carved in stone, but this should give you a good idea.  There may be more, there may be less.

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

the next version I upload will actually be called 0.841

[Wanilton]

WOW, great news...