Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!rutgers!cbmvax!andy From: andy@cbmvax.UUCP (Andy Finkel) Newsgroups: comp.sys.amiga,rec.music.synth Subject: Re: Amiga midi problems? Message-ID: <2247@cbmvax.UUCP> Date: Mon, 24-Aug-87 15:11:45 EDT Article-I.D.: cbmvax.2247 Posted: Mon Aug 24 15:11:45 1987 Date-Received: Wed, 26-Aug-87 01:28:09 EDT References: <1408@ico.UUCP> <1601@ulowell.cs.ulowell.edu> <628@cup.portal.com> <533@sugar.UUCP> Reply-To: andy@cbmvax.UUCP (Andy Finkel) Organization: Commodore Technology, West Chester, PA Lines: 26 Xref: mnetor comp.sys.amiga:7753 rec.music.synth:1346 In article <533@sugar.UUCP> peter@sugar.UUCP (Peter da Silva) writes: >As for the Amiga MIDI problems, I'd like someone to explain exactly what >they are without The Amiga serial.device does not timestamp the serial input events. In a multitasking system you cannot guarantee getting the events exactly as them come in (not without giving up the advantages of multitasking). There are timers available on the Amiga which would allow your program to timestamp the events when your program receives them, but sometimes this isn't good enough. The solution ? There are two...(I like this one) write a small, very fast midi.device (which can leave out a lot of stuff the serial.device has to keep around) or set up a small task, running at a high priority, whose task it is to get bytes from the serial.device, timestamp them, and feed them to whoever asks. (through a message port) andy finkel -- andy finkel {ihnp4|seismo|allegra}!cbmvax!andy Commodore-Amiga, Inc. "The goal of Computer Science is to build something that will last at least until we've finished building it." Any expressed opinions are mine; but feel free to share. I disclaim all responsibilities, all shapes, all sizes, all colors.