Path: utzoo!mnetor!uunet!cbmvax!rutgers!mcnc!uvaarpa!virginia!boole!pmy
From: pmy@boole.acc.virginia.edu (Pete Yadlowsky)
Newsgroups: comp.sys.amiga
Subject: Re: Problems reading midi data
Message-ID: <406@boole.acc.virginia.edu>
Date: 1 Feb 88 17:28:58 GMT
References: <1599@phoenix.Princeton.EDU>
Distribution: na
Organization: Academic Computing Center, University of Va.
Lines: 30

In article <1599@phoenix.Princeton.EDU>, andy@phoenix.Princeton.EDU (Andrew M. Milburn) writes:
> Can someone outline the correct way to open and read the serial port
> to capture incoming midi data?  I've been hacking at this a while,
> but I'm having (very) intermittent problems losing single bytes of data.
> This only happens on certain synthesizers (a DX100 and a DX27)
> and only in certain phases of the moon.  I'm setting RAD_BOOGIE,
> any other tricks?

Unfortunately, even with RAD_BOOGIE, the serial port can lose bytes on
large transfers. Do these data losses occur during normal midi channel
messages (e.g. note_on, note_off), or while passing big chunks of
sysex stuff? I'd be very surprised if the former, not so if the latter.
Maybe you could try breaking up sysex transfers.

Also, there's a PD midi.library available which I find quite nice. It
has greatly simplified a lot of my own midi programming. I've already
discussed (raved about) it on the net. Briefly, it provides the midi
application designer a set of tools that facilitate the contruction
of midi communication networks, based on Exec's list, port and message
schemes. The library automatically handles all midi message merging and
distribution, and all serial port communication/management. Now if
only someone would write a PD midi.device! :-)   Let me know if you'd
like more info.


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