Vengeance Producer Suite - AVENGER - 1.8.5 the main thread

[Hanz Meyzer]

Those crackles won't go away if you closed the GUI, I would say it's caused by the OSCs at voice initalization. Then there is a spike, and this spike will sum up with lot of voices, after initilization of the OSCs, the crackling usually goes away, playing all voices without crackling, so it happens mostly at sound start.

[surreal]

Those crackles won't go away if you closed the GUI, I would say it's caused by the OSCs at voice initalization. Then there is a spike, and this spike will sum up with lot of voices, after initilization of the OSCs, the crackling usually goes away, playing all voices without crackling, so it happens mostly at sound start.

As far as I can recall some of avengers core sound processes where reliant on the GPU in the beginning stages of the development and thats why Avenger gave an inmpression that it was "light" on cpu.. that is difficult for me to assess though cause my i7 cpu uses the imbeded onboard intel video card which is powerd by my cpu anyway

[KenjiDeVries]

As far as I can recall some of avengers core sound processes where reliant on the GPU in the beginning stages of the development

Could you elaborate this some more?

[surreal]

https://www.steinberg.net/forums/viewtopic.php?t=156690

Check this out, maybe this helps.

[magicmusic]

Those crackles won't go away if you closed the GUI, I would say it's caused by the OSCs at voice initalization. Then there is a spike, and this spike will sum up with lot of voices, after initilization of the OSCs, the crackling usually goes away, playing all voices without crackling, so it happens mostly at sound start.

As far as I can recall some of avengers core sound processes where reliant on the GPU in the beginning stages of the development and thats why Avenger gave an inmpression that it was "light" on cpu.. that is difficult for me to assess though cause my i7 cpu uses the imbeded onboard intel video card which is powerd by my cpu anyway

I use the intel onboard graphic with DVI. the crackle happen when i close edit window too. crackle is sync to arp step. maybe other can do test as see in youtube video i upload in some posts ago ?

If avenger use GPU to render audio, i can try disable that. is that possible ?

My CPU is 1 year ago released from intel 8600k and it is fast. the crackle on arp step i get with cubase, reaper and mixcraft same. other synths have not such problems.

[surreal]

Hey there. First of all: I really like Avenger. Besides the (all over) positive aspects, and before writing a report to Rene, i would like to ask a question to the communitiy here, about the (well discussed) performance issues, regarding GPU vs CPU usage.

In my case, I can load up to 20 instances of avenger. The CPU usage looks okay (well, of course depending on what kind of presets i load). The GPU *PROCESSING* usage as well.

My Problem is: The GPU *MEMORY*.

Yes, my system specs are really individual, and my GPU is lightly outdated. But: Is there anybody out there, who could confirm this?

When opening a (previously saved) cubase project i.e., with all Avenger GUIs closed, there is absolutely no Problem. But when opening the GUis, one after another, and even when closing them right after...

I will get a GPU Memory overload...

It simply looks like, the GPU Memory is not unloaded after closing the GUI.

This is a first Screenshot, with only 2 Instances opened:

Bildschirmfoto 2017-09-29 um 17.57.53.png

Could this not be a factor?

[surreal]

Those crackles won't go away if you closed the GUI, I would say it's caused by the OSCs at voice initalization. Then there is a spike, and this spike will sum up with lot of voices, after initilization of the OSCs, the crackling usually goes away, playing all voices without crackling, so it happens mostly at sound start.

Also sounds like the old pentium p4 denormalisation symptom... wonder what type of cpu the gpu of videocards are now?

[godly]

Those crackles won't go away if you closed the GUI, I would say it's caused by the OSCs at voice initalization. Then there is a spike, and this spike will sum up with lot of voices, after initilization of the OSCs, the crackling usually goes away, playing all voices without crackling, so it happens mostly at sound start.

As far as I can recall some of avengers core sound processes where reliant on the GPU in the beginning stages of the development and thats why Avenger gave an inmpression that it was "light" on cpu.. that is difficult for me to assess though cause my i7 cpu uses the imbeded onboard intel video card which is powerd by my cpu anyway

I use the intel onboard graphic with DVI. the crackle happen when i close edit window too. crackle is sync to arp step. maybe other can do test as see in youtube video i upload in some posts ago ?

If avenger use GPU to render audio, i can try disable that. is that possible ?

My CPU is 1 year ago released from intel 8600k and it is fast. the crackle on arp step i get with cubase, reaper and mixcraft same. other synths have not such problems.

Could be over asio?
That's still a big problem over asio with latency and cracks.
Wasapi no problems.
I hope this gets fixed for once guys. It's important!

[msvs]

I have AMD Radeon HD7700 (100% passive - no fan)

btw generally I am not a fan of mixing gaming pc, internet surfing and office pc and your studio music working pc

[godly]

I have AMD Radeon HD7700 (100% passive - no fan)

btw generally I am not a fan of mixing gaming pc, internet surfing and office pc and your studio music working pc

The problem is in the asio driver. My PC is dedicated to music only and optimised, a recent performant 3ghz with ssd. All works perfect, on wasapi but not on asio. I bought a new soundcard, and another soundcard from another brand. Problem stays or gets worse.
I'm on Motu mk4 now. So it's not toy quality.
I managed to improve the latency by using jbridge. But still...
It's a known and reported problem. I hope this will be fixed one day.

Avenger is my best plugin but still has major issues to fix. Otherwise it would be my nr 1 workhorse.

[msvs]

I have RME audio cards and their Asio drivers are stable as hell

[Trancit]

...I managed to improve the latency by using jbridge. But still...

What do you use jbridge for???

[JoaquinAce]

I also had some crackles in Live 10.18 and I have a RME interface, i7-8700@4.2Ghz and 32GB mem.

[SouledOut]

I also had some crackles in Live 10.18 and I have a RME interface, i7-8700@4.2Ghz and 32GB mem.

You guys need to check if your PSU is sufficient to supply enough wattage to run your computers. First of all, change the energy saving theme in Windows to high efficiency or whatever that's called. If that don't fix the problem, upgrade the PSU. We musicians like to connect a lot of USB devices (interfaces, MIDI keyboards, perhaps some other outboard gear), like to have a good gfx card for gaming and all of those devices suck power. I was getting a lot of crackles from my audio interface (Tascam US 22) just by moving my mouse cursor around until I upgraded to 900W PSU.

[Hanz Meyzer]

Avenger never used GPU for audio calculation That would be the first commercial VST doing so (except UAD) and then it would use 0.5% I think you can save your time searching for a hardware problem. There is none, it is software made.

I would appreciate if that spiking problem now finally was accepted by the team as being a in reality existing problem. There needs to be some optimization to prevent such spikes. Since msvs has a slightly more recent i7 than me (I guess one generation or so?), the only real diff seems to be additionally provided cpu instruction sets, which will be targeted by the c++ compiler automatically (except Rene is using custom assembler inside). That's why I assumed it could be the compiler setting. Or, as stated by surreal, a denormalization problem, which needs to be fixed manually within the code then, also recent common dsp libs still are doing that manually.