JaredV@... writes: >I have been messing around a bit with hyperdraw to control volume, >panning, etc. In particular, I have been trying to figure out what >latency issues might exist. Looking back through the archives I see >lots of questions and complaints about hyperdraw and latency as it >pertains to the native audio engine. What about TDM? I did a bit of >testing and it certainly isn't perfect, but it isn't anywhere near as >bad as it sounds from the messages. Aside from trusting my own ears >(and eyes), is the latency issue associated with hyperdraw much >alleviated (to the point of usability) on TDM hardware? Or once I get >into the real world (as opposed to my quick tests), is it going to break >my heart? Automation latency with TDM (or even the lowly AudioMedia II or III or Session 8 or PT Project) is inaudible. In fact, stick a volume node of zero one measly tick before the first audio sample, turn up the volume for that track, and you won't get a sneak "click" when the SPL passes that point. Some folks had complained that if you put the volume node exactly at the first sample then you will hear a "click". If that first sample is at the beginning of the region, then simply use a 5ms fadeup (you know, those green fades that are completely independent of the volume?) The automation latency with many native systems has two seperate problems: 1) Delay. If this were the only problem, then it could be sort of fixed by negative-delaying the automation. 2) Slew. This is much more serious. The automation can't change from one value to another quickly enough. f-erenc "Fix signs"