On Oct 1, 2004, at 4:08 AM, rhgkswhd wrote: > Stefan Garr <stefangarr@c...> wrote: > >> ok, sorry. My guess is a bit vague, but I do monitor the coreaudio >> user group, and I know that there are going to be some changes in >> CoreAudio. No, I don't know exactly what. However, I guess I assumed >> that building a structure to correctly compensate for all plug ins >> would probably be best accomplished at the operating system level. >> Since Apple is the only pro audio developer that is completely privy >> to >> its plans at both the application and the OS level, I assumed that if >> the "fix" is coming at the OS level, it naturally has to occur on the >> next OS upgrade cycle. >> >> So yeah, it's a vague guess with a tiny little bit of logic thrown in. > > Wouldn't it be the AU plugins report their latency to the host and > Logic, the host, calculating the biggest latency and making all the > other equal to that latency? What would an OS level implementation > bring that isn't available on other applications (cubase, nuendo, > samplitude, dp, etc) to Logic? Exactly. I am not a developer but I am pretty sure that whatever the implementation is in the end it will have nothing to do with system level stuff. in fact on a technical level it is not even difficult to manually set up the current environment to do delay compensation. On a practical level it is is certainly a huge hassle because you have to set all the delay values manually and I certainly wish it were done automatically. I do think there should be delay compensation implemented on auxes and busses ASAP but I do not necessarily see it as quite the overriding issue a lot of people make it out to be. I also sometimes wonder if some of the people who are shouting for it are not understanding that it will not help at all for live instruments when those instruments are routed though auxes and busses with any effect that produce latency.