thanks guys. got some good ideas and seb replied on the bidule forum too. that guy is the best.
On Wed, Nov 24, 2010 at 4:58 PM, Rainer Straschill
<moinsound@googlemail.com> wrote:
james fowler schrieb:
the dsp monitor inside of bidule reads 30-50% at any given time (depending on number of instruments currently at work) but in task manager cpu usage hovers around 10-11%. is there a way to boost dsp allocation or whatever (dunno if that's even a real thing) so that bidule has a little more headroom? i find that under certain circumstances
One thing I found is that for some reason (which may very well make sense, because in a typical scenario it displays how far you're from interface driver dropouts), some audio programs seem to display the maximum load on a single core, not the averaged load over all cores, as Windows' task manager does.
There is a strategy that you may try to check (on multicore or multiprocessor systems) on which core your audio interface driver is running and then (also using task manager in the "Process" window) keep your audio app (e.g. Bidule) from using that core. Careful with hyperthreading architectures (e.g. Nehalem) - you need to remove them from the entire physical core (which is two cores in the task manager display). Then again, Windows XP generally has problems with hyperthreading architectures (or so I heard)...
Rainer
--
http://moinlabs.de
Follow me on twitter: http://twitter.com/moinlabs