[gmpi] Re: 3.8. Events Req 25 eventorder




> On Tue, Jan 18, 2005 at 06:12:28PM +0100, Robert Fehse wrote:
> > eventlist->sortByTimeStampNoteOffBeforeNoteOn();
>
> Something like that, except with a sane API :)

okay ;)

> > > And I think that it makes sense to say that events are sorted in
timestamp
> > > order, with events for the same timestamp sorted by the order
received.
> >
> > ok, but cases like i described (loop border events) should described
also in
> > detail because there is no receive order if the user has drawn a note in
the
> > sequencer, here the host simply must follow the rules GMPI gives (so
there
> > should be exact rules).
>
> The entity that is sending the events is responsible to send events.  So
> it should send an off before an on.  Or better, it should send a restart,
> if we have such a thing.

restart ? ...sounds weird to be honest


> > btw.: is the intention to pass the list by reference and declaring it
valid
> > for the following process loop (like vst) ?
>
> Something like that sounds reasonable to me.

yes but if you want to sync the events in realtime (realtime quantization)
you have to copy and rearrange the event queue , i hope the eventlist class
will have the power to do such things fast(!!!) and easy.
but okay thats not typically and more plugin related.

Robert


----------------------------------------------------------------------
Generalized Music Plugin Interface (GMPI) public discussion list
Participation in this list is contingent upon your abiding by the
following rules:  Please stay on topic.  You are responsible for your own
words.  Please respect your fellow subscribers.  Please do not
redistribute anyone else's words without their permission.

Archive: http://www.freelists.org/archives/gmpi
Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe

Other related posts: