Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!cica!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!uakari.primate.wisc.edu!xanth!mcnc!ncsuvx!ecemwl!jnh
From: jnh@ecemwl.ncsu.edu (Joseph N. Hall)
Newsgroups: comp.sys.mac.programmer
Subject: Re: MIDI Manager woes...
Message-ID: <4594@ncsuvx.ncsu.edu>
Date: 20 Nov 89 13:12:33 GMT
References: <46d6de80.a590@mag.engin.umich.edu>
Sender: news@ncsuvx.ncsu.edu
Reply-To: jnh@ecemwl.UUCP (Joseph N. Hall)
Organization: North Carolina State University
Lines: 25

In article <46d6de80.a590@mag.engin.umich.edu> lwk@caen.engin.umich.edu (Woody Kellum) writes:
>
>I bought the MIDI manager from APDA and, as Murphy would say, it never stood
>a chance.  The demo programs communicate among themselves just fine, but when
>I try to hook up an actual device to SquidCakes to monitor it, or when I try
>to play it through SimpleKeys, etc, nothing works right.  Here's a summary
>of the weirdness:
>
The demo programs worked fine right out of the box for me.  If I remember
correctly, I first tested them with a DX-7 and a couple of TX-81Zs.  If you
post a list of the equipment in question you might get some useful answers.
Your notion that your MIDI stream is being "corrupted" is probably wrong
unless there is something *seriously* out of whack in your setup.

There is always the possibility (however remote) that another INIT (or
whatever) is causing you difficulty.  The MIDI Manager patch crashes some
commercial software ...

The folks on rec.music.synth and rec.music.makers may be able to help you
figure out what MIDI idiosyncracies your specific instruments have.

v   v sssss|| joseph hall                      || 4116 Brewster Drive
 v v s   s || jnh@ecemwl.ncsu.edu (Internet)   || Raleigh, NC  27606
  v   sss  || SP Software/CAD Tool Developer, Mac Hacker and Keyboardist
-----------|| Disclaimer: NCSU may not share my views, but is welcome to.