Feedback Komplete Kontrol 3.1.X

First of all, thanks to NI for providing your new KK 3.1.1 release which finally allows window resizing. From my perspective still one important thing is missing (which also applies to Kontakt 7 btw.):

In order to create a "real" full screen app, please finally activate the "maximize" icon in the KK3 top menu bar (currently grayed-out only), subsequently allowing users to maximize KK to its full and "monitor-filling" screen size by just one single click. Thank you.

However, the reason for my feedback is that I have experienced some inconsistencies when operating the current KK 3.1.1 release in conjunction with my NI S61/MK2 keyboard. As a pre-requisite and to comprehend what I'm talking about, let's assume that the "PIN" icon/switch in the KK3 browser menu is not activated. In theory, this should "force" any related VST plugin view to appear after its associated preset has actually been selected out of the KK preset browser list and loaded accordingly.

Case 1 - Navigating via PC keyboard (without MK2 controls):

When clicking on any particular NKS preset appearing in the KK3 app browser list (or when scrolling through the same preset list by using the PC keyboard's arrow keys etc.), the currently selected entry can be "pre-heard" accordingly. By pressing "ENTER" on the PC keyboard, the related sound for the currently highlighted preset/library will be finally loaded into memory while the KK3 browser view will also be automatically exchanged by a related VST plugin view (which is actually occupying the same window). Now, that's not what has been really appreciated by users, but this seems to be the "new way" KK3 is supposed to work. Fair enough, let's move on.

Another way to achieve the same result is to use the PC mouse and to double-click directly on a particular entry within the KK3 browser list; the associated VST plugin window will also be presented correctly on the screen by taking over the window space of the previously opened browser. However, whenever double-clicking in such a way, the "pre-hear" function will be even triggered twice, which was still not the case in KK2. Well, that's not really an issue; however, it's somehow annoying and should be pointed out. After all, it soon feels like an "audible bug" whenever working with the mouse and using the browser for longer than a few minutes only. Maybe NI can take a look and improve that situation. Thanks.

Case 2 - Navigating via MK2 keyboard (and this is the actual problem I'd like to report):

When performing exactly the same procedure as before directly from an MK2 keyboard, namely first browsing via the MK2 knobs through the actually presented NKS preset list and then stopping at a particular entry, the related sound(s) can also be "pre-heard" properly. No complains here; the current preset selection will not only be properly reflected on the MK2 display, it will also be shown on the app's screen, as it should.

However, after pressing the "LOAD" softbutton on the MK2 keyboard (or pressing the "3D KNOB" there instead) the preset will be finally loaded up, but only the MK2 display will change its actual view. Loading a particular preset via MK2 will obviosuly not trigger the related VST plugin view to appear on the PC screen simultaneously, even if the "PIN" icon/button in the KK3 app (supposed to prevent the content browser view from being changed) has always been turned off. The expected communication between MK2 and the KK3 app is simply not existing in this special situation (or is currently not working as intended).

In other words, especially when exclusively navigating on an MK2 kexboard directly, there is currently no way to open the associated VST plugin window of a newly loaded preset in the app via MK2 controls, unless the VST plugin window will first be opened manually within the KK3 app, e.g. by using PC peripherals. Please fix this, as this is obviously a bug, not a feature.

Special EDIT:

And even if the VST plugin view has been finally activated manually within the KK app as described above, the "browser content view" cannot be recalled again from the MK2's controls only. Even if pushing the "BROWSER" button there, the VST plugin view will remain to be displayed within KK3, instead of switching back accordingly to the browser view. Please also consider this reverse case.

Thanks again.

@Matthew_NI:

I'm fully aware that NI's main focus is currently set on the new MK3 keybard and its related interworking with the KK3 app, but please don't forget to test with older hardware as well. Please always keep in mind to (re)implement all those functionalities that have flawlessly been working already in KK2. If NI really intends to win back the favor of existing users owning older NI gear (or those who are willing to switch to newer ones in the future), please honestly compare previous features carefully with the ones you plan in the future and align those by introducing related KK3 equivalents as soon as possible.

In fact, in the described case above you wouldn't even have to bother to switch between two different KK3 views within the same app window when it would be much easier to present both views at the same time (like it was possible before). Exactly that's what has anyway been requested many times by die-hard users, as only this can be "the real thing" when it comes to "resizing options" and "full screen views". Thanks for listening.