Vengeance Producer Suite - AVENGER - 1.8.5 the main thread

[Nightpolymath]

Not too surprised with regards to the high CPU usage. My impression of Vengeance (after owning all plugins except Phalanx and Avenger) has been of great sound but generally inefficient programming. Even Glitch Bitch and Delay introduce unacceptably high CPU count, and these are supposed to be "simpler" plugins. Pass for me.

[Soundplex]

Sorry I should clarify there and will edit the original post - what i listed is not all the expansion gives you, that's just how many sounds you get in those particular categories I listed. Seems very small to me.

Now I understand. I think this is pretty small especially for edm (just 11 synth sounds? 7 arps and 4 pads?) I'd like to know where the bigger amounts of presets are placed in I mean, if there are just 100 drum patches I wouldn't buy it either since they're not useful to me.

+1 I agree a patchlist would be very useful!

[docam28]

i am realy disappointed, update to 1.0.23 nothing happen, everything is the same
Fan go very high in macbook 15 Retina mid 2015 16 GB RAM 256 SSD i7 Quad Core
-ECO Mode is on nothing help,
-Cutting voice more than 1.0.22
-CPU Very High
- No multi output for the Drums you get max 3 output to Logic Pro and rest channels are dead
- Right click to show the source modulation is don't working at all
- lose 9% from my Macbook batterie in 3 Minutes, Never happen to me before with any program
-Clipping Sound

this Synthesizer is not usable for me at the moment

ich bin von Vengeance sounds enttäuscht

