Vengeance Producer Suite - AVENGER - 1.8.5 the main thread

[m-ac]

As komplete kontrol sends host automation and not midi (apart from CC1), if a parameter hasn't already been mapped in kk, you'll have to map it here yourself first;

Thanks m-ac for your reply. However I do know how to properly map third party vst in KK. I have fully mapped out the presets for all my third party instruments and added the image and JSON files to the right locations, even edited existing templates with a hex editor. I can load all my Avenger presets with images, logos and sound previews and completely mapped controls directly from Komplete Kontrol. I can turn the knobs just fine during a performance, it's just that the automation is not registered within Ableton. This is actually the first time I've encountered this problem. It works perfectly well for Serum, Ana2, Rapid and a bunch of other non-nks vst. I'm happy to hear that you don't have this problem (right?) and so I'm sure this can be solved with the help of support.

Ah, maybe it's an ableton thing (I'm on logic)? Having to add JSON files sounds a bit heavy haha. Hope you manage to get it sorted.

Out of interest, does live not even register mod wheel automation with avenger running in kk?

[gondii]

Maybe it's an ableton thing (I'm on logic)? Having to add JSON files sounds a bit heavy haha. Hope you manage to get it sorted.

Out of interest, does live not even register mod wheel automation with avenger running in kk?

Yeah it's important to me that everything is neat and tidy within KK, since I don't like to use mouse and keyboard during the creative parts of the process. So I read into editing third party instruments and effects as much as I could. I'm quite happy with where I am and aside from using PresetMagician and doing some minor adjustments in the hex code there was no need to go any further into scripting as of yet. A lot of it is just "copy & paste" and adjusting the values. Once you've wrapped your head around it and have done it a few times it gets easy. But it's still a bit crazy to me how many hoops NI makes you jump through...

But good call on the ModWheel, haven't considered that. So since ModWheel and PitchWeel are actually not automation, but midi data (at least in Ableton), they are transmitted and written differently. Both of them are working fine through Komplete Kontrol, including for Avenger. This at least opens a few doors, since this should also be the case for the expression slider and after touch. Still not ideal though, but better. I already got an E-Mail reply from Rene with some additional questions, so I'm hoping there is some easy fix here.

[m-ac]

Maybe it's an ableton thing (I'm on logic)? Having to add JSON files sounds a bit heavy haha. Hope you manage to get it sorted.

Out of interest, does live not even register mod wheel automation with avenger running in kk?

Yeah it's important to me that everything is neat and tidy within KK, since I don't like to use mouse and keyboard during the creative parts of the process. So I read into editing third party instruments and effects as much as I could. I'm quite happy with where I am and aside from using PresetMagician and doing some minor adjustments in the hex code there was no need to go any further into scripting as of yet. A lot of it is just "copy & paste" and adjusting the values. Once you've wrapped your head around it and have done it a few times it gets easy. But it's still a bit crazy to me how many hoops NI makes you jump through...

But good call on the ModWheel, haven't considered that. So since ModWheel and PitchWeel are actually not automation, but midi data (at least in Ableton), they are transmitted and written differently. Both of them are working fine through Komplete Kontrol, including for Avenger. This at least opens a few doors, since this should also be the case for the expression slider and after touch. And I can probably find some work arounds with midi learn. Still not ideal though, but better. I already got an E-Mail reply from Rene with some additional questions, so I'm hoping there is some easy fix here.

It might be worth testing it without your modifications to see if it works, and then go from there.

[gondii]

It might be worth testing it without your modifications to see if it works, and then go from there.

Holy shit, that actually works. Wow, thanks!!!

Edit: Actually no - it seems that Macros and global controls (Volume) don't send automation, but the controls inside the synth (filter cut off, osc 1 controls, etc...) do send automation both with my mapping and the default one. strange. but I'm making progress!

[msvs]

1.6.1 ***BETA changelog (get betaversion by mailing us or visit our FB Avenger group)

- improved: less CPU usage of Multiloops (especially the CPU-spike at the voice start). These are nearly completely gone now!
- added: new feature for OSC sample stacker: each sample slot can have its own key/velocity range where it is played. This is also displayed in realtime. Go to a sample OSC / Edit / chose slot 1-4 of sample stack
- added: Multiloop module: in the context "chord type" you may now chose what should be the priority when playing just single notes / no chords The user can choose that single notes are detected as minor or major chords
- added: modmatrix "duplicate" feature: You can now duplicate entire mod sources with all its targets into other existing sources. You can find this in the mod matrix context menu /duplicate.
- added: massive speed improvements when converting/importing multisamples, shapes, wavetables etc to an expansion. Should now work nearly instantly!
- added: shape batch convert for folders that conains a lot of shape-samples. Just chose the main folder and select "batch convert OSC shapes" to convert everything whats inside into shapes
- added: TAB key switches the OSC tabs / shift+TAB key moves backwards through the OSC tabs
- improved: sample loading time. If you now load large multisamples ( 100MB and more) from the OSC browser, this now goes a lot faster
- improved: loader will notify the user if the license needs a refreshing. It can be done directly on the Avenger loader or -if you want- like before in the V-Man
- fixed: Drum-Routing was disabled and showed "OSC used as FM Source" when OSC1 was used as FM source
- fixed: annoying click-sound on chord change/sample change in Multiloop mode under specific circumstances
- fixed: fixed a memory leak/crash when loading data from an expansion
- fixed: volume of the autoplay previews are now taking the master volume into account
- fixed: chords were not always detected correctly when latch mode was on and OSC chord root note filter was set
- fixed: ARP moving notes stepwise to left or right may have caused grafical bugs in the arp under specific circumstances
- fixed: issue with saving/restoring solo mute state in presets after the implementation of the the solo/mute handling
- MAC: fixed a crash that was related to a not released openGL context after closing the GUI
https://keilwerth-audio-data-2.com/file ... _1_6_1.exe
https://keilwerth-audio-data-2.com/file ... _1_6_1.dmg

