Kontrol 2024 outlook: what was, what now, what next?

1111214161747

Comments

  • Duffcat
    Duffcat Member Posts: 44 Helper
    edited March 14

    Interesting approach. It would be way easier however to just equip the Kontrol with a mic once AI is implemented, which is likely to take us into the next hardware cycle anyhow. AI for Mk4 and please consider left-side Maschine Jam style faders for Mk4. PLEASE!! @Matthew_NI I bet that a user survey would overwhelmingly agree with this. Simplicity is pretty but functionality trumps it for working musicians. (Evidently I’m not working much this week given all the comments I’m making LOL. About to get busy next week so I’ll probably stop hammering poor Matthew with all these suggestions!)

  • nightjar
    nightjar Member Posts: 1,322 Guru

    Yes.. adding a mic to future hardware is a MUST for such input.

    But in the meantime... a "phonetic" approach to "speaking with your fingers" could be language agnostic and also allow for some creative music-related fun.

    Functional and fun. The mullet haircut of data input!

  • Ongey
    Ongey Member Posts: 24 Member

    Thanks Matthew, a well-written and informative roadmap. I would be really excited about the potential of KK MK3, except that at the moment using my keyboard with the KK software is unworkable due to a known and raised bug with Studio One (the 'update KK' bug). I really hope this gets fixed - it's not on the roadmap, but I suspect you only put new features / innovations there, and work on bugs in tandem.

    Otherwise, the potential remains high, especially with onboard processing. I can still use the keyboard with Kontakt 7 - it's not ideal, I don't have access to KK features (Play Assist etc), but it's a workaround... I purchased my keyboard in the knowledge that this is an evolving ecosystem, and I wanted to come along for the ride! Fingers crossed.

    Lastly, no other requests from me - I've got all the features that I need. Except one: the ability to map aftertouch to a MIDI CC (e.g. with my old keyboard, I used to be able to control vibrato on an instrument (e.g. Picked Nylon) with aftertouch mapped to CC11).

  • Matthew_NI
    Matthew_NI Product Team Posts: 1,454 mod

    To be fair, the entire point of this thread is to encourage you to hammer us with suggestions!

  • Matthew_NI
    Matthew_NI Product Team Posts: 1,454 mod

    The Studio One bug is under investigation at the moment. Yeah, there are tons of small things not mentioned on the roadmap.

    Aftertouch is itself a specific type of MIDI event. The way it is transmitted and received is defined as part of the MIDI spec. You're describing MIDI transformation, which is often possible within the content or the DAW itself (I use Logic's Environment for instance). If the keyboard allowed this sort of remapping on-device it could get a little confusing and/or unexpected, no?

  • Hywel
    Hywel Member Posts: 55 Member

    I'm a bit baffled here @nightjar , may I ask in what situation might you need to name stuff/input text on the hardware rather than the KK software or is it to do with NKS development stuff that I know nothing about?

    Hywel

  • nightjar
    nightjar Member Posts: 1,322 Guru

    Well.. NI has stated their goal of keeping the user more deeply immersed in the device experience...

    And MIDI Template editing will be done exclusively on-device.., not the desktop. So there's that need for naming.

  • Matthew_NI
    Matthew_NI Product Team Posts: 1,454 mod

    MIDI Templates, Play Assist (if we add presets) and more things we may do in future

  • Matthew_NI
    Matthew_NI Product Team Posts: 1,454 mod

    The Browser team are aware of the Sub-Banks issue, but may not be able to get to it in Q2.

  • Vagus
    Vagus Member Posts: 489 Guru
    edited March 14

    Questions:

    1. Banner images are currently static, but webp supports animated files. Any plans to enable this in future, as this is handled on device?
    2. During a Kontakt discussion about a year ago, I had a good chat on accessibility with Mario and the Kontakt dev lead, and Mario mentioned that what NI do with accessibility is great, but that it could go further, like Surge XT does....Is there the possibility that one page of parameters could be reserved on each NKS enabled instrument where parameters could be assigned on-device, perhaps using voice accessibility feautres to read out exposed assignable parameters by turning a single knob, with the assignment confirmed via a press of the wheel? Maybe even via midi templates for non-NKS products.

    From an accessibility standpoint for blind users, this might be a game changer.

    For the average user, this would also open up customized mappings for any user, on-device, rather than desktop. I'm pretty sure this would be possible for both VST and KSP if those parameters are exposed by the plugin, or the NKI.

  • chpiatt
    chpiatt Member Posts: 91 Helper

    @Matthew_NI thanks for the response. Any hope for better effects support in the near/mid-term? Any automation support for effects would make the whole NKS ecosystem so much more useful. As is, I have to skip using effects within KK because I (and many others) need to be able to automate parameters for any effects I use.

  • LostInFoundation
    LostInFoundation Member Posts: 4,491 Expert

    Does this have something to do with latest Sonoma 14.4 update? I started receiving mails (last is from Kilohearts) with a warning saying “audio software developers are advising users against upgrading your MacOS to Sonoma 14.4” since it seems many plugins have problems with it.

    It could be useful to state if NI stuff are also suffering of this update, in order to prevent to have many people affected and coming in the forum in need for help


  • LostInFoundation
    LostInFoundation Member Posts: 4,491 Expert

    I strangely feel comfortable with how text inputting works on the M+, with the 4d encoder allowing both gestures: turning it but also pushing it up/down, left/right. A good combination: turning to move inside a line, but also up and down to move from one line to the other. And then click to select

  • DunedinDragon
    DunedinDragon Member Posts: 975 Guru

    I know I'd be very comfortable with it. It's pretty much the same gestures you use to navigate text entry with your remote on streaming TV channels.

  • Duffcat
    Duffcat Member Posts: 44 Helper
    edited March 14

    It would be good for Kontrol on-device images to correspond to the area in the GUI that is being adjusted. This way we could easily jump between device and computer GUI if and when needed. This may take too much work though… a full hi-res image of the GUI that can ‘fly around’ the various knob functions may help. This way developers only need to provide the hi-res image with a reference point in it for each knob.

This discussion has been closed.
Back To Top