Fix for Kontrol Mk3 firmware update on Windows

124»

Comments

  • PoorFellow
    PoorFellow Moderator Posts: 4,435 mod
    edited February 29

    You are very welcome !

    Incidentally , for what it is worth ! , then while I being a Moderator here then I am not an NI employee and I am still just another user and all I can do is to relay the information given by Matthew_NI. Personally I believe Matthew_NI to be telling the truth, but you know !, when you do neither have the numbers nor the insight then in the end it will be a matter of if you believe the person or not !

  • Matthew_NI
    Matthew_NI Product Team Posts: 1,404 mod
    edited February 29

    They were not USB-C. This is quite different.

    I'm not sure how many ways I can restate that there are issues integral to the USB-C implementation on certain machines, affecting peripherals. We are a peripheral. I have seen other peripherals affected too. Other audio products, hard drives, displays, anything using USB-C can be affected. We've done more to bring awareness to it, out of necessity, and report it directly to the manufacturer(s) than some companies, who simply don't acknowledge that it exists, as indeed the manufacturers also don't.

  • Rob Ainscough
    Rob Ainscough Member Posts: 61 Member

    I'm having this exact same problem and I'm going to RMA the unit to Sweetwater and look for a different company for my MIDI controller … this is frankly ridiculous.

    I'm a software engineer with 37+ years' experience and I've never had the luxury of blaming a specification. I certainly understand specification can sometimes be open to interpretation and vary … BUT knowing (which apparently NI do know that) that is how I write code to deal with those cases that are different … just like coding a website and having to do a lot of work due to how one browser interprets HTML different than another browser … the responsibility lies with me and not me blaming a spec that isn't sufficient.

    Programming 101:

    1. Always operate a timeout specification that isn't zero or infinitely.
    2. Log/trace all events of the process so a user or developer can review to identify issue.
    3. Exception handling always and everywhere it needs to be.

    I wish I had read this thread prior to purchase and I'm EXTREMELY disappointed with NI product team response. My NI KONTROL S88 MK3 is completely useless, just says "Something went wrong" … I can't even get to the point to do a factory reset simply because none of the buttons function when present with this message. Seriously, can't do a factory reset except via the UI?? Come on … that's the entire purpose of a factory reset is to get back to "factory" if something major goes wrong.

    My additional info seems to be under "moderation" for some reason??

    You've lost a customer, one that will never return because of such poorly written software and even worse design/support philosophy. "Something went wrong" … yes indeed it did.

    Rob.

  • Rob Ainscough
    Rob Ainscough Member Posts: 61 Member
  • Ojustaboo
    Ojustaboo Member Posts: 331 Advisor
    edited June 10

    Congratulations on getting it working.

    Personally I really think that this long after launch, people shouldn’t need to come to a forum just to get a product working. Sure my Novation keyboard recommended that I update the firmware, which was one of the first things I did, but it still worked before I did that. Whereas we unbox out nice new S88 and cant to anything until we’ve updated the firmware, worse still is some of us also need to buy a power supply before we get to try this.

    They should include a power supply in their next run of these and they should come preloaded with a newer firmware that allows use out of the box.

    I do really like my S88, but I feel frustrated when I read a post like yours that 9 months after release, this is still happening. It spoils new users experience and as nearly happened in your case, is costing them some customers which is a shame


  • Alex Niedt
    Alex Niedt Member Posts: 7 Member

    Utterly and laughably untrue. My computer is kept meticulously up-to-date and I had to go through the full workaround, which only worked after having disabled driver signature enforcement. Of course it took an hour of web browsing to figure that last part out.

    Over the last year or two, you guys have somehow devolved into having the absolute worst software in the industry. KK MK2 installed like a breeze, but KK MK3 is a nightmare. Native Access 1 works flawlessly, but Native Access 2 is a laggy, unresponsive mess. Kontakt was fine until Kontakt 7, which has absurdly slow instantiation times. One of the Komplete Kontrol software updates broke recall completely. Please, I'm begging you guys to get it together. It feels like watching an ecosystem I've poured vast amounts of money into over the years suddenly burn to the ground.

  • Matthew_NI
    Matthew_NI Product Team Posts: 1,404 mod

    @Alex Niedt this would suggest something specific has gone wrong then, for we have tens of thousands of Windows users who've simply bought and installed the keyboard without issue.

    Did you have a support ticket open at any point in time that I could review?

This discussion has been closed.
Back To Top