VPS Avenger 2.4 [RELEASED - FAQ in OP]

[noiseboyuk]

@noiseboyuk
may change:

Thank you - OP updated.

[remix68]

I need to roll back to whatever I had before 2.2.0. The glitches and pops are back on my M1. Is there a place to find older versions, in my case 2.0.6? Really could kick myself right now for updating. It's spiking at 100% just sitting there doing nothing on the init preset with nothing else loaded.

[msvs]

We are proud to release "Funky House 3," the new VPS Avenger sound expansion crafted by genre experts Manuel Schleis & Andy Hinz. Experience the ultimate fusion of authentic 70s disco riffs and the vibrant energy of House. With 172 presets, this pack is our biggest yet - including so much content, it could be easily two expansion packs. Some of the highlights are: professional female & male lead vocals, new funky guitar multiloop kits, especially recorded real brass sections & riffs, all kind of pianos, bass guitars or analog 70s vintage gear: ensuring your tracks stand out with a genuine funky groove. It also contains some lower bpm styles for Funk-Pop, agressive french House and anything between. Perfect for adding that classic yet contemporary flair, this new expansion pack is essential for any producer looking to produce anthing funky or groovy - no matter if its Pop, EDM or House.


Attention: VPS Avenger version 2.2 minimum required!

this expansion adds to your library:

172 Avenger presets 41 new drumkits / drum seq
119 new multisamples 22 new wavetables
87 granular samples 16 multiloops
172 new arp presets 23 shapes

[m-ac]

...

[m-ac]

I need to roll back to whatever I had before 2.2.0. The glitches and pops are back on my M1. Is there a place to find older versions, in my case 2.0.6? Really could kick myself right now for updating. It's spiking at 100% just sitting there doing nothing on the init preset with nothing else loaded.

Mine does the exact same thing with version 2.1. Did you find the same? So 2.0.6 didn't have this issue? Have you been in contact with support?

Disappointing and worrying to hear that 2.2 has the same issue.

[m-ac]

Avenger update 2.2.0 is released.

2.2.0 Release notes:
New Features:
Added Drum SQ multi pattern.
Added formant lock to single loop osc mode to preserve formants while pitching +12/-12.
Any multisample displays will switch to the sample for the recently played note.
New icons for preset preview.
Reworked previews: added categories with different play lengths, changeable on the sys page.

Rework:
Preset -> update preview now displays a small progress on the file in the browser instead of an annoying popup.

Fixes:
Fixed an issue where the drumkit browser had an incorrect scroll size after renaming a preset in a custom expansion.
Sound browser now shows the correct selected sample for the slot in osc stacker mode when changing the slot.
Fixed arp ratchet 7-in preset having a wrong value.
Renaming a preset in a custom expansion that has a preview will also rename the preview correctly.
Fixed an initial click sound when modulating oscMaster, DrumMaster, or MasterVol from high to zero on the first voice.
Fixed another issue with osc velocity.
Fixed adding a shaper module not displaying the correct selected initial shaper model.
Fixed pitch envelope used as mod-source on a non-per-voice target being triggered by drum voices.
Fixed an issue with MIDI export when speed is triplet or dotted.
Fixed an issue with macro button modulation where the final value now behaves more like a button than a dial.
Fixed a crash on windows when file load/save dialog was open while DAW was about to get closed by the user.
Fixed an issue where osc keytrack was not correct applied when using copy/paste
Fixed a click sound in TG when stereo width is not 0% or 100%
Fixed AAX timeout on "ALL NOTES OFF" midi cc


@noiseboyuk
may change:
Is there a version 2 manual available?
Not yet.

on the first site to yes.
https://downloads.vengeance-sound.com/p ... _2_0_0.pdf

Thanks for posting these. Where did you find the changelog details?

[c0LIn]

Thanks for posting these. Where did you find the changelog details?

on the vengeance website if you click on Plugins -> Avenger 2 -> Downloads

https://vengeance-sound.com/plugins/plC ... venger%202

[Jac459]

