VPS Avenger 2.4 [RELEASED - FAQ in OP]

[remix68]

If the M class CPU spikes have been eliminated, I'll upgrade asap. I love the synth, but it has been pretty unusable since I bought it.

[Jac459]

If the M class CPU spikes have been eliminated, I'll upgrade asap. I love the synth, but it has been pretty unusable since I bought it.

Hello, I have an MBP with an M2 Pro that I run in low power mode (M2 Pro is so powerful I can have a full track with mixing and mastering included, tons of effects, still in this mode and about 10 hours of battery)..

I was having a test project with obvious spikes in it with avenger 1&2.
Since this update 2.0.5, I don't have them anymore. CPU usage is generally lower also. Still more than serum for example but much less than diva.

[DCrown]

If the M class CPU spikes have been eliminated, I'll upgrade asap. I love the synth, but it has been pretty unusable since I bought it.

Hello, I have an MBP with an M2 Pro that I run in low power mode (M2 Pro is so powerful I can have a full track with mixing and mastering included, tons of effects, still in this mode and about 10 hours of battery)..

I was having a test project with obvious spikes in it with avenger 1&2.
Since this update 2.0.5, I don't have them anymore. CPU usage is generally lower also. Still more than serum for example but much less than diva.

Only preset loading takes a bit longer time with v2 than v1 here, though.

I read several times that a gui generally could be also the reason for higher cpu or loading times. So why not offering a Valhalla-like skin for lower cpu usage and faster loading?! Not sure whether this would work, though, I am no dev.
But I like v2 so far.

[m-ac]

After the initial install issues people seemed to be having, are there still any gotchas for V1 users installing and updating to version 2?

[Teksonik]

I'll try this again since there was no response.....

Working on some presets to upload and I notice that no * appears when a patch is edited. I can't find any visual feedback as to whether or not a patch has been edited. Sometimes when I play a patch for awhile I can't remember if I edited it or not.

Of course all I have to do is re-save the patch just to be safe but that can get to be a little tedious after awhile.

So is the lack of a visual clue intended behavior or is this a bug or am I missing something? If it's a bug I can report it to Rene. If it's intended behavior then I'd make a feature request for a * or some other visual clue when a patch has been edited.

On another note regarding patches, If I load one of my patches, edit it to the point where I give it another name, edit the new patch even further and go to save that patch again it wants to save under the old patch's name:

AV2 121023-1.png

In the image above I started with SP Vamping, edited it then saved it as SY Cosmosis, edited it further then went to save Cosmosis again. You can see that it wants to save to Vamping again.

All we have to do is pay attention and it shouldn't be a problem but again I don't know if this is intended behavior, or user error on my part. Seems like it could be easy to overwrite a patch that way or maybe it's just a visual thing.

Ok back to making more patches. Avenger 2 really is a ton of fun to patch..

EDIT: I'll explain further. When you edit a patch in DUNE 3 for example the * shows up indicating there have been changes made to the patch:

D3 121223-1.png

Many if not all other synths do the same thing. There is some visual indication that changes have been made so you know to save those changes if you wish.

When you edit a patch in Avenger 2 you get:

AV2 121223-1.png

No indication that any changes have been made.

[Chauzou]

Exploring the spectral oscillator introduced in Avenger 2 using a custom sound texture I made with Kaleidoscope. Beware of atonal dissonance!

Wow!
This sounds awesome and so different than what we're used to with this synth! Looking forward to more of that! I also noticed some clicks here and there in the sound. Are these CPU spikes related? I kind of noticed that in other avenger videos.

[Old Crab]

Regarding the CPU spiking issues, I've read comments about the improvements for M2-M3 and also Pro and Max versions of Macs. Can anyone please confirm that the M1 (Standard Version) is no longer spiking?

[Musical Gym]

I'll try this again since there was no response.....

Working on some presets to upload and I notice that no * appears when a patch is edited. I can't find any visual feedback as to whether or not a patch has been edited. Sometimes when I play a patch for awhile I can't remember if I edited it or not.

Of course all I have to do is re-save the patch just to be safe but that can get to be a little tedious after awhile.

So is the lack of a visual clue intended behavior or is this a bug or am I missing something? If it's a bug I can report it to Rene. If it's intended behavior then I'd make a feature request for a * or some other visual clue when a patch has been edited.

On another note regarding patches, If I load one of my patches, edit it to the point where I give it another name, edit the new patch even further and go to save that patch again it wants to save under the old patch's name:


AV2 121023-1.png


In the image above I started with SP Vamping, edited it then saved it as SY Cosmosis, edited it further then went to save Cosmosis again. You can see that it wants to save to Vamping again.

All we have to do is pay attention and it shouldn't be a problem but again I don't know if this is intended behavior, or user error on my part. Seems like it could be easy to overwrite a patch that way or maybe it's just a visual thing.

