VPS Avenger 2.4 [RELEASED - FAQ in OP]

[Bla28]

I really have no rational explanation, why you guys at vengeance are not addressing these issues… is this some kind of “works on my pc” thing? Or is nobody in your team responsible for such work? Why not temporarily hire another experienced dev, e.g. Uhe or so?

Yeah ....

[Atlatnesiti]

Also Cubase has some special buffer techniques AFAIK which no other DAW uses

Interesting post, and you might well be on to something here. I've had no issues with Avenger, but I exclusively use it in Cubase with ASIOguard on.

That said, most people with issues do seem to be on Macs. Does anyone have this spiking as a major problem on Windows?

I don't think it is Mac platform related.
After updating to version 2.03, I don't see any CPU spikes at all
I have played many different patches for past 2 hours and CPU meter didn't go past 7%.
That is on Mac mini PRO with M2 12 cores and 32 GB RAM and 1TB SSD
Tested in Logic, Cubase 13 Pro, Ableton 11 Suite and Reason 12 and all of these DAWs returned the same result - NO spikes and very low CPU usage

[noiseboyuk]

I don't think it is Mac platform related.
After updating to version 2.03, I don't see any CPU spikes at all
I have played many different patches for past 2 hours and CPU meter didn't go past 7%.
That is on Mac mini PRO with M2 12 cores and 32 GB RAM and 1TB SSD
Tested in Logic, Cubase 13 Pro, Ableton 11 Suite and Reason 12 and all of these DAWs returned the same result - NO spikes and very low CPU usage

Interesting.

So it sounds to me like one of those very slippery issues that doesn't have a clear common factor. I've been chasing a problem with the Omnisphere gui for many years - only a month or so ago could Spectrasonics reproduce it, and so begin to address it. Full credit to their support team for persevering.

There's two equally bad responses here. First - no problem here mate, it must be you - shut up. Second - the developer is lazy and stupid, everyone has this problem except them. The reality is Three - it's real, but extremely slippery and hard to track down.

I'd hope that Rene can start to work more intensively with one or two users who have the problem. But the breakthrough in Spectrasonics' case came when they had a machine that could demonstrate the problem. And that's out of everyone's hands.

[msvs]

some seem obsessed with spikes.
Short spikes will always be there, since on generation of a sound after note press, there are some parameters to be initialized. The sound/cpu is on hold until this is is finished (just a fraction of a second). The Asio buffer size determines how much time you grant the processor for this task. If buffer is too short or your cpu too slow for that timewindow, it will conflict.
So on most machines you wont even notice. Afaik Hanz has one of those rare machines, where you seem to notice. But unless you bring us your machine, I guess Rene has no idea, why that is the case.

[Atlatnesiti]

Don’t know where to post anymore…
2 seperate threads about the same thing..
Can we join them into 1 please…

[Atlatnesiti]

What’s going on here?
Don’t know where to post anymore…
2 seperate threads about the same thing..
Can we join them into 1 please…

[noiseboyuk]

What’s going on here?
Don’t know where to post anymore…
2 seperate threads about the same thing..
Can we join them into 1 please…

2 separate posts about the same thing in the same thread...

Pretty simple. Avenger 1 is the other thread, Avenger 2 is this one.

[Bla28]

some seem obsessed with spikes.
Short spikes will always be there, since on generation of a sound after note press, there are some parameters to be initialized. The sound/cpu is on hold until this is is finished (just a fraction of a second). The Asio buffer size determines how much time you grant the processor for this task. If buffer is too short or your cpu too slow for that timewindow, it will conflict.
So on most machines you wont even notice. Afaik Hanz has one of those rare machines, where you seem to notice. But unless you bring us your machine, I guess Rene has no idea, why that is the case.

Some of you are obsessed with spikes? The plugin is broken, it doesn’t work.

I can run Davinci Resolve where I edit a full blown 4K music videos for YouTube while at the same time Logic Pro is running in the background with a fully loaded project loaded and not a single audio crackle happens as long as I long as I don’t use Avenger.

