[gmpi] Re: Topic 6: Time representation
- From: David Olofson <david@xxxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Wed, 30 Apr 2003 00:10:33 +0200
On Tuesday 29 April 2003 23.55, Tim Hockin wrote:
> > to exclude it. And that's not at all a reason to imply that a
> > plug-in API feature doesn't work reliably.
>
> If you peek ahead, then I change something, your peek-ahead is
> WRONG. I'd call that a feature that doesn't work reliably. If we
> can come up with a robust answer, I'm all for it, but it had better
> handle all corner cases.
Would it be sufficient if this "gimme' some events from the database"
API forbids keeping any data across process() calls? I'm quite sure
it would, but I could be missing something.
However, that isn't the whole answer. Consider a phrase sequencer
that's playing a clip of a few bars while the user is dragging that
clip back and forth along the time line. I think you need to know
more than the current state of the database for each process() call
to get that right.
//David Olofson - Programmer, Composer, Open Source Advocate
.- The Return of Audiality! --------------------------------.
| Free/Open Source Audio Engine for use in Games or Studio. |
| RT and off-line synth. Scripting. Sample accurate timing. |
`-----------------------------------> http://audiality.org -'
--- http://olofson.net --- http://www.reologica.se ---
----------------------------------------------------------------------
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: //www.freelists.org/archives/gmpi
Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe
Other related posts:
