Vengeance Producer Suite - AVENGER - 1.8.5 the main thread

[Trancit]

but they might have different lengths within a multisample. You cant set this globally, you have to do it individually. (Apart from drumsamples, I nearly never use the sample end... why, if you have amp envelopes).
Sure we can make editors for every sample of the multisample, but this is a nightmare to operate with, we want to keep Avenger as easy to handle as possible. Maybe we have an idea to do this without making the current editor crowded.

The top part has some space for making a selector drop down list...
Here you could choose, which sample of a multisample to edit...

Editor.jpg

[stanis1avsky]

yes exactly. Drag and drop 1 sample into the OSC view and this can then be editet with loop points. There is no sample end here, but this we can easily add in the next update

Oh please do this! Thank you!

[Trancit]

By the way... is there any chance to convince Avenger showing it´s GUI a bit faster???

No offense here, loading Avenger from a fast SSD but it´s slow as hell... and not only on initial startup in a project... in Bitwig and FL Syudio it takes more than 6 seconds from clicking on the GUI button of a loaded Avenger till it shows it´s GUI...
Everything else (like Serum , Omnisphere, Synthmaster, Sylenth, ...etc...) loads the GUI in a blink of an eye, while a snail crosses a street faster than Avenger take off it´s clothes...

[Hanz Meyzer]

For macos: The gui works nicely on fast gfx cards like nvidia. But on a intel iris pro (cpu internal), it seems to be quite a device killer. I cannot go higher than lowest framerate setting, it will not speedup. Instead the Macbook Pro becomes veeery hot soon, as long as the gui is opened. For it is ok like this, because I barely use Avenger on such underpowered device anyway. But somewhere in the future, it would be great if Vengeance could improve the gui performance, e.g. using Metal framework (it has like 40x speedup over OpenGL). Or improve the way the gui is resized (I guess it is now fully resized for every frame?, so kind of queue for changed areas etc). Even if there was a "low quality" mode for intel gfx, that would help already (e.g. reducing to 24bit, reducing resolution a bit).

[Raphie]

Gui works great on highest mode on nvidia 1070 gtx on Win10, I can understand the need for Low Quality modes, as long as it doesn’t affect the current quality?

[sircuit]

For macos: But somewhere in the future, it would be great if Vengeance could improve the gui performance, e.g. using Metal framework (it has like 40x speedup over OpenGL).

Amen, brother!

[Ryan99]

Man i really appreciate the passion from manuel here even not nice comments get replied.

Nothing where parawave can compete! after ginding out how u cannot resell rapid it died for me.

Go on avenger!

Rapid must not be selling so well. It's on sale until tomorrow at 45% off at 99 Euros.

[Trancit]

For macos: The gui works nicely on fast gfx cards like nvidia. ...

Gui works great on highest mode on nvidia 1070 gtx on Win10...

Does it really benefit from a better graphic card??? How long does it take for you to open the GUI on an already loaded instance??? Counted from the click on a button till you see the GUI...

[Hanz Meyzer]

For macos: The gui works nicely on fast gfx cards like nvidia. ...

Gui works great on highest mode on nvidia 1070 gtx on Win10...

Does it really benefit from a better graphic card??? How long does it take for you to open the GUI on an already loaded instance??? Counted from the click on a button till you see the GUI...

I think the initial delay somehow has improved in 1.26, but still is around 0.8 second here on a nvidia 1050ti. I guess crazy graphics buffers buildup or copyprotection decrypting is the cause for this. At least I know this delay from lot of software ilok plugins Wild speculation only. The loading time is very fast though.

[sircuit]

On my macbook the first instance inserts and opens in shortly under 6 seconds. The subsequent openings are 1-2 seconds.

[Rommelaar]

My only wish for Avenger is that the developer start using the latest SDK for VST3, since the current one that is used is quite old, and the latest one has more posibilities.

[noiseboyuk]

General question - is there a master list anywhere of all the official and third party sound sets?

[jstorerjet]

just thought you should know i loaded AU into logic and was blasted with idk what variety of noise. At any rate my speakers and ears are not pleased.

[Warehouseparty]

just thought you should know i loaded AU into logic and was blasted with idk what variety of noise. At any rate my speakers and ears are not pleased.

Thx for letting us know, that was quiet helpfull!

Just thought I let you know something: I was driving down the street and my car just stopped without warning. I am not pleased.

[Trancit]

I think the initial delay somehow has improved in 1.26, but still is around 0.8 second here on a nvidia 1050ti. ...

Wow... that´s quite fast against my about 6.5 seconds in Bitwig and FLS... while I´ve seen in Reaper it takes just the half of the time...
What DAW do you use???

Edit:

I just made some tests and I was really surprised how big the differences are... but only with Avenger here (using the onboard graphics of my I5 3570 (should be Intel HD 4600) ):

Winner: Ableton... after initial start (took about 3 sec.) the GUI opens as fast as all my other plugins... press the button and there it is... perfect!!!!!!!!!
Second: Reaper... takes a bit longer on initial start... GUI of an already loaded instance shows up after about 3 seconds...
Loosers: Bitwig/FL Studio ... intial start takes about 8-9 seconds... GUI opens afterwards after about 6.5seconds everytime you hit the button...

Where do these huge differences come from???
The kind how they handle/wrap VST??? But why only with Avenger (while I believe it´s the only OpenGL plugin I have)
Do they access the graphics card in a different way???
First I thought in Bitwig would be some kind of issue with Java (where the GUI is based on) but FLS behaves the same and this doesn´t use Java...