From my "Customer Center" (from http://register.vps-avenger.com) I can't see v1.0.23, but only v1.0.22 (for both WIN & OSX), downloadable files are "WIN_Avenger_1_0_22.exe" for Windows, "OSX_Avenger_1_0_22.dmg" for MacOS X...

[Ryan99]

I'm interested in buying it. I'd like to know when does the Xmas sale is ending.

[db3]

From my "Customer Center" (from http://register.vps-avenger.com) I can't see v1.0.23, but only v1.0.22 (for both WIN & OSX), downloadable files are "WIN_Avenger_1_0_22.exe" for Windows, "OSX_Avenger_1_0_22.dmg" for MacOS X...

You need to remove and reinsert Avenger in your DAW and then you will see a red update button to download 1.0.23 .

For the record, 1.0.23 (ECO mode) is the same for me as 1.0.22. i.e. I can now view Avenger at 100% without fan kicking in, but as soon as I try 150%, or more than one instance it fires up.

NB) This is when the DAW (Mac Bitwig) is sitting doing nothing and Avenger reports 2% CPU consumption.

*edit* Doesn't take much effort before fan reappears with 75% ECO GUI.

[docam28]

From my "Customer Center" (from http://register.vps-avenger.com) I can't see v1.0.23, but only v1.0.22 (for both WIN & OSX), downloadable files are "WIN_Avenger_1_0_22.exe" for Windows, "OSX_Avenger_1_0_22.dmg" for MacOS X...

You need to remove and reinsert Avenger in your DAW and then you will see a red update button to download 1.0.23 .

Thanks for this tip, but unfortunately my PC for home studio is offline (no internet access). EDIT: solved, 1.0.23 are now available from Customer Center. Thanks a lot.

[magickalmutagen]

Bug: When right-clicking an EQ's node, you can't choose the high/low-pass types, only high/low shelf and peak are available.

Bug: When creating a second oscillator, the routing of Osc 1 is used as its template. The Shaper 1 module is ignored each time however.

Bug: Pressing C3 on a MIDI controller is seen correctly as C3 by DAWs but Avenger reports it as C2 (top display).

[V0rtex]

Hello guys

I can confirm lower GPU usage with ECO and MID modes. now is about (20 - 25%), before(80-90%).

Running Win7 Ultimate, Ableton Live 9.7, Intel core i7-4790k, Intel HD graphics 4600, 16 GB ram.

[exmatproton]

i am realy disappointed, update to 1.0.23 nothing happen, everything is the same
Fan go very high in macbook 15 Retina mid 2015 16 GB RAM 256 SSD i7 Quad Core
-ECO Mode is on nothing help,
-Cutting voice more than 1.0.22
-CPU Very High
- No multi output for the Drums you get max 3 output to Logic Pro and rest channels are dead
- Right click to show the source modulation is don't working at all
- lose 9% from my Macbook batterie in 3 Minutes, Never happen to me before with any program
-Clipping Sound

this Synthesizer is not usable for me at the moment

ich bin von Vengeance sounds enttäuscht

- ECO Mode is on nothing help, > same here. i don't see different readings in taskmanager or AMD's Crimson Wattman readout between the different modes. I see however that the UI is updating slower at ECO mode. Also, i am running an AMD RX480. I guess this should be fast enough anyway to see any differences in the readout

- Cutting voice more than 1.0.22 > I have no such issue. Voicing seems to be the same

- CPU Very High > same as it was before

- No multi output for the Drums you get max 3 output to Logic Pro and rest channels are dead > i have no such issue. All AUX outputs are working over here. Tested this with OSC's and all drumchannels to their unique outputs (Windows 10, x64, FL Studio 12.4, Reaper 5.29, Ableton 9.7)

- Right click to show the source modulation is don't working at all > No such issue over here. When i right-click the little triangle, i can still see all mod sources

- lose 9% from my Macbook batterie in 3 Minutes, Never happen to me before with any program > I am on a Windows 10 Desktop...so yeah...

- Clipping Sound > No such issue over here.

[Sampleconstruct]

Bug: Pressing C3 on a MIDI controller is seen correctly as C3 by DAWs but Avenger reports it as C2 (top display).

That's by design, it seems, in the mapping editor the top note is G7 (usually G8). iZotope do it the other way round, C3 = C4, so some devs to go their own route.

[OzoneJunkie]

Another data point from an Avenger owner:

Dell XPS 15 i7-4702HQ (quadcore) CPU @ 2.20 GHz, 16 GB RAM, Windows 8.1 OS (64 bit).

ECO mode seems to help things a bit, but I'm still getting high fan usage on my laptop. It seems less than v1.0.21 and it takes a little longer (10 minutes compared to 5 minutes) for the fans to kick on and spin at top speed, but this is still an issue here.

EDIT: putting the interface to 80% seems to help a bit. Fans are still on, but not spinning at top speed.

And I do think that getting it to run smoothly with little to no fan usage on a high end laptop is relevant, considering the number of producers now who are laptop-only.

So, improved yes, but I still think we need to go further with the rendering improvements.

[kanzler]

i am realy disappointed, update to 1.0.23 nothing happen, everything is the same
Fan go very high in macbook 15 Retina mid 2015 16 GB RAM 256 SSD i7 Quad Core
-ECO Mode is on nothing help,
-Cutting voice more than 1.0.22
-CPU Very High
- No multi output for the Drums you get max 3 output to Logic Pro and rest channels are dead
- Right click to show the source modulation is don't working at all
- lose 9% from my Macbook batterie in 3 Minutes, Never happen to me before with any program
-Clipping Sound

this Synthesizer is not usable for me at the moment

ich bin von Vengeance sounds enttäuscht

- ECO Mode is on nothing help, > same here. i don't see different readings in taskmanager or AMD's Crimson Wattman readout between the different modes. I see however that the UI is updating slower at ECO mode. Also, i am running an AMD RX480. I guess this should be fast enough anyway to see any differences in the readout

- Cutting voice more than 1.0.22 > I have no such issue. Voicing seems to be the same

- CPU Very High > same as it was before

- No multi output for the Drums you get max 3 output to Logic Pro and rest channels are dead > i have no such issue. All AUX outputs are working over here. Tested this with OSC's and all drumchannels to their unique outputs (Windows 10, x64, FL Studio 12.4, Reaper 5.29, Ableton 9.7)

- Right click to show the source modulation is don't working at all > No such issue over here. When i right-click the little triangle, i can still see all mod sources

- lose 9% from my Macbook batterie in 3 Minutes, Never happen to me before with any program > I am on a Windows 10 Desktop...so yeah...

- Clipping Sound > No such issue over here.

ithink they test the VST Plugin more than they do it for Audio plugin for MacOS, because for mac it have more problems than Windows plugin

[Ohlson_M]

I love the synth, it sounds incredibly but there are obvious bugs that need to be fixed. Hopefully there is an update before the december discount ends.

[dusted william]

I'm on Windows 8 and I can't seem to have 2 instances open. it has so far always crashed on me in Ableton Live 9.7 within a few minutes.

[magickalmutagen]

Bug: Pressing C3 on a MIDI controller is seen correctly as C3 by DAWs but Avenger reports it as C2 (top display).

That's by design, it seems, in the mapping editor the top note is G7 (usually G8). iZotope do it the other way round, C3 = C4, so some devs to go their own route.

I thought it may be something to do with that. I wish there was a standard that was followed.

Hello guys

I can confirm lower GPU usage with ECO and MID modes. now is about (20 - 25%), before(80-90%).

Running Win7 Ultimate, Ableton Live 9.7, Intel core i7-4790k, Intel HD graphics 4600, 16 GB ram.

My GPU is fine (~1%) in any of the modes. However my CPU suffers whenever the GUI is open. With the GUI closed, I'm idling at ~10% CPU usage. After opening the GUI, the CPU is used ~30% more. Changing FPS modes doesn't seem to affect how much CPU is being used. i7 3770K, GTX 670, up-to-date Windows 10.

I love the synth, it sounds incredibly but there are obvious bugs that need to be fixed. Hopefully there is an update before the december discount ends.

You can find out what's been fixed via the changelog.