--- Tim Hockin <thockin@xxxxxxxxxx> wrote: > > First of all, it can be very inefficient. It requires the plugin to > > always create all of the resources that it would need for maximum > > number of channels that it might process. Take for example a > > super long delay. If it can provide up to 10 seconds of delay, and > > you're dealing with 96 kHz, and it can handle up to 8 channels, > > you're talking about allocating 30 MB just for the delay lines. > > And that's regardless of whether the plugin will be processing > > 1 channel or 8. > > nah, too complex. Now you've lost me. What are you referring to as "complex"? > I'd say one of two things for this case: > > Plugins should have loadable sub-units, with the I/O. The plugin in > this case would have 1 I/O or 1 pair of I/O per unit. When you load > a unit, you get a new I/O to connect. > > Not mutually exclusive to that, the plugin knows if an I/O is connected > or not. If it is not connected, don't allocate. When it is connected, > use a background thread to do the allocation. Both parts of this proposal are what I would describe as very unecessarily complex... Marc __________________________________ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com ---------------------------------------------------------------------- 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