> From: Ian Collier > >I don't think that's true, but anyway the MIDI interrupts are not essential, >and their usefulness is somewhat reduced if you have to handle other >kinds of interrupts going on at the same time.
The MIDI-In interrupt is useful. :) But, with the MIDI-Out interrupt, I agree. In fact, depending on your interpretation of the Tech Manual, MIDI Out doesn't generate and INT signal...(?) >Unless your program >needs to multitask I would ignore the MIDI output interrupt entirely >and just code a busy loop before each output. There was a discussion >of this last year (1998-06b, archive fans) in which I discovered the >correct way to use the MIDI input interrupt, and posted the following >pseudo-code for outputting a byte. > >putbyte: wait until in(248)&2 = 0 then output to port 253 I agree with that. (That discussion was about the MIDI In for my MIDI-Bar proggy... :) ) Even if your program does want to do something whilst it's waiting to spurt something out, just do a simple check on the MIDI Out line of the Status byte: if the byte has been sent, send another byte else do something else... Justin. > imc
