On Tue, Nov 18, 2003 at 07:44:25AM +0100, Vincent Burel wrote: > severe CPU usage (that's relative) or latency are not prohibiting real time > at all ! we really need a field to indicate if the plug-in is made for > real -time or not : > - not real-time because the instability CPU load in the time (this needs 1% > CPU on some audio frame, and 10.000% on other) > - not real time because cannot support the buffer size given by the host > (require buffer multiple of 512 or 1024 samples) > - not real time because the processing needs several pass (analyse, > processing etc... ) Something like that - which the requirement covers, yes? > > > REQ 15 : difficult... > > > > Agreed, but not impossible. The simplest solution could be a single event > > to the plugin saying "you ate too much CPU last time - can you throttle > > down?". If the plugin persists in misbehaving, the host can whack it. > > or disconnect it from the chain... This is mayby the simplest solution. good > idea ! hah. And everyone else wants me to get rid of it, so far :) ---------------------------------------------------------------------- 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