Thread: Feature Requests

Switch apps, and volume were both already planned for the next major release. I can also look at turning the monitor on and off.

Can you create a log file will all the commands recognised and the ability to disable the execution of the commands.

The reason I ask is because I want to figure out command keywords that are being recognised just for car noise and MP3 playback. What I'd like to do is leave the car running for 20 minutes with MP3 full blast (normal volume!) and leave BSR to see what it does. At the moment I have to sit there and see the balloon popups or status bar of the app. Ideally I'd like to go away and have a coffee then come back and see what commands are failing on a regular basis.

While this test is going on I'd like to be able to turn off the execution of any commands BSR recognises. Ideally if BSR can come back with statistics on which commands are worse that would make my life very easy

Originally Posted by ruairi

Can you create a log file will all the commands recognised and the ability to disable the execution of the commands.

The reason I ask is because I want to figure out command keywords that are being recognised just for car noise and MP3 playback. What I'd like to do is leave the car running for 20 minutes with MP3 full blast (normal volume!) and leave BSR to see what it does. At the moment I have to sit there and see the balloon popups or status bar of the app. Ideally I'd like to go away and have a coffee then come back and see what commands are failing on a regular basis.

While this test is going on I'd like to be able to turn off the execution of any commands BSR recognises. Ideally if BSR can come back with statistics on which commands are worse that would make my life very easy

This is ... different.

I think you should just wait for 1.4 for a couple of reasons.

1. You will ALWAYS get RANDOM recognitions when you leave voice recognition running with loud music.

2. 1.4 or possibly 1.5 will have the option to Mute music, and enable recognition with a keypress. When a command is recognized, the music will be un-muted and recognition turned off. This should solve your problem.

If you could give suggestions for the development of number 2, that would be great, but I do think that making a log and disabling the executing of commands will be an unnecessary feature after 1.4.

If you are going to mute music then I'd prefer to do it by voice, I don't have a keyboard in the car.

Also, I still think the logging of commands would be useful (even with mute). I have a VW TDI engine and it is a noisey as hell. Just on my test PC I get false commands being recognised by BSR so in the car it is bound to be worse. The MICS I use are very good at reducing moise but still BSR picks up false commands.

Because BSR allows so much customisation of the voacb file users can put anything in. So the log file would help to train the user in what is a good command and what's a bad command.

Originally Posted by Cris

Maybe the music should not be muted down to zero, but do it like an HU, mute down to a certain level, but you can still hear the music...
One other thing, maybe for muting, you could create a hotkey, so we could use the remote to mute with Girder...

Sure, this could be configurable.

No program can pysically turn the power of the monitor on and off, but it can stop sending the video signal to the monitor, which will put it into standby.