Vengeance Producer Suite - AVENGER - 1.8.5 the main thread

[Trancit]

Yes and apparently the real number is 6000... not 2k....

And your infos are based on...what??

[Jac459]

Yes and apparently the real number is 6000... not 2k....

And your infos are based on...what??

Few pages back... information coming from VPS themselves.... I wrote to them about the issue.

[Hanz Meyzer]

What does the number of vst parameters have to do with the spikes at voice start?

[Jac459]

What does the number of vst parameters have to do with the spikes at voice start?

It seems we are restarting the same discussion every week .
Check a few pages back.

[Hanz Meyzer]

I read it, but I think you didn't fully understand. These VST parameters are there all the time, mostly not on voice level. A high number of these might explain a higher overall cpu usage, but not at all the given, very bad spikes. So this is a straw man discussion. Since a high cpu usage is expectable in a high quality plugin like Avenger, but not cpu spikes.

Spikes = Sudden appearance (here assumingly at voice start)
VST parameter = all-the-time appearance / cpu-load

Also most daws only track VST parameters in recording mode, and only send those which are automated. I really think you are on the wrong scent. Renoise even doesn't track any vst parameters at all, you have to automate it "from the outside" of the plugin.

So the main question remains: Why are they ignoring the spike problems? Is it a problem of measurement? Or ignorance? Or something else?

[Jac459]

I read it, but I think you didn't fully understand. These VST parameters are there all the time, mostly not on voice level. A high number of these might explain a higher overall cpu usage, but not at all the given, very bad spikes. So this is a straw man discussion. Since a high cpu usage is expectable in a high quality plugin like Avenger, but not cpu spikes.

Spikes = Sudden appearance (here assumingly at voice start)
VST parameter = all-the-time appearance / cpu-load

Also most daws only track VST parameters in recording mode, and only send those which are automated. I really think you are on the wrong scent. Renoise even doesn't track any vst parameters at all, you have to automate it "from the outside" of the plugin.

So the main question remains: Why are they ignoring the spike problems? Is it a problem of measurement? Or ignorance? Or something else?

Well, multiple points:
1 - They don't ignore the issue because they answered rhat they are currently specifically working on cpu usage..
2 - they are aware of it because one of the co-creator of Avenger acknowledged it to me via email.
3 - you seems to be pretty sure of yourself when you are saying that spikes can't be related to parameters. I don't think we have enough info to be sure at all. Except if you saw the code yourself, you can't know if the start of the note trigger a re-reading of the parameters. Maybe it does. What is for sure is it arrives at the beginning of the note so it isn't pure DSP processing as it is supposedly quite linear. So our best bet is resource loading, preparation of a component or something like that. Checking of midi parameters is a good candidate.
4 - if you are into coding, you know that modern languages involve promises and callback, maybe there is a cascade of event at note play. That would be my personal bet.
5 - finally, I am not surprised at all that performance issues can take months to be resolved, I have seen large teams struggling on much simpler systems (financial solutions) even with tools like jmeter, dynatrace or app dynamics... In particular if the issue is not fully deterministic...

[100tifiko]

Manuel any news on a Latin expansion with guitars, trumpets and accordion that will be great know that the Latin music it’s on top of Spotify it will be great to have a Latin expansion specially with real trumpets and other instruments

[Hanz Meyzer]

Well, multiple points:
1 - They don't ignore the issue because they answered rhat they are currently specifically working on cpu usage..
2 - they are aware of it because one of the co-creator of Avenger acknowledged it to me via email.
3 - you seems to be pretty sure of yourself when you are saying that spikes can't be related to parameters. I don't think we have enough info to be sure at all. Except if you saw the code yourself, you can't know if the start of the note trigger a re-reading of the parameters. Maybe it does. What is for sure is it arrives at the beginning of the note so it isn't pure DSP processing as it is supposedly quite linear. So our best bet is resource loading, preparation of a component or something like that. Checking of midi parameters is a good candidate.
4 - if you are into coding, you know that modern languages involve promises and callback, maybe there is a cascade of event at note play. That would be my personal bet.
5 - finally, I am not surprised at all that performance issues can take months to be resolved, I have seen large teams struggling on much simpler systems (financial solutions) even with tools like jmeter, dynatrace or app dynamics... In particular if the issue is not fully deterministic...

Ok, valid points. But I couldn't find a hint that they actually trying to improve this problem, since I got I similar general answer years ago "we are continouosly improving the synth blah blah". Maybe I misread your post. Will shutup now, maybe it will happen then

[Jac459]

Ok, valid points. But I couldn't find a hint that they actually trying to improve this problem, since I got I similar general answer years ago "we are continouosly improving the synth blah blah". Maybe I misread your post. Will shutup now, maybe it will happen then

Well I wouldn't old my breath neither haha... I am just trying to see the half full glass.
The positive points I find:
-They do say that they will deploy the CPU improvements both for v2 AND v1.8...
-As we are multiple to write to them, maybe they will pay attention (and I am pretty sure they read this thread as they already answer to some questions on it)
-As the synth is being actively reworked, there is more chance that the dev can catch some bugs while going around...

Anyway, just trying to be positive...

[m-ac]

Mac users have been waiting for over 6 years for CPU fixes so excuse us if we seem a little impatient.

[Jac459]

Mac users have been waiting for over 6 years for CPU fixes so excuse us if we seem a little impatient.

No dude, I am calling the cop right now and the NSA is tracking your IP...

Seriously, you have all the right to be upset or impatient, I was just sharing the latest state of the discussion.

[m-ac]

Mac users have been waiting for over 6 years for CPU fixes so excuse us if we seem a little impatient.

No dude, I am calling the cop right now and the NSA is tracking your IP...

Seriously, you have all the right to be upset or impatient, I was just sharing the latest state of the discussion.

Ffs, did you really have to get the NSA involved?!

[Jac459]

Ffs, did you really have to get the NSA involved?!

Don't hate me man, they have this "loyalty" program, for every person I contribute to put in jail, they offer one free cheesy crust upgrade at pizzahut, who could have resisted?

[msvs]

out now

[msvs]

full walkthrough