@jcsteh @chikim @FreakyFwoof @KaraLG84 Hmm I thought they were doing some nice sorting or something as well. So two questions:
1. Is using the controller to twiddle DAW params still subject to the same delayed speech response?
2. If there's nothing complicated happening, does that mean ReaKontrol could do this with hardware other than MK3 Jamie?

@Scott Regarding 2, I wondered that too. The issue is that ReaKontrol doesn't get feedback from the knobs and page buttons unless you're in the mixer view, at which point the user probably wants to use them for the mixer. We could probably have a "fake" mixer view which gets enabled when you press the 4d encoder while in the mixer view or something like that, but it's definitely weird. Plus ReaKontrol doesn't get anything when you touch the knobs, only when you turn them, so you couldn't query the value. @chikim @FreakyFwoof @TheQuinbox @KaraLG84

@Scott KK does map the knobs to CCs when you're on a non-KK track, but those get sent via the main KK MIDI input, not the DAW input. And I'm not sure about the paging buttons nor touching the knobs. @chikim @FreakyFwoof @TheQuinbox @KaraLG84

@Scott Personally, I don't buy NI's argument that this stuff is only possible with Mk3. Mk3 does more of it on the keyboard hardware itself, sure, but that's no reason they couldn't have done it with Mk2. They'd have to move the display and accessibility rendering out of the KK plugin and into a separate service, but it should still be possible. I think they just chose not to. Of course, I'm not an NI dev, so maybe there's something I'm missing. @chikim @FreakyFwoof @TheQuinbox @KaraLG84

@jcsteh @Scott @chikim @FreakyFwoof @KaraLG84 Yeah maybe it's just a matter of resources. I get the impression they're trying to make their actual software more accessible without the keyboard as well, latest Kontakt update is a good example of this. I can now at least browse presets comfortably without using KK, but I hope they'll make editing accessible from the GUI as well.

@ZBennoui Ah, that's great progress. Glad to hear it. I don't own Kontakt 8, so can't benefit from that for non-Player stuff personally, but still good to know. @Scott @chikim @FreakyFwoof @TheQuinbox @KaraLG84

@jcsteh @Scott @chikim @FreakyFwoof @KaraLG84 Yeah I'm still on Komplete 13 ultimate, so only using Player right now, but at least on Mac the accessibility is honestly pretty good. Everything is nicely grouped together, there's a few issues navigating and scrolling, but a lot of that is just due to me using Ableton.

@jcsteh @chikim @FreakyFwoof @KaraLG84 I could make a script that pipes params into a text file. One might already exist for CSI tbh.

@Scott In its simplest form, a config file could look like this:
VST: ReaComp (Cockos) = 22 0 1 2 3
That would give you wet%, threshold, ratio, attack and release in that order.
@chikim @FreakyFwoof @TheQuinbox @KaraLG84

@Scott It'd get nasty for plugins with a variable number of parameters though; e.g. ReaEq when you add/remove bands. @chikim @FreakyFwoof @TheQuinbox @KaraLG84

@jcsteh Maybe match names instead to avoid that problem? @chikim @FreakyFwoof @TheQuinbox @KaraLG84

@Scott You could do that I guess, though it makes the config a bit harder to deal with.
VST: ReaEQ (Cockos) = Freq-Low Shelf | Gain-Low Shelf | BW-Low Shelf
Maybe it needs to be YAML or something like that so we can do items on separate lines:
VST: ReaEQ (Cockos):
- Freq-Low Shelf
- Gain-Low Shelf
- BW-Low Shelf
But anyway, this is a way off, so no idea why I'm musing on it.
@chikim @FreakyFwoof @TheQuinbox @KaraLG84