Ah, yes.  It's supposed to be about music.  "Ticks" be d*mned!  Where are
the definitions of Whole_Note, Half_Note, Quarter_Note, etc.?  Base these
on "Ticks per measure", then forget about ticks.  Added advantage: you can
changed the tempo by changing one constant.  Define the pitches using
something akin to do, di, re, ri, mi, fa, etc., and you will be able to
change the key just as easily.

Yes, the nitty-gritty must worked out, but don't forget the abstractions.


"W. Wesley Groleau x4923" <[log in to unmask]>@ACM.ORG> on
11/06/2000 01:58:12 PM

Please respond to "W. Wesley Groleau x4923" <[log in to unmask]>

Sent by:  "Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>

To:   [log in to unmask]

Subject:  Re: Timing for MIDI: an interesting project

I think most of us are missing something here.  We're talking about
something related to MUSIC.  How many microseconds of inaccuracy can a
human hear?  How long does a song have to be before the accumulated errors
add up to that many microseconds?

On top of that, all the instruments in the band should be using the same
MIDI clock, so they all have the same error, and they all finish the song
at the same time.  Who's going to notice if a song lasts 300 seconds
instead of 301?  Radio stations often get away with speeding up songs
enough to squeeze in one more 30-second commercial per half hour.

If you really do have a drift problem, try something like (type conversions
deliberately omitted):

   Microsec_Inaccuracy_Times_One_Million : Integer := ......;
   -- the difference between an actual tick interval
   -- and what the interval should be.

   Number_Of_Ticks := Number_Of_Ticks + 1;

   Next_Tick := Current_Tick + Tick_Interval +
         (( Number_Of_Ticks *
            Microsec_Inaccuracy_Times_One_Million ) / 1_000_000);

   delay until Next_Tick;

Write in  * Wes Groleau *  for President of the U.S.A.
I  pledge  to  VETO  nearly  everything.