the Audio User Interface

**thecapitalizt** · 01-04-2005, 09:25 PM

Again, with the iDrive inspiration, except that heres where this differs. I personally think that this should be implemented in every carpc software, since it should be just as easy to implement, and it makes using it much easier.

Imagine using a Griffin Powermate to control your software. Problem is, that even if your computer made a "click" then you would still have to look at the screen to see where you are. Instead of a "click", assign a musical tone to each different menu option. You don't have to do it for everything, but do it for the major things (forward-back, etc.). For each of the major functions (e.g. mp3, radio, car data), use different instruments so you can recognize what mode you're in. Can't use software voice (except for running through presets, like 1-9), since it takes too long to speak everything. Your brain has an amazing ability to learn things, and this is no exception. With a bit of use while looking, you will learn what sound corresponds with which option. If GPS support is enabled, turn the sounds off when the car is stopped so that it doesn't become annoying. Plus, if the cursor is used, don't make the sounds (incase the passenger is doing the controlling)

When I get around to creating my app (tentatively called iDash), this is something that i'll implement.

**0l33l** · 01-04-2005, 09:43 PM

Originally Posted by thecapitalizt

Can't use software voice (except for running through presets, like 1-9), since it takes too long to speak everything.

Saying "Computer" and then "Next" doesn't takes too long

**frodobaggins** · 01-04-2005, 11:38 PM

Originally Posted by thecapitalizt

Again, with the iDrive inspiration, except that heres where this differs. I personally think that this should be implemented in every carpc software, since it should be just as easy to implement, and it makes using it much easier.

Imagine using a Griffin Powermate to control your software. Problem is, that even if your computer made a "click" then you would still have to look at the screen to see where you are. Instead of a "click", assign a musical tone to each different menu option. You don't have to do it for everything, but do it for the major things (forward-back, etc.). For each of the major functions (e.g. mp3, radio, car data), use different instruments so you can recognize what mode you're in. Can't use software voice (except for running through presets, like 1-9), since it takes too long to speak everything. Your brain has an amazing ability to learn things, and this is no exception. With a bit of use while looking, you will learn what sound corresponds with which option. If GPS support is enabled, turn the sounds off when the car is stopped so that it doesn't become annoying. Plus, if the cursor is used, don't make the sounds (incase the passenger is doing the controlling)

When I get around to creating my app (tentatively called iDash), this is something that i'll implement.

I just did something similar with my powermate last night.
I plan on releasing the girder file when I get done.

(also iDash sounds like a cool name)

**BigToach** · 01-04-2005, 11:59 PM

uhoh, no more frodoplayer...

**frodobaggins** · 01-05-2005, 12:06 AM

Originally Posted by BigToach

uhoh, no more frodoplayer...

Oh I wouldn't steal his name

I meant it just sounds cool.

**knubile** · 01-05-2005, 12:06 AM

haha. I used the name "iDash" when I entered a University business plan competition using my carpc as the product idea.
And hey! Just googled for it. Found the news release. We came in 3rd.