Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!ll-xn!adelie!mirror!cca!m204help
From: m204help@cca.UUCP
Newsgroups: comp.sys.atari.st
Subject: reading midi input
Message-ID: <14748@cca.CCA.COM>
Date: Mon, 6-Apr-87 08:06:48 EST
Article-I.D.: cca.14748
Posted: Mon Apr  6 08:06:48 1987
Date-Received: Fri, 10-Apr-87 00:11:27 EST
Organization: Computer Corp. of America, Cambridge, MA
Lines: 23

Recently, I posted a note asking for help with reading the midi
port inside a 
c program, written with the MEGAMAX C development system. I received
a lot of replies for which I am grateful. I also noticed that there seemed
to be a discussion going on between a couple of you out there as to whay
I might have been having the problem I was having. Someone suggested that
perhaps since I had built a loop which ran as long as there was input at the
midi port, that perhaps the machine was so fast that it checked the port 
before data showed up and that was causing the problem. 
Well through some really sloppy programming non-methodology, I have been 
able to make my program work, but I don't know what I did to fix it !
In the process, however, I did find out one thing.....the function that I
am using to read the midi port (Bconin(3)) BLOCKS UNTIL a midi byte appears 
at the port. I have tested this function by changing the address to that of the
keyboard and it worked fine....as I said my program now works and uses this 
function. 
So for the person who thought this might be the problem, and anyone who read
it, I just wanted to let you know that this function DOES work and WILL block
until data appears at the midi port. 
I should say however, that I think that this was a pretty good guess as to
why my program may not have been working.
Anyway, thanks again for all of your help, 
Keith