[zvenx]

Thanks MS.
rsp

[surreal]

Awesome! Thanks Manuel!

[m-ac]

It might be worth testing it without your modifications to see if it works, and then go from there.

Holy shit, that actually works. Wow, thanks!!!

Edit: Actually no - it seems that Macros and global controls (Volume) don't send automation, but the controls inside the synth (filter cut off, osc 1 controls, etc...) do send automation both with my mapping and the default one. strange. but I'm making progress!

Yeah like I said, that's how it works here until you map those extra parameters yourself. Anyway, glad you're making progress

[gondii]

Yeah like I said, that's how it works here until you map those extra parameters yourself. Anyway, glad you're making progress

Apparently not in Ableton. These parameters are not transmitted to the DAW, even if mapped, most likely because Avenger has too many values and Ableton has a limit of 1024. That's what Rene / Vengeance support said. So in the meantime I will find a work around and hope that the global parameters (incl. Macros) can maybe be re-ordered in a future update or something like that.

Anyway, thanks for your suggestions. Helped me a lot!

[msvs]

yes do a little math, each OSC has hundreds of possible modulations. And since we have 8 OSCS + drums thats thousands of automation parameters. So its better to map a MIDI CC to a specific control - such as cutoff etc and automate the MIDI CC.
Or just use the internal 3 macro dials and 2 macro knobs - they are always automatable and can be assigned with special tasks with Avengers modmatrix. We plan more macros in one of the next updates btw

[gondii]

The point was that within Komplete Kontrol, I can map all the knobs and sliders, but can only automate the first 1024 hard-wired into Avenger, like from a programmed list. The macros are apparently not among them, so even if I midi assign one of them, the automation is not transmitted to the DAW. No matter what I do. So if I want to be able to automate the macro knobs and dials, I have to run Avenger outside of Komplete Kontrol, because from within KK it's not possible. I'm not 100% on the details, but it's something to do with the many assignable knobs of avenger and the limitations of communication between the hosts - a limitation that I just learned about.

Just to be clear, I was never looking to automate all of Avenger's knobs. Just a dozen or so including the macros. But I will have to find a work-around. So while nice, adding more macros isn't helping my specific issue. But it's fine. What I'm hoping is that in the future, the macro values are "rearranged" in an update, so that they are auto-mapped within these 1024, cause then it should work. I suggested it to Rene.

Here is a quick demonstration of my problem.

[m-ac]

The point was that within Komplete Kontrol, I can map all the knobs and sliders, but can only automate the first 1024 hard-wired into Avenger, like from a programmed list. The macros are apparently not among them, so even if I midi assign one of them, the automation is not transmitted to the DAW. No matter what I do. So if I want to be able to automate the macro knobs and dials, I have to run Avenger outside of Komplete Kontrol, because from within KK it's not possible. I'm not 100% on the details, but it's something to do with the many assignable knobs of avenger and the limitations of communication between the hosts - a limitation that I just learned about.

Just to be clear, I was never looking to automate all of Avenger's knobs. Just a dozen or so including the macros. But I will have to find a work-around. So while nice, adding more macros isn't helping my specific issue. But it's fine. What I'm hoping is that in the future, the macro values are "rearranged" in an update, so that they are auto-mapped within these 1024, cause then it should work. I suggested it to Rene.

Here is a quick demonstration of my problem.

Could you swap some of the pre-assigned 1024 parameter spaces and assign the macros instead?

[gondii]

Could you swap some of the pre-assigned 1024 parameter spaces and assign the macros instead?

In the video there are only two values mapped and it‘s still not working. I believe it‘s about the default order, that‘s what I meant with „hard-wired“. I think that this would need to be done on the developer level. Unless I‘m misunderstanding something. To me it just makes sense to prioritize the macros and global controls over some more "obscure" ones several layers down.

I just did a similar test to confirm with Rapid, a synth that should also have about as many assignable knobs as Avenger does. And as expected, a lot of the knobs in the 8th layer fx cannot be automated, just like with Avenger. The difference is just that the global controls and macros can.

[Hanz Meyzer]

Do I still have to re-activate the license each 3 months?

[Buckster]

I thought drum latch via sustain pedal was being added for 1.6 but can't find it ? Sustain works on ARP but not drum sequence