M32 compatibility with Kontakt 8

2

Comments

  • Super8boy
    Super8boy Member Posts: 89 Helper

    it’s due to the feature sets of the keyboards. Only MK3 have the processing power to integrate directly with Kontakt like that. It’s been explained time and time again to be fair.

  • MLARS
    MLARS Member Posts: 145 Pro
    edited September 30

    Is it, really? Then provide that technical reference that proves this. Because your explanation does not make sense.

    Also NI has not said any of this in response to my posts.

  • Maciej Repetowski
    Maciej Repetowski Member Posts: 673 Guru
    edited September 30

    Well, maybe they don't like your posts or something :)))

    Just kidding, of course.

    It's not his explanation, it's NI's. Kontakt integration of MK2 controllers is not viable due to technical reasons (not enough processing power inside the controller to talk directly to Kontakt). They've said it many times on this very forum. Kindly use the search function, mate ;)

    Mk2 series are "dumb controllers", all processing was supposed to be done in software via Komplete Kontrol (chords, arp, scales, light guide and so on).

    You can of course suspect planned obsolescence, even if that's the case - Mk2 series launched in 2018, so it is now 6 years old, this is an eternity when it comes to modern technology. Only plain vanilla MIDI controller with class compliant USB interface will stay compatible forever, anything that relies on software will eventually be abandoned. That's why NI is improving MK3 series by putting more and more functions onboard, instead of relying on software.

  • mykejb
    mykejb Moderator Posts: 1,740 mod

    It was said at the time of the MK3 release that the MK2 keyboards didn't have the hardware needed for direct integration with Kontakt. I'm sure @Matthew_NI can confirm this if you need another official confirmation.

  • MLARS
    MLARS Member Posts: 145 Pro
    edited October 1

    In my opinon it sounds like obvious planned obsolescence. I agree with you on that.

    That's why I am so sceptical hearing the explanations. The post I just searched does not show great messaging.

    Also 5-6 years life cycle on Instrument / Controllers is far short in my opinion. 10+ years should be the standard for software updates without shutting out older hardware. Especially now when the midi controller hardware costs 1000+ Euros. A music instrument / MIDI controller is not like a computer you switch out at the same pace as your Macbook Pro (around 5-7 years).

    You can release an iteration every 5 year of the same product, but if you are a hardware instrument / sound maker, the strategy should be to have enough categories of products to release over 10+ years to cover that many customers won't switch products every 5 years.

  • mykejb
    mykejb Moderator Posts: 1,740 mod

    The MK2 isn't being shut out though, it still does the same as it always did.

  • MLARS
    MLARS Member Posts: 145 Pro
    edited October 1

    Still not updated and supported properly in my opinion. That's the complaint.

    You are also a moderator so thinking you have a stake in supporting NI on feedback issues like this.

  • mykejb
    mykejb Moderator Posts: 1,740 mod

    Please, never buy a mobile phone. For example, the basic iPhone 16 supports Apple Intelligence yet the two year old flagship iPhone 14 Pro Max at £1199 doesn't. Would you complain that the iPhone 14 should support something that the hardware isn't capable of running?

    And no, I have no stake in supporting NI and neither do any moderators. We all do this to help people in our own time without payment so I'd respectfully suggest that you keep personal comments out of technical discussions.

  • MLARS
    MLARS Member Posts: 145 Pro
    edited October 1

    A music instrument / mid controller is not in the same category as a smartphone. Comparing the categories does not work here.

    Instrument makers (and fans of those products) sometime think they can emulate computer or smartphone lifecycles - but this is not a feasable comparison. DIfferent use cases, different expectations.

    Modern music instrument categories have and should have much longer lifecycles to be sustainable.

  • Maciej Repetowski
    Maciej Repetowski Member Posts: 673 Guru
    edited October 1

    IMHO, you are not realistic with your expectations about the lifespan of a MIDI controller which relies on drivers and custom software layer to work.

    Also, what’s expensive or not is highly subjective. I run a business, so for me - whatever equipment I buy for my studio is an investment / tax writeoff.

    For a hobbyist, perhaps a cheaper controller would be better suited.

    Anyway, always vote with your wallet.

  • MLARS
    MLARS Member Posts: 145 Pro
    edited October 1

    Agree, always vote with your wallet (and hopefully some feedback here might affect some change)

    Yes, a small studio is likely to switch gear a bit more frequently but IMO a music instrument / controller category is still not comparable to a smartphone or computer category in life cycle. However, if you can, and find it fun to switch gear every 2-3 years, go for it.

    As a counter point some composers still sit on old gen S88 and older midi fader controller (they dont see the need to switch) - so again I still think switching every 5 year is not expected/feasable for every category.

    And yes, like you say, not everyone is running a studio fulltime. Disposable income is different too which affects frequency of purchases.

  • PoorFellow
    PoorFellow Moderator Posts: 4,814 mod

    Is it, really? Then provide that technical reference that proves this.

    QuoteMatthew_NI September 2023 :

    The Kontrol S MK3 has a new on-device rendering engine, capable of rendering metadata and graphics, well, on the device.

    This enables us to do things like the Direct Connection API, for which Kontakt 7 and Komplete Kontrol 3 are our first clients. The keyboard talks directly to the plug-in, but otherwise handles the parameter mapping and graphical representations.

    The Kontrol S MK2 does not have this capability.The logic is hard coded into Komplete Kontrol, which does all of the rendering and processing, before sending the information down the pipe to the keyboard's display. It's "dumb" in a manner of speaking. So it is not as simple as enabling it.

  • MLARS
    MLARS Member Posts: 145 Pro

    Read this. Messaging and reasoning is still wonky.

    Like previously posted, in my opinon this still sounds like obvious planned obsolescence. 

  • PoorFellow
    PoorFellow Moderator Posts: 4,814 mod

    Like previously posted, in my opinon this still sounds like obvious planned obsolescence.

    That is an endless and meaningless discussion where viewpoints depends on ones views on everything on a much grander scale. While I totally agree with you and many others here that electronics such as e.g. midi keyboards ought to have a longer life also with respect to how long time they can keep up with the tech development in the world in general then that alas is not how the world works.

    Anyway , please drop the discussion at least in this thread , this is an AMA for asking relevant questions about Kontakt 8 , not respecting that and derailing the discussion into a discussion about N.I. policies or opinions about that will just make someone come along and remove the derailed part.

  • Vagus
    Vagus Member Posts: 485 Guru

    You don't need a technical reference to know that MK1 and MK2 do not have onboard processors or memory to handle direct API connection and/or on device functions.

    Planned obselescence is very different to end of life cycle.

    Sure, I could still use a laptop from ten years ago, but if it's an Apple laptop, half of it just wouldn't work, and if it's a Windows laptop, it would be ******. It's simply lifecycle management of a product - to launch new features, you need new hardware.

Back To Top