Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!sri-unix!sri-spam!ames!ucbcad!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU (Matt Dillon)
Newsgroups: comp.sys.amiga,rec.music.synth
Subject: Re: Amiga midi problems?
Message-ID: <8708240351.AA12164@cory.Berkeley.EDU>
Date: Sun, 23-Aug-87 23:51:44 EDT
Article-I.D.: cory.8708240351.AA12164
Posted: Sun Aug 23 23:51:44 1987
Date-Received: Tue, 25-Aug-87 00:46:27 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 22
Xref: mnetor comp.sys.amiga:7712 rec.music.synth:1339

>As for the Amiga MIDI problems, I'd like someone to explain exactly what
>they are without jingoism (on the part of ST people) or mealymouthed

	I think the problem is mainly the serial driver currently installed.
After all, 303uS per character seems like plenty of time for an interrupt
handler to queue to a FIFO.  Does anybody know how long the copper takes to
setup the video chip at 320x200x4?

	Secondary problems occur when one is in extremely high resolutions,
but assuming the MIDI program only uses something simple, like 320x400x4 
(16 colors interlace), this is a moot point.  

	The RBF interrupt (Read Buffer Full) is at priority 5.  The only
things above it are the disk-sync interrupt (5) and external interrupt (6).
Neither of these are used normally. 

	The only other thing I can think of is if somebody is calling
Disable() for too long a period of time.  Could somebody at CATS fgrep the
kernel source for Disable() calls?????  I'm working on a replacement
serial.device, but with school starting up it won't be done for a while.

					-Matt