Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!yale!cmcl2!brl-adm!umd5!uvaarpa!virginia!boole!pmy
From: pmy@boole.acc.virginia.edu (Pete Yadlowsky)
Newsgroups: comp.sys.cbm,comp.sys.amiga
Subject: Re: Amiga and MIDI
Message-ID: <336@boole.acc.virginia.edu>
Date: Mon, 30-Nov-87 11:29:31 EST
Article-I.D.: boole.336
Posted: Mon Nov 30 11:29:31 1987
Date-Received: Fri, 4-Dec-87 20:48:04 EST
References: <447@nuchat.UUCP> <32160@auc.UUCP> <528@otto.COM> <21987@ucbvax.BERKELEY.EDU>
Organization: Academic Computing Center, University of Va.
Lines: 14
Keywords: MIDI Amiga Atari ST
Xref: mnetor comp.sys.cbm:982 comp.sys.amiga:11790

In article <21987@ucbvax.BERKELEY.EDU>, bryce@hoser.berkeley.edu (Bryce Nesbitt) writes:
> The midi.device work should ensure that in the future if non-compatible
> interfaces *are* marketed, they will all talk with a clean, standard
> multitasking interface.

What midi.device work? I'd kill for a midi.device (as would many others).
Who's doing this?


-- 
Pete Yadlowsky
Academic Computing Center
University of Virginia
e-mail: pmy@vivaldi.acc.virginia.EDU