There was CPU hit? I have a CPU from the last century, and still not a major hit. Plus it does have a fully routable signal path, including independent feedback paths, which has to be more computationally intense than a regular delay.hlmst wrote:omg with such a cpu hit, is there a point?
I mean it's just a delay with a few filters...
Audio Damage Ronin preview
-
- KVRAF
- 12235 posts since 18 Aug, 2003
-
- KVRian
- Topic Starter
- 515 posts since 18 Jan, 2004 from PHX AZ
What CPU level are you showing, and with what system? All our testing shows lower CPU usage than similar plugs (Filterscape, PSP Nitro, FilterVST) on every system we or our testers have tried. This is what we aimed for, and achieved, to the best of our knowledge. I'm definitely concerned if you're not getting similar results.hlmst wrote:omg with such a cpu hit, is there a point?
I mean it's just a delay with a few filters...
On an Athlon64 3000+ (which is my development system) I show 3% to 5%, depending on the routing. On a 2.4gHz P4, I get similar results. On a reasonable quality G4, it will be a little higher. On a low quality G4, the hit can be extreme. (On my 1gHz iBook, I show between 15% and 20%.)
As was mentioned, different routings will show different CPU results. Some of the blocks shut down when they aren't routed. Others do not. The highest possible CPU usage is a stereo routing of both delays to both filters to both saturation stages to the outputs. Any routing beyond that won't change the CPU at all.
Chris Randall
Audio Damage, Inc.