if the CPU load is low, and glitches are occurring then audio processing is being interrupted for too long. there are many things that can cause this.Stromkraft wrote: How is it relevant for the "audio system" that several scenes are launched? Sounds more like a bug to me than something to expect. If you load the CPU too much, OK, but if not? I acknowledge the real time factor, but what is the difference starting up tracks or playing them, you mean?
the discussion on that blog page, which is scraped from another forum, is pretty confused.Stromkraft wrote: That's good thinking on analyzing latency. But you've heard of OS X Developer Tools and Instruments (that Ansolas just mentioned), right? There's some interesting thoughts on this area here in the Ableton Tech Resource blog.
the concept of DPC latency doesn't directly refer to the achievable round-trip-latency, although of course it may affect it. the various Windows DPC latency checkers are used to test a system for interrupt spikes, often caused by badly written drivers, e.g:
http://www.thesycon.de/deu/latency_check.shtml
http://www.resplendence.com/latencymon
i haven't use those OS X dev tools much, but i don't believe they will do the same kinds of tests as the two Windows apps that i linked to above...