ISSUE: KK not reporting parameters correctly for plugins with large number of parameters (Avenger2)

Options
JesterMgee
JesterMgee Member Posts: 3,374 Expert
edited July 7 in Komplete Kontrol

So just discovered that with Avenger2 while you can map any parameter within the plugin as a macro control, KK is not reporting 90% of the parameters to the host and so most parameters (including macros) canont be recorded!

I've never really used Avenger myself but I was contacted by a user using KK V3 reporting most of the parameters he tries cannot be recorded in Ableton when used via KK but can be recorded when loaded direct on a track.

I am on Windows and can confirm this issue also in KK V2 (VST3)

Using Reaper I can see the list of parameters that KK reports from Avenger is completely broken:

P5hcq4l0g0Y2NaCo.png

If I load Avenger direct on the track, it is reporting fine:

g0wzMXOANx8j4Uf8.png


Since I don't have any faith in wasting time reporting this in the Beta anymore, maybe someone would like to chuck this one also in the void. My hunch is the parameter count of Avenger (which is huge) exceeds the max that KK was designed to handle, likely because it still has the VST2 parameter limitation applied to the VST3 side of things. In any case, it's another popular plugin that is unsuitable for use in KK.

Back To Top

Categories