First, that isn’t a CPU load meter, it’s the System Performance Meter which looks at the performance of the entire audio system & measures a variety of things of which CPU is only one. So while a CPU problem would show up here, other things can also trigger this meter. I assume if you look in Task Manager you see the CPU maxing out.
Ah thanks for the info, didn’t know that, interesting!
If you think about it it makes sense reducing the sample rate saves CPU. Every point along an audio waveform needs to have its value calculated. When you lower the sample rate there are fewer points along the waveform that need to be calculated.
That was my theory too. In practice I would work barely at where the Nyquist level becomes audible for the ears eg. 16 Khz, save alot of cpu (half the points calculatet in the waveform should mean half the cpu load?) and when bouncing the project I still could go to 192 Khz.
What I’m wondering is if something else in your configuration is causing your CPU to start maxing out. And then when you lower the sample rate you regain just enough capacity to not be maxing out. Can you give us some details about your computer and also what a typical Project looks like - number/type of Tracks, main VSTi’s & plug-ins, etc.
That would be good to know too, and I appreciate the help, but besides of me believing my PC runs quite decent, I’m more interested at the moment in finding the Answer to the sample rate problem.
I was really surprised that I could find NOTHING on the Internet about it, thats why i started this post in the first place.
It seems to me like a great solution for saving computing power. Just Imagine it: twice as much of effects, instruments, busses… anything!
It really is a miracle to me why this isn’t a common technique.
have you tried making the buffer larger?
Yes I tried, but it only works to a certain extend.