Emu XL-7 & MP-7 User's Group

I. Timestaming Issue:

I only took a quick look at the library source code and I believe it 
does support timestamping.
 
--- In xl7@yahoogroups.com, Aaron Eppolito <synthesis77@...> wrote:
>
> As a side note, even if you were getting clocks, if they weren't
> timestamped as to reception time, it'd be pretty much impossible to
> get useful timing information from them anyway.  That's not to say
> it wouldn't, but I would doubt it.
> 
> -Aaron

II. MTC and MIDI clocks Issue:

Yes, they are different. That's why I only >>guessed<< that midi 
clocks might be filtered, too. I would be happy to learn they are not.

> --- steve_the_composer <smw-mail@.. .> wrote:> 
> > I took a quick peek at the MIDIIN.PAS file where I found the 
> > following note:
> > 
> > "Midi Time Code (MTC) and Active Sensing: The DLL is currently 
> > hardcoded to filter these short events out, so that we don't 
> > spend all our time processing them."
> > 
> > Without delving further, my guess is that MIDICON3 will not give
> > you access to the F8, FA, FB, F9 bytes you need.

> yeah that's been filtered but i dont think it has anying to do with
> F8 byte does it? arent MTC and MIDI Clock 2 different things?

III: How is MIDI_TIMINGCLOCK handled?

Is there source code for the DLL that handles (and hence filters) 
incoming midi data? If so, that should tell if clocks can be returned 
to your code or if they are filtered out.

Write some simple code that takes midi in and tells you if you are 
getting each of the following:

MIDI_ TIMINGCLOCK = $F8;
MIDI_START = $FA;
MIDI_CONTINUE = $FB;
MIDI_STOP = $FC;

Malik wrote:

> In the MIDICOM3 library, i've managed to find a const called
> MIDI_TIMINGCLOCK in the midicons.pas file and it = F8!!!!

--Steve