[gmpi] Re: 3.8. Events Req 25 eventorder
- From: "Robert Fehse" <robertfehse@xxxxxx>
- To: <gmpi@xxxxxxxxxxxxx>
- Date: Tue, 18 Jan 2005 18:12:28 +0100
Hi
> if you have multiple
>senders to one receiver, you can't guarantee to get it right, since that
>involves actual meaning and intent.
the eventqueue class then should have special sort functions, so that a
plugin
can prepare the list as it wants.
eventlist->sortByTimeStampNoteOffBeforeNoteOn();
> The best we can do is provide a fixed guideline for expected behavior.
Yes that's exactly what i want.
> 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).
> If this is wrong for a plugin, the plugin should handle it internally.
or better the eventlist class is able to handle it easily.
btw.: is the intention to pass the list by reference and declaring it valid
for the following process loop (like vst) ?
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
- Follow-Ups:
- [gmpi] Re: 3.8. Events Req 25 eventorder
- From: Tim Hockin
- References:
- [gmpi] Re: Reqs final draft
- From: Didier Dambrin
- [gmpi] Re: Reqs final draft
- From: Mike Berry
- [gmpi] Re: Reqs final draft
- From: Didier Dambrin
- [gmpi] Re: Reqs final draft
- From: Mike Berry
- [gmpi] Re: Reqs final draft
- From: Angus F. Hewlett
- [gmpi] 3.8. Events Req 25 eventorder
- From: Robert Fehse
- [gmpi] Re: 3.8. Events Req 25 eventorder
- From: Tim Hockin
- [gmpi] Re: 3.8. Events Req 25 eventorder
- From: Jeff McClintock
- [gmpi] Re: 3.8. Events Req 25 eventorder
- From: Tim Hockin
- [gmpi] Re: 3.8. Events Req 25 eventorder
- From: Robert Fehse
- [gmpi] Re: 3.8. Events Req 25 eventorder
- From: Tim Hockin
Other related posts:
- » [gmpi] 3.8. Events Req 25 eventorder
- » [gmpi] Re: 3.8. Events Req 25 eventorder
- » [gmpi] Re: 3.8. Events Req 25 eventorder
- » [gmpi] Re: 3.8. Events Req 25 eventorder
- » [gmpi] Re: 3.8. Events Req 25 eventorder
- » [gmpi] Re: 3.8. Events Req 25 eventorder
- » [gmpi] Re: 3.8. Events Req 25 eventorder
- » [gmpi] Re: 3.8. Events Req 25 eventorder
- » [gmpi] Re: 3.8. Events Req 25 eventorder
- » [gmpi] Re: 3.8. Events Req 25 eventorder
- » [gmpi] Re: 3.8. Events Req 25 eventorder
- » [gmpi] Re: 3.8. Events Req 25 eventorder
- » [gmpi] Re: 3.8. Events Req 25 eventorder
- » [gmpi] Re: 3.8. Events Req 25 eventorder
- » [gmpi] Re: 3.8. Events Req 25 eventorder
- » [gmpi] Re: 3.8. Events Req 25 eventorder
- » [gmpi] Re: 3.8. Events Req 25 eventorder
- » [gmpi] Re: 3.8. Events Req 25 eventorder
- » [gmpi] Re: 3.8. Events Req 25 eventorder
- » [gmpi] Re: 3.8. Events Req 25 eventorder
- [gmpi] Re: 3.8. Events Req 25 eventorder
- From: Tim Hockin
- [gmpi] Re: Reqs final draft
- From: Didier Dambrin
- [gmpi] Re: Reqs final draft
- From: Mike Berry
- [gmpi] Re: Reqs final draft
- From: Didier Dambrin
- [gmpi] Re: Reqs final draft
- From: Mike Berry
- [gmpi] Re: Reqs final draft
- From: Angus F. Hewlett
- [gmpi] 3.8. Events Req 25 eventorder
- From: Robert Fehse
- [gmpi] Re: 3.8. Events Req 25 eventorder
- From: Tim Hockin
- [gmpi] Re: 3.8. Events Req 25 eventorder
- From: Jeff McClintock
- [gmpi] Re: 3.8. Events Req 25 eventorder
- From: Tim Hockin
- [gmpi] Re: 3.8. Events Req 25 eventorder
- From: Robert Fehse
- [gmpi] Re: 3.8. Events Req 25 eventorder
- From: Tim Hockin