Quote:
Quote:
Are you sure that it's not one of those Task Manager jumps? I could probably just as well limit the bass clipping at 6 steps, but it _really_ should not make much of a difference (like at most 2-3% of the total clipping CPU load - that's what I'm measuring here).
I'm as unsure of it as I was unsure of it the time I brought this up and you added the "Take some shortcuts (CPU)"...
...and the time after that when I brought something else up and you made an optimzation (I can't specifically remember what that one was, and I don't have time to look right now).
Until you own a CPU with 1MB cache (per core) and test on that limitation, and perhaps more significantly, an AMD, we're going to have these "you sure it ain't Task Manager" situations... :sigh:
I know... But this time it really doesn't make sense. What I did is add a loop like this:
FOR i FROM 0 UPTO 5
DO something;
Now you say that at '5' (6 steps) it takes almost no time, but at '7' (8 steps) it takes a lot of time. That really doesn't make any sense. 'something' doesn't suddenly use more memory if the number of repeats is increased, and the 'strict bass clipping' CPU load should rise by 8/6th. -> 25%. But since you say that at 6 steps it's not much higher than without strict bass clipping, I don't get it anymore...
I'll create a version where the number of steps is limited to 6, then we can at least see if it's the bass clipping or the total clipping filter that responds to the increase. Will post something later today.