Why is Ableton setting Komplete Kontrol / Kontakt VST volume to 0 when pressing stop?

Martin Schmid

@Matthew_NI any suggestions?

Martin Schmid

@JesterMgee you mentioned

"Hate to break this to you but this has been an issue for some time, been discussed on the Ableton Forums over the years. Was an issue in V2 of KK and is now still in V3. The issue is KK as it can also happen with 3rd party plugins loaded in KK too."

What other plugins have you had this happen w/ in KK? Any from NI? or just 3rd party as you mention?

I've a thread going w/ NI Support… hoping to get some traction…

JesterMgee

I cannot recall exactly and unsure if it was the vol went to 0, I know that was the case for Kontakt but I am pretty sure I had issues with any instance of KK where on stop of transport the automation would "disconnect" and require you to enable it again after start. TBH I have not produced much for a while now, I did a quick little mix for a Breaking Bad theme I wanted to make a few weeks back just for fun but I didn't automate anything on that. Wish I had more info for ya, I know there was discussion years ago about it on the Ableton forums but I have not bothered to engage there for years now.

I have kind of given up trying to wait it out for improvements and accepted it's just how it is these days and nothing more.

holonology

Hi folks, I posted about this issue a few years ago and was always frustrated at the outcome (which is broadly speaking silence in terms of help with the issue.)

I have, however, found a non-ideal but semi-workable workaround which was staring me in the face the whole time. When using Max for Live a common complaint is devices not recalling session states. This is less to do with automation and more to do with the challenge of some devices effectively needing to stay "live" to recall their settings. As soon as you close the session - your settings are gone.

In this case, there are always 2 tried and trusted things to try. Of course the first is to print to audio, but this is not always ideal, especially at the writing stage. The second is to group the device in an Instrument Rack. What I'm seeing with KK3 in Ableton 12 is that is you put KK in an Instrument Rack and map that to Instrument Rack macros, it will recall the settings. This does of course mean that Ableton is the main driver of your session and the main benefit of Komplete Kontrol in tight integration with controllers etc is somewhat lost. However, if you have a MIDI controller mapped to your session you can effectively never need to open the NI plugin which is handy in its own way.

Not super great, but in my initial tests of this, the automation does reload. I wonder if this is because the movement is bound to the Instrument Rack macros, and this in turn is driving the KK macros, which causes them to stay live because it's not relying on the internal KK mechanism to reset each time? Either way, it seems to work but more testing needed to properly confirm it.