New customer to both Abassi and Plini (love em). I’ve noticed that the CPU load for both plugins is HUGE, and behaves strangely. Ranges from 20% to 35% for one instance in an empty session, and changes depending on whether the plugin GUI is open! Weird. Relative to my system’s capabilities, that % massive. I own Komplete 12 Ultimate Collector’s Edition, Serum, and the Arturia V Collection, and the Neural plugins blow them away in CPU usage by a lot. The runner up is NI’s Modern Drummer at 16%, with internal eq/comp/effects active on 9 “mics”/stereo Kontakt outputs.
Forgive the length here, but I tried to be comprehensive. My system is a brand new (3 weeks old) purpose built custom PC by avadirect.com, and more than exceeds Neural’s recommended system specs -
- DAW is Abelton Live 10 Suite, latest version
- Buffer size is 32MB, sampling at 44,100, 32 bit audio in
- 8 core i7 9700
- Gigabyte Z390 Gaming X motherboard
- 64 GB of DDR4 RAM @ 3,200 mHz
- 500GB NVMe boot drive (where the Neural products are installed along with my DAW, currently at 40% capacity)
- 2TB SDD working drive (where my Abelton projects/sound libaries are stored, currently at 40% capacity)
- 6TB storage drive, not used for audio
- Interface is a Focusrite Scarlett 2i2, but that’s not relevant to the issue.
- The only non-OS 3rd party background software running are Malware Bytes, NVIDIA graphics drivers, and the Focusrite driver
- All native windows settings (power, etc) referenced in your articles have been optimized
Given the fresh/more than capable PC and the fact that I have a hard time believing that the minuscule background software I have running accounts for the CPU drain, I think it’s safe to rule out my computer as the cause.
Specific numbers for each plugin below. They were measured in an empty Abelton session after a computer restart with one audio track only for the neural plugin, which is running stereo out with oversampling at normal.
Abassi, with the plugin GUI open inside Abelton:
- Abassi, Gnarly Rhythm (Nolly) preset, reverb/delay on - 22-24%
- Abassi, Gnarly Rhythm (Nolly) preset, amp OFF only - 15-17%
- Abassi, Gnarly Rhythm (Nolly) preset, cab and amp OFF only - 12%
- Abassi, Gnarly Rhythm (Nolly) preset, cab, amp and delay/reverb OFF only - 6-7%
- Here’s the weird part - with the plugin GUI minimized, empty track with no active inputs or recorded audio - Abassi, Gnarly Rhythm (Nolly) preset, reverb/delay on - 2%
- With the plugin GUI minimized, AFTER audio has been recorded - Abassi, Gnarly Rhythm (Nolly) preset, reverb/delay on - 26-28%
Plini behaves almost identically +/- a few %, with one notable exception. On an empty track with no active inputs or recorded audio the CPU usage does NOT drop with the plugin GUI minimized like Abassi does. It hovers around 20-22%.
Both plugins can spike into the low 30% range when messing with mic placement, delay times, etc.
I ran LatencyMon as your other threads suggest, and these are the numbers. This is over my head, so maybe you can let me know if there’s an issue -
In sum, you’ve got some killer plugins here. But, it looks like there may be some room to streamline some stuff under the hood to make them less system intensive. I’m lucky to have a pretty powerful computer so far as an amateur apartment setup goes. Based on how my other plugins perform (including CPU heavy synths), I never thought I would have to start watching CPU usage on this computer with only an amp sim and drum VST loaded. Abassi + Modern Drummer crack into the 40% range. I can’t imagine how someone running these on a laptop with at/just above your recommended minimum specs deals with it.
Let us know if this is a known issue, and if any solution is expected beyond encouraging us to mitigate its effects.