> > > The problem as I see it is that the ALSA OSS emulation does not send this
> > > TMR_WAIT_ABS event - it only sends the NOTEON event. Jazz gets this and
> > > without any TMR_WAIT_ABS to tell it otherwise, assumes that it occured at
> > > the "current" time - which is always a multiple of 48
At Fri, 28 Mar 2003 08:58:47 +1030 (CST),
Jonathan Woithe wrote:
>
> Ok. Last night I investigated ev->time.tick. Admittedly this was under
> 0.90rc8b. It transpires that ev->time.tick is *always* zero when the event
> is a NOTEON/NOTEOF, and therefore gives no timing information what-so-ever.
> > Now, when input occurs, Jazz++ needs to know the current time, which is very
> > unlikely to be a multiple of 48 ticks. Under nateive OSS it seems that
> > before the NOTEON event (for example) OSS sends a TMR_WAIT_ABS event to
> > update the application on the current time - the NOTEON event
At Thu, 27 Mar 2003 09:54:16 +1030 (CST),
Jonathan Woithe wrote:
>
> I also suspect that seq_oss_midi.c:send_midi_event() might also need to
> reference ev->time.tick rather than the oss timer because as far as I can
> tell the oss timer time is somewhat bogus (or at least that's what it
> appears
> > Now, when input occurs, Jazz++ needs to know the current time, which is very
> > unlikely to be a multiple of 48 ticks. Under nateive OSS it seems that
> > before the NOTEON event (for example) OSS sends a TMR_WAIT_ABS event to
> > update the application on the current time - the NOTEON event
At Wed, 26 Mar 2003 17:30:09 +1030 (CST),
Jonathan Woithe wrote:
>
> Hi all
>
> I've been messing with the following problem on and off for the last few
> weeks. It occurs when the OSS sequencer emulation is used with Jazz++
> 4.1.3. In essence, incoming MIDI events from an external MIDI interf
