Quote:
Found another problem:
Something in the new multiband (* and the declipper) actually causes CPU usage to be higher at 1024 samples than at 2048 samples.
I got on the path to discovering this when I was trying to play PhantomFM's "80's" preset. Even though that preset is set to 1024 samples, and even if I shift it down from "realtime" to "high", it absolutely chokes my system to death. I discovered that setting the samples to 2048 still resulted in stuttering, but less than at 1024.
So, I then decided to try with GAP Impact. I observed the same thing - CPU load actually goes up when set to 1024 vs. 2048.
Then I decided to get away from all the new stuff and use my own preset. CPU load consistently goes down as you lower the number of samples, EXCEPT if you have the declipper on. If declipper is on, the same load increase happens at 1024.
Conclusion: Something about the new multiband AND the declipper doesn't like the lower number of samples, at least on a K8-based system.
Too tired to try 512 right now, but I will later.
I've noticed the difference you mention and also tried with 512 latency and is very similar to 1024.
But what I have noticed is that while the message box remains the "Warning" on the screen, the CPU goes to 100%!
