Recab 3.6.1 Update

[schust]

Anybody else experiencing CPU spikes with this new release?

I first noticed it when my DAW session grinded to halt, completely unexpected, after upgrading. Never had this happen before. When the project first loads the CPU use on a track with Recab is ~1.25% - but can later jump to over 17%. No rhyme or reason why some do and some don't.

win7 64x, i7 4 core, 10Gb mem, Reaper (32x)

 

[hurdy]

Yes I am getting CPU spikes in Ableton Live 8.x
32bit Win7, 32bit Recabinet 3.6.1

 

[Kazrog]

Very strange, sorry to hear this. Nothing I've experienced here, and nothing our beta testers have reported either. I've tested in Win7 64 with the same DAWs as you guys. I'll have to throw some more things at it to see if I can recreate the behavior, but I'm surprised my high track count stress test sessions didn't make this happen.

If you need to downgrade to 3.5.1, you can do so here. You won't lose any functionality; most of what Recabinet 3.6.x is about is getting current with various SDKs and supporting AAX, as well as squashing obscure bugs.

 

[hurdy]

I have just realised that it's that same issue I told you about a while back.
When I have a gate before Recabinet and it silences the sound entirely, CPU spikes pretty bad.
But if I adjust the gate to only attenuate to around -60db, no more CPU spikes occur. Hope this helps.

 

[Kazrog]

That's denormalization, but Recabinet already has an internal noise generator that compensates for that. Perhaps this needs to be increased for 32 bit VST even more so. Annoying - modern DAWs shouldn't allow this to even happen actually...

 

[hurdy]

Yeah maybe I should upgrade Ableton to 9.x and see if that helps too.
I am happy to work with you on this issue if you need more testing done.
Just let me know if you need my email or anything, I can PM

 

[hurdy]

No issues with Ableton Live 9.1

EDIT: Actually, really bad CPU spikes after changing the mic

 

[Kazrog]

PM sent. The cab/mic switching spike is likely denormals as well. I'll conduct some further tests in Live myself and start working on a new build. This needs to be resolved once and for all. Thanks for your help!

 

[Deathell]

I should mention about Recab in reaper. I usually save the whole project and close it but when I open up the project again the external IRs that I have been using has been un-highlighted. Totally confusing guess work just to make sure that I still do remember all of which IR I was using most of the time but when I reinstate this by clicking on the same IRs I have previously used, the sound changed and I'm sure it is not perceived hearing.. has recab gone back to some certain default setting and not saving the last selected IR when I save the project in reaper?

 

[schust]

Shane, if you want me to test any mods for you given I have the situation here, I'd be happy to. Just send me a PM.

@Dethell: this must be a 3.6.1 thing too. i downgraded to 3.5.1 last night and pulled up my project this morning. both my IR location and IR name are listed correctly.

 

[Leevious]

I'm using the latest version of 64bit Reaper as well, Windows 7 64bit, and experiencing issues. When I load up a session, my saved guitar tracks are fine, but when I add another guitar track and load in Recabinet, the default 1960 cabs sound buzzy, and it isn't until I load a different cab pair, that things sound normal again. The difference is night and day.

 

[Kazrog]

I should mention about Recab in reaper. I usually save the whole project and close it but when I open up the project again the external IRs that I have been using has been un-highlighted. Totally confusing guess work just to make sure that I still do remember all of which IR I was using most of the time but when I reinstate this by clicking on the same IRs I have previously used, the sound changed and I'm sure it is not perceived hearing.. has recab gone back to some certain default setting and not saving the last selected IR when I save the project in reaper?

When you open the plugin, the current IR should be shown in the filename field, even if the highlight isn't showing up properly. This is a known issue and will be looked into, sorry for any inconvenience.

Rest assured, the IR that you selected last when the session was saved will be loaded properly every time.

 

[Kazrog]

I'm using the latest version of 64bit Reaper as well, Windows 7 64bit, and experiencing issues. When I load up a session, my saved guitar tracks are fine, but when I add another guitar track and load in Recabinet, the default 1960 cabs sound buzzy, and it isn't until I load a different cab pair, that things sound normal again. The difference is night and day.

Possibly a sample rate issue, I'll try to recreate that. Recabinet has methods in place to guess the current session sample rate if a host is evil and doesn't want to share that (incredibly critical) information sometimes (an issue I've never seen in Reaper, but a very popular host that shall remain nameless did have this issue for years, until recently.)

What sample rate is the session in, incidentally?

 

[Leevious]

Sessions are in 96k, Recabinet worked great prior to this last update.

 

[egan.]

I think it's worth noting how insanely on responsive Shane is. In a world where empires with huge dev teams ignore major faults for years he's totally on it.

 

[Deathell]

I'm using the latest version of 64bit Reaper as well, Windows 7 64bit, and experiencing issues. When I load up a session, my saved guitar tracks are fine, but when I add another guitar track and load in Recabinet, the default 1960 cabs sound buzzy, and it isn't until I load a different cab pair, that things sound normal again. The difference is night and day.

This is exactly what I meant by saying it doesn't sound like it should when I load up a saved session. Usually the highs became more fizzy or buzzy like you have experienced and when I reinstate it by selecting the same IRs that I have worked with, it would then sound normal again.

When you open the plugin, the current IR should be shown in the filename field, even if the highlight isn't showing up properly. This is a known issue and will be looked into, sorry for any inconvenience.

Rest assured, the IR that you selected last when the session was saved will be loaded properly every time.

Thank you Kazrog, please make further investigation onto this issue above and having the highlighted IRs show up properly would be more helpful. I usually try out so many IR combinations, layers, quad tracks and I need to be able to see what I have in store.

 

[Kazrog]

Thanks for the kind words, Egan! I'll have an update for you guys next week.

 

[drew_drummer]

Annoying - modern DAWs shouldn't allow this to even happen actually...

Wait until you start trying to sync LFO's to the host clock!!

 

[Leevious]

I second Egan's statement. Fantastic, personal customer service.

 

[Kazrog]

OK, I've posted a quick beta build of Recabinet 3.6.2 for Windows VST to the list, which should fix the CPU spike issues you guys are having - but I may as well share it here as well for anyone who's interested. These are direct links to the DLLs themselves, so you'll have to manually install into your plugin folders:

• 32 bit VST
• 64 bit VST

Please let me know how this goes for you. I'm following this thread so I'll know if you post feedback here. Thanks for helping out!