VPS Avenger 2.4 [RELEASED - FAQ in OP]

[miloszz]

Secondly the better the repro steps the better the chances of the developers being able to isolate the issue.

The repro steps, as stated repeatedly, are: open the plugin. It is an issue independent of DAWs, sample rates, buffers, etc..

Thirdly and most importantly, all this info has to get to the developer.
Unlike u-he and a few others, vengeance does not have an official forum here on kvr.
By far the best way to get to the developer, rene is thru email.

The company posted on this very thread! And another post quotes an e-mail from the company! Pretending that information posted here is beyond their awareness is just silly.

By all means, anyone should feel free to send them an e-mail - I see no point, given their awareness of the issue. Either they'll fix it or they won't - but given the lack of demo, people should be aware of CPU spikes and whether or not they're ongoing in the current version and future version. The only way for people to find that out is through threads like this.

[medienhexer]

Exactly. The information was pretty clear before the yelling started.

It‘s not about multiple instances or a specific preset. It‘s not wether your system manages 40 or 110 instances or how many voices.

One single instance with whatever preset. After the first note has been played, Avenger will spike between basically 1% CPU and 100% on the last core in Logic. Measured via Logic‘s meter or Activity Monitor. Avenger‘s internal meter is not showing the spikes.

Apparently, other DAWs across AU and vst show it, too. It doesn‘t have to play a single voice. Just sitting there idleing, killing the engine every now and then.

It doesn‘t change with buffer, it doesn‘t change wether playback is running or not. And it‘s an issue which only occurs with Avenger, not any other instrument in my collection. As soon as you bypass Avenger, it‘s gone.

From the discussion around that JUCE framework issue I know that it is very likely that the live processing is moved to one of the efficiency cores. I did provide a link describing the issue and as far as I‘m aware, all other plugins with that issue have fixed it. Even if Avenger is not JUCE based, there is useful information about Mac OS scheduling in there.

It also says that it doesn‘t seem to be an issue on M1-3 base models, but only on the high end Pro, Max and Ultra. So testing with an entry level machine and saying you don‘t have that issue doesn‘t help.

Back in the day, I would have said: look at denormals. But I think that isn‘t an issue anymore.

[zvenx]

I have an M1 Max.. doesn't happen here...
rsp

[medienhexer]

You can‘t help with the issue then

[X-cytr]

I have an M1 Max.. doesn't happen here...
rsp

do you use Ventura or Sonoma? Ableton Live 11.3.13?

Thanks in advance

[zvenx]

Sonoma, Cubendo.
rsp

[magicmusic]

is it posible in V2 to make slice play from a sample ?

for those people who have CPU spike problems. I have such problems on other synths that are juce lib based and i solve this by deinstall the asus cpu tweak tools asus install .maybe thats problem on avenger too

[e-musician]

According to the changelog, V2.0.1 should have fixed this issue:
"WINDOWS: reimplemented version information in Avenger2 files. VMAN should display the version correct now. ( instead of n.a.)"

I still have V-MANAGER telling me that I am using V1.8.6 (although my current version is V.2.0.4).

So my question is: Is this still something that needs to be fixed?
[The OP says that "At time of posting, V Man isn't correctly reporting the installed version."]

[noiseboyuk]

Changing the root note in Spectral is working now in 2.0.4, yay.

2.0.4 change log
- spectral-granular root-note is working as expected now
- fixed additional utf8 problems
- fixed a skin issue in random arp where the length and silense option buttons where switched
- fixed arp-randomizer not using notes after edit
- fixed a issue with drum sample reverse-end-sync on very long samples

[medienhexer]

Alright, credit where it's due,
- wrong installed version in VManager is fixed for me in its latest version (today's release).
- the .component bundle version, as well as the plugin version via PlugInfo are correct as of 2.0.4.

[miloszz]

CPU spikes still present on 2.0.4 (M1 Max, 48K/64 samples, Ableton 11, 64GB RAM, 68 degrees Fahrenheit in the room, unsure of the exact humidity level in the room but it's nice, etc..), happening while the GUI is open and unplayed.

[medienhexer]

Same here.

Just wanted to be fair about the improvements I am seeing.

Are you also seeing the first spike going to about 25% CPU, then back to normal, then about 50%, back to normal, up to 75% CPU, back to normal, up to 100%, back to normal and then always to the limit?

[kkvvrr]

Mac m1 and up users :



Hope this helps a bit somewhere…

[Gam456]

This v2.0.4 looks way more stable on my Intel I7 6820HK 32Go, Win 10.
It's stable around 30% (a lush pad with 3 osc, unison, sub, voicing, detune, slow and long decay, 3 heavy effect), before it was up to 55% with 75% peak

[miloszz]

Same here.

Just wanted to be fair about the improvements I am seeing.

Are you also seeing the first spike going to about 25% CPU, then back to normal, then about 50%, back to normal, up to 75% CPU, back to normal, up to 100%, back to normal and then always to the limit?

Yes, I never looked at the initial bit but it hovers around the normal 15% for the init patch then progressive spikes 25/50/100 on up, I think the last spike just registered 500%.