switchboardI was using the vOICe to find the switch board in a conference room to plug-in my laptop. It was very tough especially since that part of the room was poorly lit.
Archives for December 2008
outinI have attempted to show the transition between a glass wall and a glass door. I am in the door way of a balcony. I was trying to determine where the door way began. It is very tough when there is a glass wall and a glass door since you keep seeing the inside of the room.
leavesI was visiting Jaipur and was staying at this place which had an interesting balcony. See the image of the leaves of a plant. I walked towards this sound in attempt to find the railing of the balcony.
fronthouseThe front of my house on Diwali 2008. It has a lot of lights.
See the abstract of this study. If I understand things correctly, a late blind subject was subjected to TMS such that the areas related to vision were made temporarily inoperative. This user was unable to use the vOICe thereby indicating that the vOICe’s approach to sensory substitution is closly mapped to vision.
I have created a utility to remote control the vOICe
The program is open source and you can get it at the following link.
I am including the program’s manual below.
vOICeCmd is a utility that allows remote control of the The vOICe from the commandline. The vOICe uses windows messages as a remote control mechanism. This approach though easy-to-use cannot be used by the average user primarily because it involves a lot of programming. This utility is a wrapper around that functionality. The entire interface of the vOICe can be accessed using simple to use commandline commands.
All that you need to do to use this interface is to ensure that the vOICe is running. Once that is the case, you can pass one command at a time to the vOICe. For example, to increase the frame rate by four times, you would issue the command:
similarly, to mute the vOICe, you would issue the command
no special installation is required. Copy the vOICeCmd executable to the folder where the vOICe executable resides.
- Only one command at a time can be specified on the commandline using vOICeCmd. This is deliberate. It is easy to implement the passing of multiple commands. However, in my experience, the user needs some time to assimilate any change that takes place in the output of the vOICe. So, as of now, I have decided to stick to the single command approach.
- It is also important that the vOICe is started manually. I have decided not to start the vOICe from vOICeCmd. This is because I have no easy way of telling whether the user has enough permissions to run the vOICe.
Batch file error codes
If executing vOICeCmd from a batch file, you can use the errorlevel construct to trap the results from vOICeCmd.
|1||an invalid command was specified|
|2||no command was specified on the commandline|
|3||the vOICe is not running|
This programme would not have been possible without the sample code an easy to follow instructions provided on the seeing with sound website by Doctor Peter BL Meijer
I would also like to thank members of the program-l list
in particular, Mark Long for helping me with my Visual C++ questions.
You can contact me through the seeing with sound mailing list or through this blog.
= Links of interest =
Direct link to the page about remote controling the vOICe including a list of commands