Vengeance Producer Suite - AVENGER - 1.8.5 the main thread

[kokotte]

I'm a Reaperist, and no problem here, vst3, no crash, all is fine.
and congratulation for the release

[wagtunes]

Several things...

Wagtunes, I think you will find .21 to be just fine. I have had no issues with it and messed with it all yesterday. I understand you want to finish your sounds first, so do what you think best.

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.

The only complaint here that I have read that I just can't figure out is the "missing content". Maybe I missed the post, but are there specific patches where this happens?

Thanks Jon. Yes, when it comes to GUIs, I am the worst of the complainers. Just check the ArcSyn thread. I have terrible eyes and everything has to be big enough and clear enough for me or I won't get it. Avenger is excellent. Are there some fonts that are a little small? Yeah, but they're not in areas that prevent me from using this thing and the small areas are intuitive features where I don't even need to read the text. The main controls are crystal clear. Maybe it helps that I have a 15 inch monitor and am on 1280 resolution. Don't know.

The missing content error was one of the first things I reported as a beta tester as I was the first one to run into it. It was fixed on my end but maybe on some systems it's still not working. But I definitely did run into it.

[izonin]

I'm experiencing the "high CPU usage when GUI open" too. No other vst does that. Weird.

Overall the synth sounds as expected. The reverb, as previously mentioned, is ace. There are some artifacts in the synthesis, but that's normal with low CPU/low oversampling oscillators.

If I have to describe Avenger in one word: fresh.

[Joey ten]

Hi,
I want to stack Some layers in one osc. I click the plus button, but the sample list doesn't show up. I only see the word samples, and thats about it. Any clue how to solve this!

[Cinebient]

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.

[chk071]

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.

[exmatproton]

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.

I have the same behavior. Also the other way around. Also, when i add the fourth lfo to let's say the WT index knob on the second OSC, the first LFO stops working (still visible in the matrix) and the order in the mod matrix changes to LFO 1, LFO3, LFO 2, LFO 4. Weird...

[cowby]

Serious problem here!

This morning (before went to office), I could start Avenger under Studio one. But now, when I drag Avenger into my project, it shown a white screen with frame. And then it hung up studio one. Have uninstall-reinstall-reboot few times still no luck.

Tried another DAW like Sonar .. same. Anyone has such problem?

[Ingonator]

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".

[exmatproton]

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.

[Elektronisch]

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.

[izonin]

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.

Nvidia.

The strange thing is that the CPU goes up, even when I'm not touching any controls on the GUI. Just opening it already starts loading one of the cores heavily.

[Ingonator]

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.

[wagtunes]

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.

[exmatproton]

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.

Nvidia.

The strange thing is that the CPU goes up, even when I'm not touching any controls on the GUI. Just opening it already starts loading one of the cores heavily.

Same here. I am on an AMD RX480 btw. Should be strong enough for a "simple" UI. Still, 4 of 8 threads are going up to around 50% (taskmanager) on my 4,8GHz clocked i7 4790K (when i open up the UI). When i close the UI again, those 4 threads are going down to around 5 ~ 10 % usage.