Vengeance Producer Suite - AVENGER - 1.8.5 the main thread

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
Post Reply New Topic
RELATED
PRODUCTS
VPS Avenger VPS Avenger 2

Post

Ingonator wrote:
exmatproton wrote:
Ingonator wrote:
Cinebient wrote:Is that the supposed behaviour that when i delete an LFO (tab) the modulation is still going on and the deleted LFO is still present in the mod matrix.
Just checked this. It looks like if you for example use LFO 2 to modulate the wavetable index and then remove LFO 2 it will automaticlly use LFO 1 for this whie in teh mod matrix still LFO 2 is shown as a source.
If you close and re-open the GUI the "LFO 2" label in the mod matrix is replaced with "LFO 1".
Hmm, that would explain it...not a very handy/practical solution. Especially when using a lot of modulating...

*edit* No Ingo.
After re-opening the UI, LFO 1 is still there (in the LFO section + the mod matrix), but not doing anything. The mod is still assigned as well...

*edit 2*
I can't delete LFO 1. When i delete LFO 2, LFO 1 takes over the properties and assignments of LFO 2. :?:
That's exactly what i just mentioned. Deleting LFO 2 will automatically lead into using LFO 1 instaed and you could not delete LFO 1 indeed.
If you want to remove the LFO mod source completely from the matrix you have to right-click on the source and select "---" (the last in the list) as a source which will remove it.
True. But i mean, when i delete lfo 1, when lfo2 is still intact.
When i delete lfo2, indeed, lfo 1 is taking over the properties of lfo2.

Post

chk071 wrote:
izonin wrote:I'm experiencing the "high CPU usage when GUI open" too. No other vst does that. Weird.
Just wondering, but, do you happen to have a AMD graphics chip? As Manuel said, the GUI is being hardware accelerated, i figure that, if they power/performance of the graphics chipset is not sufficient, it rather stresses the CPU. And, as i also figure that that is optimized, or tested rather for Nvidia chipsets, it could mean that other chipsets might not perform as well. My totally unscientific theory.
My fan goes into overdrive (relative to how large the GUI is), even when I'm not playing anything on Avenger. I'm assuming the integrated GPU causes this, as my i7 CPU isn't even breaking a sweat.

Post

wagtunes wrote:
Elektronisch wrote:
thejonsolo wrote: On the GUI "font is unreadable". See that fellow I just commented to (wagtunes)? If the GUI was bad or unreadable he would be the FIRST to complain about it. Yet he has not. I do not know what was trying to be shown in the picture with Bazille, but both were highly viewable. On my system it works fantastic. I tried it in 4k and have had no issues. While the GUI is large, there is a lot going on there and I see/saw no other way to present it and make the visuals still pleasingly aesthetic.
Either you lying to defend or your eyes has sharpening augmentation because here Avenger font is small and blurry as ****. And picture with Bazille is to show that by comparison. And there is no denying Aavenger font in that picture is unreadable where' s Bazille also having small font is readable. I really dont understand why you should lie about that when its so clear in picture...Also im not the only one who has mentioned this so it cant be bad eyes right?

On the other hand i do believe it might not look blurry on 4k display. But here on Dell ultrasharp at 1080p, it does.
Well, here's how it looks on my 15 inch monitor at 1280 res. And my eyes are the worst and I have no problems at all.

Image
Actually i can read what is written in your picture.

Scaling issues/bug with different resolutions?

Post

Elektronisch wrote:
wagtunes wrote:
Elektronisch wrote:
thejonsolo wrote: On the GUI "font is unreadable". See that fellow I just commented to (wagtunes)? If the GUI was bad or unreadable he would be the FIRST to complain about it. Yet he has not. I do not know what was trying to be shown in the picture with Bazille, but both were highly viewable. On my system it works fantastic. I tried it in 4k and have had no issues. While the GUI is large, there is a lot going on there and I see/saw no other way to present it and make the visuals still pleasingly aesthetic.
Either you lying to defend or your eyes has sharpening augmentation because here Avenger font is small and blurry as ****. And picture with Bazille is to show that by comparison. And there is no denying Aavenger font in that picture is unreadable where' s Bazille also having small font is readable. I really dont understand why you should lie about that when its so clear in picture...Also im not the only one who has mentioned this so it cant be bad eyes right?

On the other hand i do believe it might not look blurry on 4k display. But here on Dell ultrasharp at 1080p, it does.
Well, here's how it looks on my 15 inch monitor at 1280 res. And my eyes are the worst and I have no problems at all.

Image
Actually i can read what is written in your picture.

Scaling issues/bug with different resolutions?
Possible. Could be just about anything. Graphics cards too. Who knows? Too many variables to know.

