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

crap that did it!!
i was looking at that page for like 2 days and didnt understand it. i 
must have skipped over that in the FAQ!! omg thanks SO much steve!!

--- In xl7@yahoogroups.com, "steve_the_composer" <smw-mail@...> wrote:
>
> I delved a little further into MIDICOM3 and here are two references 
> you should check out:
> 
> (1) From the README file:
> 
>  Q: How do I receive MIDI timing data?
> 
>  A: This is filtered out by default in the callback function in 
> DELPHMCB.PAS. Enable it by removing the check for MIDI_TIMINGCLOCK 
in 
> the midiHandler function.
> 
> (2) From DELPHMCB.PAS (with dashes to simulate whitespace):
> 
> Begin
> ---case wMsg of
> -----mim_Open: {nothing};
> -----mim_Error: {TODO: handle (message to trigger exception?) };
> -----mim_Data, mim_Longdata, mim_Longerror:
> --------begin
> { TODO: Make filtered messages customisable, I'm sure someone wants 
to
> do something with MTC! }
> ----------if (dwParam1 <> MIDI_ACTIVESENSING)and (dwParam1 <> 
> MIDI_TIMINGCLOCK) then
> --------------begin
> etc.
> 
> You might want to try deleting "and (dwParam1 <> MIDI_TIMINGCLOCK)" 
> and recompiling the Delphmcb unit.
> 
> (BTW: David Churcher's TODO comment about MTC leads me to believe 
he 
> equated MTC with MIDI_TIMINGCLOCK.)
> 
> Hope this helps.
> 
> --Steve
> 
> --- In xl7@yahoogroups.com, "malik" <malik_martin@> wrote:
> >
> > > --- 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?
>