Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!yale!ox.com!crane!rich From: rich@dante.sendai.ann-arbor.mi.us (K. Richard Magill) Newsgroups: comp.sys.mac.programmer Subject: Re: Apple MIDI Driver Message-ID: Date: 26 Feb 90 22:13:06 GMT References: <4260@cbnewsl.ATT.COM> Sender: news@ox.com (Usenet News Administrator) Reply-To: rich@ox.com Organization: Digital Works, Ltd. - Ann Arbor, MI Lines: 18 In-Reply-To: saf@floyd.ATT.COM's message of 21 Feb 90 17:28:09 GMT In article <4260@cbnewsl.ATT.COM> saf@floyd.ATT.COM (Steve Falco,14D-327,4865,ATTBL) writes: Has anyone found a "raw" mode whereby arbitrary data can be written? Just do it. ie, send one byte packets. Seems to work on output. My guess is that the sanitization guarantee comes from requesting all input to be sanitized. that is, midi manager doesn't *enforce* sanitization. If your application isn't producing sanitized, this approach will probably break other midi manager clients. It may break them anyway. Also, since Apple can sanitize data coming in from a synthesizer, there should be a way to force the same clean-up routines to filter data from an application, relieving the application of the hassles of doing its own sanitizing. Looks like this is only done in the apple midi driver and thus isn't exactly a midi manager function. Still, you have a point.