Well now, that scares me, cause my comp is no where near that powerful. I have dd3 ram at 16 gigs but my processor is wayyyy under powered.
Hopefully they can work a way to make it load a little less.
Or put everything in a suite like superior drummer and let us cache things we dont need at the moment
I can run Cali on my system fine (Cubase Pro 10.5, 9900k, 32gb RAM, Windows 10), but at present it is using much more CPU for the cab than would seem reasonable. One instance of Cali with two mics on, no pedals, and normal oversampling takes about 10-15% CPU, compared to negligible CPU usage for Plini and Nolly with equivalent settings. Removing the Cali mics reduces the CPU usage to approximately the same negligible level as Nolly and Plini. As christopher.mccella said, importing IRs didn’t help. And it’s the same for both VST2 and VST3 versions.
I notice that reported latency of Cali in Cubase is just 6 samples, compared to 50 and 55 samples for Plini and Nolly. Might this low latency be giving the IRs problems?
@Gonzalo, I’ve tried disabling Intel Turbo Boost in the UEFI, seems to help a lot. The plugin is still a bit heavy on the CPU when cab section is activated but there’s no more CPU spikes, way more stable. I tested this in a blank Cubase project. Buffer at 128. Two audio tracks both with Cali (oversampling:high, two mics activated) + a send with some delay and reverb. Real time CPU meter in Cubase is stable and stays around 35% I would say. I’ll test in a full mix project tomorrow.
Ufei. Can you tell me what that is? (, total noob here)
When you restart your computer and you press F2 before windows boots. I guess I should have said BIOS.
@charlesalexandrebeau Thanks for the update! That makes sense. Constant CPU frequency changes usually hurt the real-time performance of the system. We’re still investigating the problems related to the cab sim.
Ahhh. Ok. That makes sense. I’m going to try that
I too am having these issues. Cubase 10.5, 9th gen i7, windows 10, blah blah blah. if i run the plug in mono, it seems to run better, but the moment i switch it to stereo, or try to use 2 mics, cpu overload to the point that it’s making my whole project skip, and i’m only 5 tracks deep. i don’t remember it doing this when i first installed it. could this be a windows 10 update issue? please help! 
if need be, i can set up the video rig (it’s a pain, but can do), and make a video of what it’s doing
post script: after going back to cubase and comparing it with Nolly, even in mono it’s using up WAY more cpu than Nolly…and it IS maxing out my CPU…just not as often, so i didn’t notice it. 
I know these programs as a whole run a ton of cpu, but this program is especially bad. It makes it unusable for me. I want to buy, but not until I know there’s a fix
3 Likes
Hello!
It’s been a Month since Cali release, and although it’s great, specially the cab section, it’s very hard to use inside a DAW due to it’s massive cpu consumption. I can’t do any AB comparisons inside the mix because I have to freeze the tracks in order to playback the project. This happens with only 2 instances of cali, when I have projects that used many more instances of Nolly, Omega, or NTS.
It would be good to know how close you are to fix the problem, (nothing yet, beta testing, 1 week, 1 month, 1 year?).
It’s a pity to have such a game breaking bug.
Thanks.
4 Likes
I have the same issues described on a Intel 10600 I5 z490i Apollo Twin Thunderbolt card 16 GB 3600 Mhz corsiar dominator ram. When in standalone it cuts out audio for no reason and i can press “reset” it then comes back but it can cut out again after 2 sec. In my daw S1 it uses up all the daw CPU power on only 2 x Cali and 1 x parallax. So yeah, it would be great with a update soon please.
1 Like
As everybody, I love Cali but it’s clearly useless in a DAW (Studio One in my case).
I think about returning to an hardware solution and be not CPU-driven anymore when it comes to record some guitar tracks.
I purchased 3 of your plugins, but I begin to regret that.
1 Like
agreed. massive increase in price for the products, no real solutions for this problem
it’s 2021 … and so far no update from May 20, 2020 …
1 Like
Is there a pending update for Cali Suite to address this problem?
hi did you resolve your c pu issues ? ive only just started using nameless this last month ,when i play the cpu goes to about 23% when i record and play back ,man it goes to 65 then jumps to 90 % just wondering if you have any tips you can share …I am running a mid 2015 MacBook pro 16 gigs ram 2.6 processor
I honestly did not because at that point I assumed it was my computer and built a new one haha.
These things tend to run pretty hot. Mostly due to the quality of the captures and such.
I had also jumped to the gojira plugin as they optimized that one I a bit. I’m unsure if they’ll do that with cali as it’s a bit older.
Best bet, high power CPU that’s able to run all the memory needed efficiently
ok cool thanks for reply ,so your fix was to build a computer with more powerful cpu, thats cool …i guess there is no other tweak to do than that ?as i tried all the optimisations for macs i guess i gotta buy a new mac ?I wish neural dsp would upgrade the advertised specs needed to run these plugins as my current mac is well within the required specs advertised as needed to run the plugin ,but i just simple can’t use it as it craps out my CPU within minutes
It could also be your daw is taxing the cpu. Any other plugins may be doing it. May need to freeze channels or mix any midi tracks down to audio as you finish them to help save on cpu.