Make sure you choose a buffer size that's a power of 2 or you will have problems with Recabinet (64, 128, 256, 512, 1024, 2048.) Lower buffer sizes will give you less latency but will put more load on your CPU. Higher buffer sizes will give you more latency but keep a lot more CPU headroom available.

The sweet spot will depend on what you are doing (tracking or mixing) and the overall horsepower of your hardware. Cheaper audio interfaces will force your computer to work harder also. There's a big difference in performance and sound quality between M-Audio and RME for example.

Thanks for the answer Kazrog, but what i really needed to know was which buffer of reaper in particular in i should mess with. There are disc read buffers, fx pre process buffers etc.. i just wanted to know which one i should give more enfasis on the teaking

"Request block size" under Audio->Device in Preferences is what I'm referring to when I say samples/buffer. Make sure it's set to a power of 2, as I said before.

Hi again and thank you once again.

I thought it was that value, but i did not see great gains when i changed that one. however im going to tweak it further now.

I solved the issue of the pops, with the option of enabling realtime FX processing which was turned off now everything works just great

Thanks for the help and sorry for being a nuissance:P

No worries, Reaper can be really confusing, even if you're already familiar with other DAWs.

I wanted to post a separate thread but I'll do it here since it's the same subject. I too have serious CPU consumption issues on my intel i5, Win7 64bit and 4GB RAM. Recabinet 3.0.4.

Buffer size is 256 and like that Recabinet weighs in at about 28% consumption on Ableton Live (32bit). In Renoise 64bit it's marginally better but still huge at about 21%. Needless to say this is not really acceptable to work with. Especially in Live, any elaborate other effects cause overload way too soon.

To test, I used two instances of a MeldaProduction Multiband Convolution with a Recabinet IR in each and CPU usage was at under 8% in Ableton Live. Another test involved the quad IR convolver from Kouassa Amplifikation One with four Recabinet IRs and CPU again was at a mere 8% in Live. Same if I use the Control Room Pro from Guitar Rig. 8% is about standard with two cabs, but even loaded up with more than two speakers I'm only at about 10-12% CPU in Ableton Live (versus 28%).

If I put an EQ on each channel I may get it up another 2%, but that's still a 300%+ higher consumption of Recabinet over comparable setups. And Control Room Pro sounds pretty good at its 8% CPU.

I'm afraid I can't perform or even work Live with Recabinet Windows VST in it's current state because the CPU load of Recabinet alone makes my setup suddenly CPU sensitive. I kept hoping for newer versions but apparently 3.0.4 is what it will be?

We're currently beta testing a new version with a rewritten core that should significantly address any remaining CPU issues in Windows. Sorry for the inconvenience.

Thanks, that's a relief!

If you'd like to beta test Recabinet 3.1, there's a public beta page I've set up for those who are interested:

http://www.recabi.net/recabinet-3/download-demo/recabinet-public-beta/
password: recab31

This version introduces a completely rewritten audio engine that provides more efficient CPU utilization, as well as improved sound with better dynamic response. Additionally, the keyfile importer now has a dialog indicating successful registration, and instructs the user to restart their DAW.

You may need to adjust your presets due to the aforementioned sonic improvements, but don't worry - Recabinet 3.1 will reside on your drive separately from previous versions of Recabinet 3.0.x, so you can use both versions simultaneously.

Please write back if you discover any bugs, and describe them in detail. Thanks!

I missed the beta but 3.1 is now much improved. 20% CPU in Ableton Live (down from 28%), 15% in Renoise 64bit (down from 20%).

Still not quite the 8% of Control Room Pro and others, but it's in an acceptable range now.

Thanks for your efforts!