>>> OR the host ensures that B runs before A and C, since there is a dependancy there. Now, if there is a circular dependency ANYWHERE, you have a latency problem. Therefore, this reduces to a previously unsolved problem. <<< But A must run before B, because it lives upstream from B. A's output is consumed by B's input... -----Original Message----- From: Tim Hockin [mailto:thockin@xxxxxxxxxx] Sent: Friday, February 06, 2004 9:41 PM To: gmpi@xxxxxxxxxxxxx Subject: [gmpi] Re: Reqs 3.9. Time - opening arguments.1 On Sat, Feb 07, 2004 at 03:35:53PM +1300, Jeff McClintock wrote: > Latency. Before a plugin processes a block, all it's events must be > qued up, that includes tempo changes. > > Plugins are processed in order 'upstream' to 'downstream'. > > [A]->[B]->[C] > > If plug B changes the tempo, there are two ways the host can handle it : > > - Host can change the tempo map immediatly, in which case C receives > the new tempo, but A will have already used the old tempo. > > or > > - Host can propogate the tempo during the next 'block', all plugins > receive consistant tempo info. > > Neither case is ideal. Either A and C see different tempo changes > during the same song, or all tempo changes are lagged by the graph latency. OR the host ensures that B runs before A and C, since there is a dependancy there. Now, if there is a circular dependency ANYWHERE, you have a latency problem. Therefore, this reduces to a previously unsolved problem. ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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