Vengeance Producer Suite - AVENGER - 1.8.5 the main thread

[Chipi]

[AxlMaldini]

Jim Aikin encounters possibly the most powerful synthesizer he’s ever looked at



The Wrap-Up. If you’re new to synthesizers, editing the factory presets in Avenger could be intimidating, because there’s a lot going on. Still, the user interface is about as easy to navigate as it could possibly be. If you’re looking for a deep and powerful resource for designing sounds, you’ve just found one.

All high-end synthesizers have their own unique features, so I’m not rash enough to claim that Avenger can do absolutely everything — but if I can say this without casting aspersions on Synthmaster2, Serum, Dark Zebra, SurgeXT, or Omnisphere, all of which are amazing in their own ways, Avenger may be the most powerful synthesizer I’ve ever looked at. It’s a remarkable piece of software. (Jim Aikin 2023)

[Jac459]

Says the user struggling with quoting others.

Well his way of argumenting tells a lot about him haha...

Anyway, I won't put another coin in the machine lol...

[Jac459]

.....It’s a remarkable piece of software. (Jim Aikin 2023)

There is no question about that mate.... we are page 971 of forum discussion, that's show how avenger is appreciated.

Yet if there is a bug in cpu handling, it is good to inform the developer.

[AxlMaldini]

.....It’s a remarkable piece of software. (Jim Aikin 2023)

There is no question about that mate.... we are page 971 of forum discussion, that's show how avenger is appreciated.

Yet if there is a bug in cpu handling, it is good to inform the developer.

Send them your question here they should be able to help you: https://www.vengeance-sound.com/support.php

[Jac459]

Send them your question here they should be able to help you: https://www.vengeance-sound.com/support.php

I did it immediately yesterday when I noticed the issue and saw it was common to apple silicon users. It is weekend though, I didn't get feedback yet but will report here when I have.

[Hanz Meyzer]

Chipi likes to cut into his own flesh... Makes no sense, but whatever.

Maybe let's stop the discussion, won't change anyway.

[Hanz Meyzer]

Send them your question here they should be able to help you: https://www.vengeance-sound.com/support.php

I did that many times, I also wrote some kind of dissertation about the problem to Rene and offered my help with testing and so on. In the end, it was completely ignored, by Rene and Manuel. Yet the problem is there. Spreading fake news or pretending that there was no problem with Avenger won't help anybody.

[Jac459]

Send them your question here they should be able to help you: https://www.vengeance-sound.com/support.php

I did that many times, I also wrote some kind of dissertation about the problem to Rene and offered my help with testing and so on. In the end, it was completely ignored, by Rene and Manuel. Yet the problem is there. Spreading fake news or pretending that there was no problem with Avenger won't help anybody.

2 questions, one for Hanz, one for the community:

1 - Are you sure you were having these issues before being on the Bitwig Beta ? (I assume you are)? I ask because I don't remember having any issue before.
2 - Do we confirm that only Apple Silicon is impacted ?

[Hanz Meyzer]

I would answer:
1. No, I am on Bitwig 4.4. And the problem exists since 2016, on Mac Intel, Mac ARM, Windows Intel, AMD.
2. No, all OSes and cpu types are affected. It is a problem in the code of Avenger, not a system or OS problem.

[Jac459]

I would answer:
1. No, I am on Bitwig 4.4. And the problem exists since 2016, on Mac Intel, Mac ARM, Windows Intel, AMD.
2. No, all OSes and cpu types are affected. It is a problem in the code of Avenger, not a system or OS problem.

Thanks... Weird that the support didn't answer... Let's see what they do now.

[Jac459]

Actually that reminds me a problem I saw with Bitwig and Punch2 with the way they manage automatable midi parameters:
viewtopic.php?t=538450

I just checked a track with a loooot of stuffs (complex spectral analysis, convolution revers side chaining everywhere), the track is played easily except when Punch2 is used where I got ... exactly the same spike than Avenger.

So, what I think is that certainly it is a shared bug between Bitwig and a few VSTs. When I say a shared bug, I mean a bug where each of the party can blame the other...

So my next question is... Is there anybody not using Bitwig having this issue ?

[sacer]

There is also a problem if you use avenger or rapid on vst3 with ableton live on windows.
If you switch a preset and have controllers like APC40, touchable or Push, the preset change takes nearly a half minute and every parameter change between the changing preset is Diplayed then controller. My push2 displays on the first knob 20 to 50 parameters with different values, before switching a preset. On vst2 I don’t get this problem. So rapid and avenger are my only synths where I can’t use the Vst3 version. On bitwig, fruity and Cubase I can’t reproduce this error, they are working fine. So the problem is only with Ableton, but Ableton is running all my other 100 synths without problems on VST3.

[LFO8]

So where do I download a demo/trial for Avenger?

[Jac459]

Thanks... Weird that the support didn't answer... Let's see what they do now.

I did received a nice and long answer from VPS.

In a nutshell, there are still working at optimising Avenger.
They also say that when they test with M1, they don't get audio glitches. But some of their presets have 10% cpu peaks. I think that's coherent with my experience as I get audio issues with 12+ instances.

They also give an interesting perspective on the automations and its cpu cost.

"
And please if you compare VSTs please also think about other functions that could cause high/lower CPU usage.

For Example automated parameters could cause a high CPU useage:
As of Serum version 1.33b4, there are over 450 parameters that can be automated, including oscillators, filters, envelopes, LFOs, effects, and modulation sources.
In the VPS Avenger version 1.8.2, there are over 6000+ parameters that can be automated.

This is not meant to be an excuse for high CPU loads or crackling audio, it's just to show that there is often more to it than people think.
"

Nice answer from the developer.
I will continue to wait for further optimization and in the meantime bounce the track in case of problem....