The pluggins are reacting to knob manipulation in Cubase 14, but fail to record the automation.
Hello,
i guess you have write enabled on the according track and read for playback.
yes I did
What plugin you try to automate, an fx plugin after the instrument? That's not possible, you can unfortunately only automate the instrument within komplete kontrol
Thats what I'm talking about. I'm opening KK as a Instrument Track in Cubase and open what ever Pluggin in KK, lets say Massive X, Serum or what ever. When enabling write in Cubase, no Automation is recorded.
Have you tried this solution to see if it makes any difference ? : My Kontrol Keyboard's Auto focus Function Does Not Work with Komplete Kontrol or Kontakt in Cubase
1. On the Komplete Kontrol plug-in window, right-click in the top bar area and select Remote Control Editor:
2. In the Remote Control Editor, click the downward arrow and select Get Default Factory Layout.
3. Click Apply.
4. Close the Remote Control Editor window.
.
That should work, the instrument can be automated only fx loaded after the instrument don't work with automation. I tried in Cubase 14 and it works like I described, it even creates a new automation lane as usual in cubase, if I move a knob if write is enabled.
I raised a concern about this too. Example is Avenger, I have a template that works in the previous version of KK V2 and it all controls fine from the keyboard but enable recording in any DAW (confirmed with both Ableton Live and Reaper) and most of the parameters are not sending automation. I say most because there are just a couple that do but seems there is a limitation on how many parameters KK can pass to the DAW and it isn't correct at all.
Testing Avenger outside of KK everything works fine, every parameter can be learned for automation.
Most plugins seem fine but some just do not seem to pass automation through KK, usually ones with a lot of parameters available.
In saying that, you mention Serum and I have no issues (using KK V2, I do not use the latest V3 of KK so could be an issue with that version) so seems possibly a configuration issue maybe? Do you know how to use Reaper? You could test using the free version of that and see if it is the same issue unless you have another DAW to test in. Also, try replace the instance of KK with just the plugin in question on the track as a test and see if that also has the issue or if it works then you can claim the issue is more likely KK. A video of the test would help to confirm it.