Post

exmatproton wrote: True. But i mean, when i delete lfo 1, when lfo2 is still intact.
When i delete lfo2, indeed, lfo 1 is taking over the properties of lfo2.
Deleting LFO1 does not actually seem to work. BTW if you no longer need 2 LFOs but want to use the settings of LFO2 in LFO 1 you could use the copy and paste feature (right-click on the LFO label) to transfer the settings and then delete LFO 2.
Ingo Weidner
Win 10 Home 64-bit / mobile i7-7700HQ 2.8 GHz / 16GB RAM //
Live 10 Suite / Cubase Pro 9.5 / Pro Tools Ultimate 2021 // NI Komplete Kontrol S61 Mk1

Post

Ingonator wrote:
Cinebient wrote:Is that the supposed behaviour that when i delete an LFO (tab) the modulation is still going on and the deleted LFO is still present in the mod matrix.
Just checked this. It looks like if you for example use LFO 2 to modulate the wavetable index and then remove LFO 2 it will automaticlly use LFO 1 for this whie in teh mod matrix still LFO 2 is shown as a source.
If you close and re-open the GUI the "LFO 2" label in the mod matrix is replaced with "LFO 1".
Mmhhh....i added a new LFO 4 f.e. to modulate the flip of the pitch envelope...works great. But when i now delete the LFO 4, the modulation of the pitch envelope´s flip is still going on and in the mod matrix there is still LFO 4?

Post

Ingonator wrote:
exmatproton wrote: True. But i mean, when i delete lfo 1, when lfo2 is still intact.
When i delete lfo2, indeed, lfo 1 is taking over the properties of lfo2.
Deleting LFO1 does not actually seem to work. BTW if you no longer need 2 LFOs but want to use the settings of LFO2 in LFO 1 you could use the copy and paste feature (right-click on the LFO label) to transfer the settings and then delete LFO 2.
Indeed. Deleting LFO1 was the thing i meant.
Copy/paste was indeed the thing i did.

Btw, anyone have an idea how to snap edit the different editors (pitch, mod, etc..) on the horizontal scale? And is snapping possible, even when sync is off?? I can't find anything about this in the manual...
Last edited by exmatproton on Fri Dec 02, 2016 5:00 pm, edited 1 time in total.

Post

Cinebient wrote:
Ingonator wrote:
Cinebient wrote:Is that the supposed behaviour that when i delete an LFO (tab) the modulation is still going on and the deleted LFO is still present in the mod matrix.
Just checked this. It looks like if you for example use LFO 2 to modulate the wavetable index and then remove LFO 2 it will automaticlly use LFO 1 for this whie in teh mod matrix still LFO 2 is shown as a source.
If you close and re-open the GUI the "LFO 2" label in the mod matrix is replaced with "LFO 1".
Mmhhh....i added a new LFO 4 f.e. to modulate the flip of the pitch envelope...works great. But when i now delete the LFO 4, the modulation of the pitch envelope´s flip is still going on and in the mod matrix there is still LFO 4?
It is similar to what i explained with 2 LFOs. If you delete LFO 4 then LFO 3 will take over the modulation and if you close and re-open the GUi LFO 3 will be shown as mod source in the mod matrix.
If you want to completely remove both the LFO modulation AND the LFO 4 you have to remove both LFO 4 and the mod source in the mod matrix (by right-clicking on the source (e.g. LFO 4 or LFO 3) and then using "---" from the list in the drop-down menu).

If a mod source is modulating multiple destinations you could also just delete a destination no longer needed (again with the right-click and choosing "---"). If you remove the destination at a source where there is only one destination you will also remove the source.
Last edited by Ingonator on Fri Dec 02, 2016 4:51 pm, edited 1 time in total.
Ingo Weidner
Win 10 Home 64-bit / mobile i7-7700HQ 2.8 GHz / 16GB RAM //
Live 10 Suite / Cubase Pro 9.5 / Pro Tools Ultimate 2021 // NI Komplete Kontrol S61 Mk1

Post

