>This is the case I am talking about. There may be audio cross fed between >graphs, but there may be audio running externally to what is nominally >considered the host (or the controller or the workstation from the point of >vie of the user). The plug-in that the user is interacting with (and >controlling via automation in the host) is probably a proxy in this case >(e.g. It is running on the local host, but the process routine is not), and >the local plug-in is responsible for communicating with the remote "host". >The GMPI host thinks that it is talking to a local plug of some sort, but >the processing (and audio feed) may be remote. i think you have either missed for forgotten our earlier discussions on this. we allow proxies, but they get absolutely no special consideration. if we allow per-plugin latency reporting, then proxies that hide latency-bound proxies will have to have a global effect on the overall system latency, which is bad. > The remote timeslice may be >very different from the local time slice. this is unacceptable. the whole point of a sample-synchronous system is that every node in the graph is processing data for the same time slice. if that's not true, the nodes are not part of a sample-synchronous graph, and i consider that to be out of the realm of GMPI. ---------------------------------------------------------------------- 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