Y’all might remember the switch in my motherboard and how much difference it made. I was only testing on V3.3 and MME at the time. Anyway, I ran the same song with the same devices in V4.
P4 - 3.2 ghz - 1 gig memory (Soyo Dragon2 V 1.0)
WinXp Sp2
n-Tracks V3.3-1516
10 - 24 bit stereo tracks
5 - 24 bit mono tracks
13 plug-ins - not counting built-in EQ, which is being used on most tracks
2 - Aux returns being used
4 subgroups
Output to the Layla20 in MME 16 bit mode (Gina24 and onboard C-Media – MAJOR YUCKO – are enabled and working, except in the case of the C-Media working is relative. It audibly clicks when a CD is placed in the CD or DVD drive.)
n-Tracks V3.3-1516 (no master EQ at all)
– PIII 750 mhz 512 megs ram: ~60-70% total
– P4 3.2 ghz - 1 gig ram:: ~8% to ~9% total
n-Tracks V4-1696
– P4 3.2 ghz - 1 gig ram:: ~27% to ~30% total (master EQ open w/freq analyzer on)
– P4 3.2 ghz - 1 gig ram:: ~12% to ~14% total (master EQ open w/freq analyzer off)
– P4 3.2 ghz - 1 gig ram:: ~6% to ~8% total (master EQ closed)
There are blank areas, waves with zeros, and the end fades. My guess is that this may not be the floating point problem. It sure could be, but if it is Flavio has found a way to work around it in V3.3, and should be able to eventually do the same in V4. Fade in out definitely doesn’t spike the CPU the way it use to in the V4 build I currently have (emailed to me to see if a song loading problem was fixed - it was).
While the P4 does bump up to 80 bit math for floating points, that might not be the only thing causing this…whatever it is.
Anyway, closing the EQ window altogether seemed to avoid the problem completely for me in V4.
Yes, it is the EQ window for sure on my machine, but Mine goes into the nineties everytime I open it. I only have a P4 1.7gHzwith 800 ram but I am usually using ASIO though Ihave tried it in WDM as well. It’s possible it’s my video card, I’m not sure though others are reporting similar problems.
I take that back. I just loaded one 24bit track into N, hit play and opened the EQ window. CPU 76%. That’s way too high IMO for one track with no effects or anything.
Blessings, Terry
Yes, it is the EQ window for sure on my machine, but Mine goes into the nineties everytime I open it. I only have a P4 1.7gHzwith 800 ram but I am usually using ASIO though Ihave tried it in WDM as well. It’s possible it’s my video card, I’m not sure though others are reporting similar problems.
I take that back. I just loaded one 24bit track into N, hit play and opened the EQ window. CPU 76%. That’s way too high IMO for one track with no effects or anything.
Blessings, Terry
v4.0.1 build 1698 has just been posted which is supposed to fix this.
So why is Flavio the man? I haven’t made the jump to 4.0 yet, but anyone who has, let us know if this build does indeed fix all the problems.
I will DL it as soon as I get home.
Blessings, Terry
I’ve also been having CPU consumption issues om my P4(m) with the latest versions of 4.0, in the EQ plugin and other places. I’ve been lurking, waiting to see if it gets fixed.
I just downloaded 4.0.1, and I’m happy to report, my problems have vanished.
Thanks, Flavio! 
Yep, that did it. Problem solved!
Thanks Flavio.
Blessings, Terry
[Handel’s “Hallelujah” plays in the background]
Oooooohh…it may be time to pop for the upgrade…you guys are killing my wallet! 
TG