Ingonator wrote:
Cinebient wrote:
Ingonator wrote:
Cinebient wrote:Is that the supposed behaviour that when i delete an LFO (tab) the modulation is still going on and the deleted LFO is still present in the mod matrix.
Just checked this. It looks like if you for example use LFO 2 to modulate the wavetable index and then remove LFO 2 it will automaticlly use LFO 1 for this whie in teh mod matrix still LFO 2 is shown as a source.
If you close and re-open the GUI the "LFO 2" label in the mod matrix is replaced with "LFO 1".
Mmhhh....i added a new LFO 4 f.e. to modulate the flip of the pitch envelope...works great. But when i now delete the LFO 4, the modulation of the pitch envelope´s flip is still going on and in the mod matrix there is still LFO 4?
It is similar to what i explained with 2 LFOs. If you delete LFO 4 then LFO 3 will take over the modulation and if you close and re-open the GUi LFO 3 will be shown as mod source in the mod matrix.
If you want to completely remove both the LFO modulation AND the LFO 4 you have to remove both LFO 4 and the mod source in the mod matrix (by right-clicking on the source (e.g. LFO 4 or LFO 3) and then using "---" from the list in the drop-down menu).
If you first remove lfo 4 (for instance), then the mod sign at the parameter is still there, but you can't remove it. If you first remove the mod sign at the parameter, you can remove the lfo and there will be no signs (little triangle) at the parameter...i am sure these niggles will get fixed. Kinda annoying behavior.

Post

exmatproton wrote:
Ingonator wrote:
Cinebient wrote:
Ingonator wrote:
Cinebient wrote:Is that the supposed behaviour that when i delete an LFO (tab) the modulation is still going on and the deleted LFO is still present in the mod matrix.
Just checked this. It looks like if you for example use LFO 2 to modulate the wavetable index and then remove LFO 2 it will automaticlly use LFO 1 for this whie in teh mod matrix still LFO 2 is shown as a source.
If you close and re-open the GUI the "LFO 2" label in the mod matrix is replaced with "LFO 1".
Mmhhh....i added a new LFO 4 f.e. to modulate the flip of the pitch envelope...works great. But when i now delete the LFO 4, the modulation of the pitch envelope´s flip is still going on and in the mod matrix there is still LFO 4?
It is similar to what i explained with 2 LFOs. If you delete LFO 4 then LFO 3 will take over the modulation and if you close and re-open the GUi LFO 3 will be shown as mod source in the mod matrix.
If you want to completely remove both the LFO modulation AND the LFO 4 you have to remove both LFO 4 and the mod source in the mod matrix (by right-clicking on the source (e.g. LFO 4 or LFO 3) and then using "---" from the list in the drop-down menu).
If you first remove lfo 4 (for instance), then the mod sign at the parameter is still there, but you can't remove it. If you first remove the mod sign at the parameter, you can remove the lfo and there will be no signs (little triangle) at the parameter...i am sure these niggles will get fixed. Kinda annoying behavior.
Well, a bit unconventionell maybe but i try to live with it.
I really love the things i can do with Avenger so far.
There is another little thing i can´t figure out (might be user error of course).
I just can set the sync timing of the pitch envelope to quarter or off but triplet doesn´t work.

Post

db3 wrote:
chk071 wrote:
izonin wrote:I'm experiencing the "high CPU usage when GUI open" too. No other vst does that. Weird.
Just wondering, but, do you happen to have a AMD graphics chip? As Manuel said, the GUI is being hardware accelerated, i figure that, if they power/performance of the graphics chipset is not sufficient, it rather stresses the CPU. And, as i also figure that that is optimized, or tested rather for Nvidia chipsets, it could mean that other chipsets might not perform as well. My totally unscientific theory.
My fan goes into overdrive (relative to how large the GUI is), even when I'm not playing anything on Avenger. I'm assuming the integrated GPU causes this, as my i7 CPU isn't even breaking a sweat.
Noticed the same thing. This is the only plugin that causes my laptop fan to hit full tilt, even when playing no notes at all and while having all effects turned off. It's quite weird actually.
"Wisdom is wisdom, regardless of the idiot who said it." -an idiot

"They don't ban hate speech; they ban speech they hate." -an oracle

Post

A hint for Windows users (using Win 10 64-bit here):
If on Windows you want to add an Avenger content file via drag & drop from Windows Explorer (for example also with my free wavetables pack available from the free content page at the official website) you have to start the host without administrator rights (which is an option when starting programs in Windows and could be also done automatically).
Ingo Weidner
Win 10 Home 64-bit / mobile i7-7700HQ 2.8 GHz / 16GB RAM //
Live 10 Suite / Cubase Pro 9.5 / Pro Tools Ultimate 2021 // NI Komplete Kontrol S61 Mk1

Post

Could it be that the GUI refresh rate is not capped, say at 30fps? The controls action is extremely smooth, though.

I had this on a game engine, where the fps would go to over 1000fps, maxing out the CPU.

Post

izonin wrote:Could it be that the GUI refresh rate is not capped, say at 30fps? The controls action is extremely smooth, though.

I had this on a game engine, where the fps would go to over 1000fps, maxing out the CPU.
The website says 60fps... But that shouldn't cause that overload either especially on the cpu.

Post

like I said earlier, an ECO mode with lower hz rate will come

Post Reply

Return to “Instruments”