On Tue, 1 Apr 2003, Tim Hockin wrote: > > > If we want to explore that route, how about a 1-call per event target per > > > timeslice method. > > > > The problem that I see with that is that the plugin needs to be rendering > > in order to get any events. What if rendering is currently stopped, but > > Well, plugins should be rendering all the time, anyway, right? No. Why do you say that? Maybe you are a more efficient musician than me, though, you never stop recording or playing back audio... ;) > But that aside: load_preset, plugin->process(0 frames). All events get > handled immediately. Ewww, kludgy. Not to mention that it also precludes doing any events when the plugin is in a less-than-fully-created state (yes, that's a topic in a later point, but since I know that I definitely wanted to see multiple stages of creation and readiness for plugins, this is important to me). Marc ---------------------------------------------------------------------- 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