Finally switched from Winamp back to Foobar (used Winamp for some time as earlier Foobar crashed very often, deleting configs).
Nevertheless my turn back (from 0.6 yo 0.7 RC4-13) was darkened by one thing: Foobar CPU usage became incredible big.
Don't tell me about DSPs, resamping, etc... I switched all this stuff off at the very fist minute. One of main CPU consumers was foo_looks plugin (formaly foo_WSGUI), gettin whole 30% of it.
next, after leaving only native in, out and GUI modules it still wastes 15 to 30% for playback. Damn, my plugin overloaded Winamp needs only 5-10% for the same. IIRC 0.6 needed twice less, than Winamp.
Is there something wrong with new Foobar? it's getting really annoying :\

Please post full system specs and configuration (including dithering, output mode, etc), list of loaded components (dll files in component directory) and foo_null speed test results.
Sounds like you have the habit of installing all sorts of weird components first, then saying "omg my player uses a lot of CPU and crashes".

What kind of CPU do you have?

Thanks, Peter.
Damn, who turned this dithering on? :\
I didn't see this option before...

btw, does foobar load plugins into memory on loading or only when needful plugin is activated?

Thanks again: 6-10% on Celeron 333 is quite OK for me.