I'm stumped. Any ideas why Recabinet is causing the horrible noise on the second clip:
http://www.box.com/s/iqdz6mk6obx4xt3v3rfr

First section: Revalver with a built-in Revalver IR - no noise.
Second section: Revalver with Recabinet 3.04 64 - horrible clipping type noise.
- Revalver cab obviously turned off
- Devildriver preset, downloaded from here (just to make sure I'm not screwing something up.)
- Same result with any other Recab 3 cab types I've tried

I *thought* this started happening when I switched from an Edirol interface to a Focusrite Scarlett 8i6. But re-tested with the old Edirol interface, same noise.

Troubleshooting steps I've covered:
- Scarlett updated to latest (2012) 2.3 drivers - no change.
- Tried with Recabinet 3.04 64 bit, 3.03 64 bit, 3.04 32bit, 3.01 - same noise.
(It suprises the hell out of me that 3.01 is doing this now. I've used it extensively previously.)

- Tried with Revalver, TSE X30, Guitar Rig. Any amp sim, same results.
- No noise when using Recab 2 impulses with LePou LeCab. It's Recab 3 specific.
- Recording/output levels are not clipping (as the first, noise free, riff illustrates.)

System:
-Intel i5 2500, 8Gb, Win 7 64. (Sufficient CPU juice.)
-Focusrite Scarlett 8i6.
-Reaper 64, tested with the last three versions up to 4.15, all do the same, but only with Recab 3.

Like I said, I'm stumped. Thoughts?

Hmmm. Didn't think so.

One more question: is it possible to use Recab 3 IR's without the interface. The way Recab 2 worked.

Sorry I didn't get back to you sooner. I've tried to recreate your issue (our test system has very similar specs to yours), and I can't. This is a weird one...

What sample rate are you working at? What samples/buffer setting are you using? It's called "Request block size" in Reaper under Preferences->Audio->Device. Make sure it's set to a power of 2 (64, 128, 256, 512, 1024, or 2048) or you will experience sonic anomalies.

PS - we don't offer Recabinet 3 impulses by themselves.

..aaannd it's gone. Just as mysteriously as it appeared. Upgrade 3.1 seems to have fixed it.

3.1 has a totally new audio engine. Also, it's no longer necessary to run your buffer in powers of 2.

Very glad that the issue is resolved!

I did check the buffer setting back in Feb, and was going to reply that it was set to 256, and therefore that wasn't the problem.

But first I re-checked and this time I noticed...a little checkbox in front of the 256, which wasn't checked. And of course checking that little box fixed the problem, even with version 3.01 and all the others. Bloody hell.

Knowing you had the fix all along makes me really happy. Much happier than having the problem fixed but not knowing why - it's all about peace of mind. I'm off to make music!! Cudos mate, respect.