I need to roll back to whatever I had before 2.2.0. The glitches and pops are back on my M1. Is there a place to find older versions, in my case 2.0.6? Really could kick myself right now for updating. It's spiking at 100% just sitting there doing nothing on the init preset with nothing else loaded.

Can somebody take a picture of CPU usage on a loop playing using avenger before and after 2.2 upgrade?

I just upgrade from 2.1 to 2.2. My 2.1 curve was totally flat and now my 2.2 has small spikes BUT I have the feeling the average usage is a bit less.

Now I want to slap my face not to have taken the pictures myself...

[remix68]

Yeah, I rolled it back to 2.0.5 and it's 100% fine again. 2.0.6 has the same issues for me as I rolled back to that one first, then I figured out I was on 2.0.5 before I did the update yesterday. I missed all the updates between 2.0.5 and 2.2.0

I did let them know at Keilwerth and Andre Keilwerth responded to me, so they are now aware and are looking into what changed between 0.5 and 0.6.

They will provide a link for the rollback if you ask, not sure if I can post that here. You can figure it out if you reverse engineer the link to the new 2.2.0 update, that's how I got it. Keilwerth did send over the link to 0.6...but 0.5 is what you want on an M1.

[PebbleInAStream]

Saw there's a sale going on. Is there still no demo?

[m-ac]

Yeah, I rolled it back to 2.0.5 and it's 100% fine again. 2.0.6 has the same issues for me as I rolled back to that one first, then I figured out I was on 2.0.5 before I did the update yesterday. I missed all the updates between 2.0.5 and 2.2.0

I did let them know at Keilwerth and Andre Keilwerth responded to me, so they are now aware and are looking into what changed between 0.5 and 0.6.

They will provide a link for the rollback if you ask, not sure if I can post that here. You can figure it out if you reverse engineer the link to the new 2.2.0 update, that's how I got it. Keilwerth did send over the link to 0.6...but 0.5 is what you want on an M1.

Thanks for that. Will be rolling back to 2.0.5 too as it's completely unusable on silicon macs running logic at the moment. Has Andre given you any more info other than them acknowledging the issue?

[] Peter:H []

I epxerience now some problem with Avenger 2.1 and 2.2 in Bitwig 5.2 Beta 10, Windows 10.
The Avenger GUI loads only after ages. It even get's the Bitwig plugin host process reporting sth. like timeouts.

I can only guess that it has to do with the recent change in Bitwig that they use GPU.
And I guess that Bitwig and Avenger somehow blocking themselves waiting for acces to the GPU.
On the other hand MeldaProduction plugins still works, which are using GPU as well...

My question: has anybody else experienced slow "open GUI" times for Avenger 2.2 in other DAWs than Bitwig?

[trusampler]

Where do we find the favorites if we want to back these up ?
on both mac / pc

[DCrown]

So many vocals in expansion packs really get annoying and it's a complete turn off. I am wondering who would use pre made vocals that hundreds of others could use.
That's neither creative, nor it's composing own stuff.
And in addition so many one finger presets, omg the xps are getting worse each time

[remix68]

Yeah, I rolled it back to 2.0.5 and it's 100% fine again. 2.0.6 has the same issues for me as I rolled back to that one first, then I figured out I was on 2.0.5 before I did the update yesterday. I missed all the updates between 2.0.5 and 2.2.0

I did let them know at Keilwerth and Andre Keilwerth responded to me, so they are now aware and are looking into what changed between 0.5 and 0.6.

They will provide a link for the rollback if you ask, not sure if I can post that here. You can figure it out if you reverse engineer the link to the new 2.2.0 update, that's how I got it. Keilwerth did send over the link to 0.6...but 0.5 is what you want on an M1.

Thanks for that. Will be rolling back to 2.0.5 too as it's completely unusable on silicon macs running logic at the moment. Has Andre given you any more info other than them acknowledging the issue?

No response, I just replied to let me know if they needed any help testing it.

Just go back to 0.5 and it should (probably) work like it did before the update.