VPS Avenger 2.4 [RELEASED - FAQ in OP]

[remix68]

Ok, I'm done trying to help anyone with this issue.

You're not helping anyone with the issue - it's pretty obvious that it isn't a user-error or system configuration problem.

I've got it sitting open on a patch unplayed in Ableton right now as I type this with the GUI open - I can watch the CPU monitor spike regularly to 200%+ while literally nothing is happening to it.

Same here.

[medienhexer]

Mac m1 and up users :



Hope this helps a bit somewhere…

It might help those who discuss how many tracks and voices they can play back.

For us with the CPU spikes, it only murks the water. For the CPU spikes, only one instance is needed and it can idle, not playing a single note for the issue to occur.

[medienhexer]

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

So far, we have only seen issues on Apple M1-3 CPUs. No asus tools on those systems. And by now, other JUCE based plugins like UVI don‘t show the issue anymore.

[msvs]

Just spoke to Rene, he said we had only 4 support tickets (from November to today), regarding CPU spikes...
We want to fix that of course, but if its that rare and does not occur on our machines at all, it will be tough for Rene.

[medienhexer]

But just to be clear: we don't know if Avenger is JUCE-based. I'm just saying that JUCE-based plugins had an issue with exactly the same behavior. So it might be a good idea to read up on what they found out communicating with Apple.

This is the list of developers who gave JUCE permission to reference them:

Adobe
AMS-Neve
Antares
Arturia
Audio Modeling
AudioKinetic
Avid
Bose
Bytedance
Corsair
Cycling74
Dolby Laboratories
Eventide
Fender
Focusrite
Genelec
Google
Harman
Harrison
InMusic
Izotope
Korg
Krotos
LANDR
MathWorks
Meta
Metric Halo
Moog
Music Tribe
Naughtydog
Netflix
Pioneer DJ
reFX Audio Software
Roland
ROLI
Sennheiser
Serato
Sonnox
SoundRadix
Spitfire
Splice
SSL
Steinberg
Syng
THX
Tracktion
Universal Audio
UVI
Valhalla DSP
Waves
Wolfram Research, Inc.
Yamaha

I am not seeing this issue with ValhallaDSP, UVI, Universal Audio, Steinberg, Sonnox, Moog, eventide or Arturia.

I had the same exact issue a while back with UVI Player and Falcon and otristan communicated with me and likely others to track down the issue and vastly improve on the situation, to a point where I consider it fixed. Very nice, professional in communication and I have not seen the issue pop up again.

[msvs]

Avenger is not (yet) Juce based.

[noiseboyuk]

Just spoke to Rene, he said we had only 4 support tickets (from November to today), regarding CPU spikes...
We want to fix that of course, but if its that rare and does not occur on our machines at all, it will be tough for Rene.

Thanks for posting this Manuel. This is exactly what I was saying for too many pages - so many here unwilling to help themselves.

Thanks also to Rene for fixing the spectral root note. I didn't get any support notification, but hey it's done!

[medienhexer]

Just spoke to Rene, he said we had only 4 support tickets (from November to today), regarding CPU spikes...
We want to fix that of course, but if its that rare and does not occur on our machines at all, it will be tough for Rene.

I understand that. But what is the use of all kvr members who have this issue creating additional tickets where the repro steps are:

1. Load Avenger with any preset

I'm certain we can more than double the number of tickets, perhaps even more if we get those who have the issue but just don't use Avenger until it's fixed. And it's not a new issue. I have had this issue with Avenger 1, as well. Which is why I usually use one instance max.

And there have been several users here who stated they will not upgrade unless the CPU spikes are fixed. So those are potential candidates/tickets, as well. But again, you seem to either have the issue or you don't.

That being said, I have seen device-specific bugs in iOS development, where you don't have drivers and where software installation does not produce cross-effects. It was the exact same hardware, same iOS version, only the one app installed and one device showed the issue during normal use and only after we found out how to actively trigger the issue, it would show up on other devices, as well.

I think it's easy to assume user error even when it's not a factor.

Could you point Rene to that JUCE forum discussion where the exact same behavior is discussed and where in the context of the JUCE framework, the underlying problem was identified with the Mac OS scheduler and possible solutions were discussed:

https://forum.juce.com/t/mac-m1-thread- ... oups/52188

And could you also ask him to verify that the techniques he uses against denormals are applied to all processing in the audio thread, including the FX. He will understand what that means.

If anybody else is interested in nerdy stuff:
https://www.earlevel.com/main/2019/04/1 ... denormals/
https://forum.juce.com/t/state-of-the-a ... /11?page=2
viewtopic.php?t=575799

[Atlatnesiti]

I’m assuming it’s Windows?

[zvenx]

Avenger is not (yet) Juce based.

Didn't Manuel just say it is NOT Juce Based? Why are you pointing them to Juce forums?

The idea of emailing supporting is two fold.
1) Rene will know it is not just 4 people and
2) Your configuration of your computer and DAW may help him figure out the commonality between those that are having the issue.
rsp

[MirkoVanHauten]

There were only 4 support tickets from november to today is a nice way of ignoring that customers contacted support since v1 for the same issues...

[medienhexer]

Avenger is not (yet) Juce based.

Didn't Manuel just say it is NOT Juce Based? Why are you pointing them to Juce forums?

The idea of emailing supporting is two fold.
1) Rene will know it is not just 4 people and
2) Your configuration of your computer and DAW may help him figure out the commonality between those that are having the issue.
rsp

I‘m pointing to the JUCE forum because the error which occurs there shows the exact same behavior and the issue has nothing to do with JUCE, but with MAC OS. It is a place, though, where plugin developers are discussing the MAC OS issue and how to solve it in a plugin. I could point to the developer reference for threading under MAC OS, but nobody is discussing issues there.

Can you just trust for a second that I‘m interested in getting my plugin fixed so I can finally use it? Or stop policing what is being said about a bug that doesn‘t even affect you?

Whichever is more convenient, really.

[zvenx]

You need to email support.
That you seem to be reluctant to do that for a bug you are interested in getting fixed is just weird.
If you think the thread is useful email that too.

Ftr, my intel windows does have the spiking it is just not nearly as bad as it was on mac intel. So yes it does affect me too, I just rarely use my pc these days beyond using it to test software in beta.


rsp

[Atlatnesiti]

Who cares about Juce or whatever it is…
As it is Avanger ver.2.04 works on my Mac mini Pro beautifully

[medienhexer]

You need to email support.
That you seem to be reluctant to do that for a bug you are interested in getting fixed is just weird.
If you think the thread is useful email that too.

Ftr, my intel windows does have the spiking it is just not nearly as bad as it was on mac intel. So yes it does affect me too, I just rarely use my pc these days beyond using it to test software in beta.


rsp

Every argument for and against mailing them has been repeated several times. You can think what you want to think.
I have provided Manuel with what I‘m confident is relevant information. It doesn‘t have to convince you. I don‘t know you and you‘re not the developer.