Path: utzoo!attcan!uunet!lll-winken!lll-ncis!helios.ee.lbl.gov!ux1.lbl.gov!beard
From: beard@ux1.lbl.gov (Patrick C Beard)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Wish-List: Decent MIDI support for the Macintosh
Message-ID: <1673@helios.ee.lbl.gov>
Date: 12 Jan 89 05:06:26 GMT
References: <1989Jan11.124632.27532@cs.rochester.edu>
Sender: usenet@helios.ee.lbl.gov
Reply-To: beard@ux1.lbl.gov (Patrick C Beard)
Organization: Lawrence Berkeley Laboratory, Berkeley
Lines: 19

In article <1989Jan11.124632.27532@cs.rochester.edu> miller@ACORN.CS.ROCHESTER.EDU writes:
>
>But of course, what you REALLY want is to allow >1 application to
>simultaneously access the MIDI bus, eh? I know I'd like to generate MIDI
>events with one program in the background that Performer can capture while
>running in the foreground, or vice-versa. Right now, it requires >1 mac!
>----
>Brad Miller		U. Rochester Comp Sci Dept.
>miller@cs.rochester.edu {...allegra!rochester!miller}

The obvious solution:  two MIDI interfaces, one connected to the printer
port, one connected to the modem port.  One application services one, and
the other application the other.  For example, for one application, 
a sequencer let's say, to record the output of the other, an algorithmic
composing machine, just connect a MIDI out from one interface to the MIDI
in of the other.  That way everything works quite nicely under MultiFinder.

Patrick Beard
Berkeley Systems, Berkeley CA