It is not a buffer setting or an other parameter setting that is causing the problems, it is the crappy plugin.

And I am not sending my 16” M1 Max MBP to you guys. You guys just need to have better testing in place like every other software company to catch bugs like this.

[aMUSEd]

some seem obsessed with spikes.
Short spikes will always be there, since on generation of a sound after note press, there are some parameters to be initialized. The sound/cpu is on hold until this is is finished (just a fraction of a second). The Asio buffer size determines how much time you grant the processor for this task. If buffer is too short or your cpu too slow for that timewindow, it will conflict.
So on most machines you wont even notice. Afaik Hanz has one of those rare machines, where you seem to notice. But unless you bring us your machine, I guess Rene has no idea, why that is the case.

Sorry but I am getting this too. It is not connected to initialisation of params, it is happening even when I am doing nothing. Here is Logic, I am not playing a single note, it is spiking to 100% every second or so, which is causing clicks.

https://www.dropbox.com/s/fel6meemhjlpo ... 1.mov?dl=0

This is on Mac M1 Studio Max with 64GB Ram and buffer at 128 but even with it at 512 I still get the spikes

Also not just seeing this in Logic so it is the plugin not the host and also not just the AU version so this is something fundamental to do with the synth engine not plugin format

[Bla28]

some seem obsessed with spikes.
Short spikes will always be there, since on generation of a sound after note press, there are some parameters to be initialized. The sound/cpu is on hold until this is is finished (just a fraction of a second). The Asio buffer size determines how much time you grant the processor for this task. If buffer is too short or your cpu too slow for that timewindow, it will conflict.
So on most machines you wont even notice. Afaik Hanz has one of those rare machines, where you seem to notice. But unless you bring us your machine, I guess Rene has no idea, why that is the case.

Sorry but I am getting this too. It is not connected to initialisation of params, it is happening even when I am doing nothing. Here is Logic, I am not playing a single note, it is spiking to 100% every second or so, which is causing clicks.

https://www.dropbox.com/s/fel6meemhjlpo ... 1.mov?dl=0

This is on Mac M1 Studio Max with 64GB Ram and buffer at 128 but even with it at 512 I still get the spikes

Also not just seeing this in Logic so it is the plugin not the host and also not just the AU version so this is something fundamental to do with the synth engine not plugin format

This is also my experience with Avenger. Changing buffer settings doesn't help at all, so it's the fundamental problem of the plugin itself.

Only Avenger does this.

[noiseboyuk]

Only Avenger does this.

Manuel, I think this is the crux of it. I don't think you can wave it away saying "short spikes will always be there" when clearly they are not there on other plugins. Probably not helpful to say that some people are "obsessed" when it is causing major consequences for them either.

As I posted earlier, you may not be able to reproduce it on your rig(s), but IMO you need to turn some resources to fixing this. Please reach out to one or two of the owners who have the issue and spend the time to get it sorted once and for all - this has been going on for years now and it's clearly not fixed in Avenger 2.

[aMUSEd]

I think it's worse when the GUI is open, and even worse if I switch to another desktop screen then back again with the GUI open so I think allocation of resources to the GUI may be part of the problem (and this is with M1 Max with its 32 Core GPU on my system so it's no slouch graphically)

[Caine123]

i think i know this problem from another company. new sonic arts, their plugins are best to be not active windowded, otherwise the performace is really breaking for me. maybe this is the same with avenger 2, i dont have avenger 2 yet.

[noiseboyuk]

I have a few plugins that cause problems if leave them open. XO slows Cubase's meters to about 1 update a second if the GUI is open. No issues with Avenger here though.

[geiger167]

M1 mac studio pro running logic and live in Somoma exclusively using audio units running library from an external samsung t7 ssd and listening monitoring through a simple Audient Evo external sound card, all up to date. After updating Avenger not getting any spikes or crackles with the macros