Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!ucsd!ames!ncar!noao!amethyst!face
From: face@math.arizona.edu (Chris Janton)
Newsgroups: comp.sys.mac.programmer
Subject: Re: MIDI Management Tools...first impressions (long)
Keywords: MIDI Manager, impressions, bugs
Message-ID: <1034@amethyst.math.arizona.edu>
Date: 6 Sep 89 00:06:54 GMT
References: <25132@iuvax.cs.indiana.edu> <263@castle.ed.ac.uk>
Sender: news@amethyst.math.arizona.edu
Organization: CCIT, Univ. of Arizona, Tucson AZ 85721
Lines: 25

>Ah. This suggests that I won't ever me able to use a MIDI-Manager-version
>of Performer without more RAM. Performer is too big for a 1 Meg Mac under
>MultiFinder, so I can't run this PatchBay (or the DA) and then sign in
>Performer? Or can I?
>   Does anybody know if MOTU are going to provide an upgrade, anyway?
>
>> Jon W. Backstrom                 "Yah sure...we gonna have fun, you bet!"

You do not have to have the Patch Bay open to make connections to the MIDI
Manager.  A program can make a connection directly to the manager (ignoring
the Apple guidelines) with relative ease.  The keywords here are

#define	AMDriver	'amdr'
#define	AMDtime		'ATim'
#define	AMDin		'Ain '		/* is the inbound data */
#define	AMDout		'Aout'		/* is the outbound data */

which are the 'names' of the MIDI driver ports.  Just connect an input port to
'amdr''Ain' etc. using the MIDIConnectData and MIDIConnectTime calls.

------------------------------------------------------------------------
Chris 'Face' Janton | Internet: janton@rvax.ccit.arizona.edu
CCIT                | UUCP: ..{cmcl2,allegra,noao}!arizona!face
Univ. of Arizona    | Bitnet: janton@arizrvax
Tucson, AZ  85721   | Phone: +1 602 621-6848