Make a video and send to [email protected], only that way things get fixed !

 

Agree but in a system like @Daskeladden it should not be happening. There has to be something else causing it. He should not have to be using such a large buffer size for this synth.

 

@Daskeladden It also happens here. Which DAW do you both use ?

 

Are you asking me or @Daskeladden? When you said, it also happens here, did you mean that the same thing is happening to you? If that is the case, what are you running? For comparison, let me say this one more time. I got it down to 48k and buffer size 64 with an old i7 @2.10GHz. Laptop that belongs to a friend. She uses a Focusrite 18i20 MKii which are know for not having the best drivers. She is running Windows 7 Lite with some updates. She uses FL Studio and Bitwig.

 

I have a little tip for you "Avengers". I wasn't impressed by its CPU usage when its GUI is open either, so I experimented with different things. I discovered that changing the skin to Chrono_Jade skin by SatYa lowers the CPU usage a bit. Probably because it's less demanding on the graphic FX, I like that skin, actually, and it's my default. It seems that Avenger's GUI is taxing the CPU too much, depending a bit on the ASIO buffer, too. I have my ASIO buffer at 256 samples, which is low enough for my needs. Also, CPU usage somewhat depends on what pages you have open in Avenger. When you close the GUI, you get the real CPU usage, which is not that bad, even on older computers.

Cheers!

 

I'm using both Ableton 10.1 and Cubase 10.0.30 the issue happens in both. I have uninstalled everything so I cannot test it any further. Some of the presets worked fine others like St Chambers Strings spiked like nothing else I have. Just opening that presets Cubase 10 audio performance real-time peak meter raised to over 50% and stayed there. That was before even touching the midi keyboard. So something is not right
Could be that this guy suffers from the same issue:

Strange that it could be that individual and random. And both on Windows and Mac. My only conclusion (like also SineWave mentioned) is that it has something to do with scaling and the GUI. I'm using a 4k monitor, but I also tried it in 1080 hd but same issue, but still think it's related to GUI

 

Last edited: Aug 10, 2019

You both, I was replying to your post and added @Daskeladden

I even get those CPU spikes with closed GUI, in Logic X and Studio one at any buffer size. @ 1024 it dosen't spike 100% but it spikes.
Here Studio One 4.5.2 @ 128 samples. It is definately Avenger related since ANY other synth works as expected:
http://sendvid.com/beteew3j

 

I recommend you use a "decent" graphics Nox Vidmate VLC card. I use a Radeon HD from 2013 and don't have problems

 

Last edited: Aug 13, 2019

Look at my signature I can play 4k games. So a decent graphic card is not the problem

 

I7 4790k running stock clock freq. No issues. Scan you PC for malware..

 

Try it with Reaper and with and with out the the windows GUI stuff turned on. Reaper doesn't need the eye candy to run.

 

6 years old i7 at 3.7 Ghz, 8gb corsair ram , Win 10 x64, no problems here.. had 10 instances running.. if I had any problems I would sound design then simply render my DAW is Studio One 4

 

Last edited: Aug 13, 2019

Here i tried more than 20 and CPU usage is around 15% to 20%

 

Again it is not about the overall CPU usage , it is about the nasty CPU spikes which you get with some presets eg: St Chambers Strings

And again, it is NOT GUI related, and doen't have anything to do with malware:

http://sendvid.com/beteew3j

This is the legit version running under macOS Mojave and Studio One 4.

Avenger is the only Plugin which creates such CPU spikes so it is NOT my Mac

 

Beyond all the hype Avenger seems more of the same, not necessarily a bad thing. My MacPro is old, 5,1. The graphics card could be the issue with the spiking I guess. To be fair I don't see these spikes on a Mojave laptop

 

Last edited: Jan 20, 2020

Don't waste any time on this plugin. Pretty crappy if you ask me. I just uninstalled it and never looked back

 

Try disabling Hyper-threading in the Reason settings (and also, if it doesn’t help in the computer BIOS). On some systems with separate plug-ins, the operation of this option can cause similar problems.

 

On the basis of these spikes I'm deciding against Avenger. On OSX I've found that plugs that do this sometimes take Core Audio with them when they exceed the buffer (or whatever they're doing) and then a reboot of Logic Pro X is needed, pain in the butt

 

I compared the performance now with Windows more into depth, and it looks like Avenger works better under Windows.

 

I need help too, ASAP !
I just have installed fresh Windows 7 and Windows 10 dual boot on same machine, and every time i load Avenger in Cubase no matter which OS, it is getting slow and once i open GUI it makes Cubase frozen and unresponsive.
One instance of Avenger takes more than 1.2gb of RAM, which on previous system installation that was not the case and was everything was working perfectly fine.
Same drivers, same hardware, same OS, all the same but Avenger.
Now i have noticed that when i open Cubase with Avenger, suddenly it need and uses more to much power supply , it makes very high, like goes in HEAVY RED... IDK, where exact is the problem?
Alongside i have installed it on "ruined" laptop with HDD, and it is working perfect....
Since it was working fine on previous system and it was very fast, it is big part of my all projects and now all of them are depending on one single plugin, which happen to be not working !

I guess problem is related to graphics, because even if i manage to load plugin and not to get frozen in Cubase, every time i move the GUI, it gives me nasty glitches in interface, and after some point get crash.GPU related i have already done everything with drivers , updated, reinstalled,even the CPU and mobo drivers reinstalled, but no luck whatsoever.
Have someone experienced same or similar problem?
There is a lot of online talking about this issue, but no one gave a solution, even some legit users didn't got a proper support from the developer, why is that?

All other plugins are affected but that is not noticeable, Jbridge is often getting crashed...