Ok back to making more patches. Avenger 2 really is a ton of fun to patch..

EDIT: I'll explain further. When you edit a patch in DUNE 3 for example the * shows up indicating there have been changes made to the patch:


D3 121223-1.png


Many if not all other synths do the same thing. There is some visual indication that changes have been made so you know to save those changes if you wish.

When you edit a patch in Avenger 2 you get:


AV2 121223-1.png


No indication that any changes have been made.

Maybe save with new name such as Name Edited before you modify it? Until you can get a solution.

[Teksonik]

Maybe save with new name such as Name Edited before you modify it? Until you can get a solution.

Oh there are workarounds but having to rename every one of my patches every time I call it up just in case I make changes or having to save every patch again even if I don't remember if it's been edited or not is certainly not optimal. I don't really want to end up with dozens of patches like Bass Edit 1, Bass Edit 2, Bass Edit 3, and so on.

What I'm trying to find out is if this is a bug in AV2 where the edited indicator is supposed to show but doesn't or if this is for whatever reason intended behavior that no indication is shown when a patch is edited.

The answer to that question determines whether this is a bug report or a feature request. I could just contact support but I'm trying not to bother them now as things get pretty busy after any plugin's update release. I was hoping to gain some information and insight here.

The issue where after saving a patch it does not become the chosen patch unless you reload it is another matter. Expected behavior would be that once you save a patch after editing an existing patch it becomes the active or chosen patch not the original patch that was edited. You can see what I'm saying in the screenshots above.

Seems to me like the patch handling is a little wonky in AV2. If we pay very close attention then we can mitigate any possible damage but that's certainly not an elegant long term solution....

Anyway I've spent quite a few hours working on some free presets to upload but I'm driving myself nuts trying to get the levels right. I think I'll just upload them later today so I can go on to making new ones.

[Musical Gym]

^Yes, it would seem that adding the * to a patchname automatically wouldn't be that difficult.
I think I would ask them now. I doubt that they'd have to think about it very long.

[eyeflow]

Hello,

So, with this 2.05 version maybe someone can help me out with some questions
The reason why i ask is because i have so many projects that i can´t afford to loose.

If things doesent work fine with V.2 is it possible to go back to the V.1 with all expansions working, project load as they should etc?

Will all my old expansions open upp correct if i want to open a projenct i did on Avenger 1?

The main question is,
did V.2.05 fix anything regarding the installation? Replace V.1.
I´ve read so much about moving folders, uninstall V-manager, re-install expansions.
I would really appreciate if someone could type down a "step by step" how to do if i decide to upgrade.

Big thanks!
/R

[Hanz Meyzer]

Guys, I can't currently take you seriously with the statement that spike-problems on arm Macs are gone now... Too much not-so-well-thought rubbish was posted here...

Please post a proof, by posting a screenshot of Bitwig's performance monitor playing Avenger 2.05 and a known-to-spike-preset. Or is this just fake news, just as the many times before?

[Jac459]

Guys, I can't currently take you seriously with the statement that spike-problems on arm Macs are gone now... Too much not-so-well-thought rubbish was posted here...

Please post a proof, by posting a screenshot of Bitwig's performance monitor playing Avenger 2.05 and a known-to-spike-preset. Or is this just fake news, just as the many times before?

That's a rude way to ask my friend.

But as I have no pride (or a cheap one), I can do that for 50usd. Should I pm you my PayPal?

[Jac459]

Hello,

So, with this 2.05 version maybe someone can help me out with some questions
The reason why i ask is because i have so many projects that i can´t afford to loose.

If things doesent work fine with V.2 is it possible to go back to the V.1 with all expansions working, project load as they should etc?

Will all my old expansions open upp correct if i want to open a projenct i did on Avenger 1?

The main question is,
did V.2.05 fix anything regarding the installation? Replace V.1.
I´ve read so much about moving folders, uninstall V-manager, re-install expansions.
I would really appreciate if someone could type down a "step by step" how to do if i decide to upgrade.

Big thanks!
/R

Worked the first time for me with no issue whatsoever.
If you are a simple user and installed to default you will have no issue.
If you are a power user and changed the target install location, you will be able to fix it easily.
If you are a simple user and changed the target install location.... Next time don't do it.

[Teksonik]

^Yes, it would seem that adding the * to a patchname automatically wouldn't be that difficult.
I think I would ask them now. I doubt that they'd have to think about it very long.

But my question remains is the * indicator supposed to show up but doesn't which would make the issue a bug?

Or is it something that Vengeance never thought of (I find that hard to believe) ? In that case it would be a feature request.

But an indicator that a patch has been edited is such a common and logical feature that I have to lean more towards it being a bug at this point rather than an oversight but again without more information there is no way to know one way or the other.

It's apparent that such information will not come from this thread so I guess I'll have to contact support on the issue.