General question about CPU usage and monitoring.
I've got some fairly busy Audiomulch files which I use live. They'd all been working without dramas, but I've just recently started running Native Instruments Guitar Rig on the same laptop which obviously means the CPU is a little more in demand. As a result I've occasionally hit CPU spikes and glitching has begun to occur. That's all fine, I can understand that. I just need to make sure my AMHs are economical.
However, AM's CPU reporting seems to be a little wacky. The usage indicator in the status bar doesn't get above 15%, and yet if I look at it in Activity Monitor the usage is consistently well above 90%. As a result, it's a little hard to see when I'm risking an overload unless I have Activity Monitor open all the time. Is there an issue here, or is there an explanation?
Also - what methods can I use to squeeze the most juice out of my environment. Is it worth changing the AM process priority? Are there things I can do (aside from lowering the sample rate obviously) to improve performance?
I'm beginning to realise I may need to start bouncing out some sounds and using loops for them instead - which is a little bit of a shame, but that's just the way it goes. Any other tips for making sure the files don't go out of control?