Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!think.com!linus!linus!mingus!marsh From: marsh@mingus.mitre.org (Ralph Marshall 617 271-8784) Newsgroups: comp.human-factors Subject: Re: audio Message-ID: <1991Jun13.163011.21218@linus.mitre.org> Date: 13 Jun 91 16:30:11 GMT References: <1991Jun12.171211.2716@cs.umn.edu> Sender: news@linus.mitre.org (News Service) Organization: The MITRE Corporation, Bedford, MA 01730 Lines: 25 Nntp-Posting-Host: mingus.mitre.org In article kpc@pluto.arc.nasa.gov (kpc) writes: >using audio for another few dimensions is a great idea. > >one thing that's important about audio is that it should be: > > disableable > > not required, so that disabling it does not remove functionality Another feature which hasn't been mentioned here is that you want the same sort of instant-feedback that you expect with a mouse and keyboard interface. If the sound is always after the event which triggers it (and not even by a consistent amount) because the sound is produced by the same CPU which is running the rest of the application and interface, the users will hate it. So, you either need embedded signal processing chips in the computer, or external processing power such as a MIDI-controllable music device. Also, Bill Gaver has done work in the value of adding sound to multi-user applications, in particular where users are coordinating on a given task but aren't in the same room. Neat stuff! -- Ralph Marshall (marsh@linus.mitre.org) Disclaimer: Often wrong but never in doubt... ---------------------------------------------------------------------------