Path: utzoo!utgpu!watmath!clyde!att!rutgers!rochester!daemon
From: miller@ACORN.CS.ROCHESTER.EDU
Newsgroups: comp.sys.mac.programmer
Subject: Re: Wish-List: Decent MIDI support for the Macintosh
Message-ID: <1989Jan11.124632.27532@cs.rochester.edu>
Date: 11 Jan 89 17:46:32 GMT
Organization: U of Rochester, CS Dept, Rochester, NY
Lines: 23

From: Brad Miller <miller@CS.ROCHESTER.EDU>

    Date: 9 Jan 89 13:49:45 GMT
    From: nick@lfcs.ed.ac.uk (Nick Rothwell)

    David, you mentioned "pressuring" MIDI software developers to conform to
    the correct MIDI driving routines (before realising that there aren't any..).
    One very important guideline which makes things much more bearable is this:

	    If you're sent to the background by MultiFinder, relinquish and
	    reset the serial ports.

    I know that the Kurzweil MIDIscope does this. Perhaps Performer does as well,
    I will investigate. This at least allows several MIDI applications to be
    switched between, without things going seriously nonfunctional.

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}