Just received the MK3 keyboard - Feedback
Answers
-
I didn't use a USB-C power supply to do it.
0 -
I'll put it this way. I have an PCie USB C card, another USB C port and multiple USBA superspeed ports. I bought a C hub, and a C to A cable. Tried everything on the trouble shooter. And I tried another laptop with Windows 10, not 11.
The only thing that worked, was a MAC,
0 -
I tried it even with extra power supply and it still failed
0 -
I suspect on Windows, this rash of initial firmware update failures are NOT power supply related..
Instead it's something software related... and a new firmware updater or Hardware Connection Service will fix.
Someone somewhere is coding/testing as fast as they can!
2 -
Yeah! That's the spirit! I'm pretty sure of that too. It kind of sucks most keyboards were delivered in the end of the work week and that it's Friday night. Probably we will get a response next week.
0 -
You may be one of the lucky ones. I have an M2 Mac and the firmware update looks to have bricked my S61. I started a separate thread about it. Either way, definitely not specific to Windows.
2 -
I would say just one thing:
If hundreds of other devices work on our USB C ports (with or without any USB C hub) and this one not…I wouldn’t call it a USB C problem…nor a Windows problem. The right name probably is “A not well done device”…
2 -
Same here, today arrived my S88 MK3, and not working at all. Only waste of my time (7 hours),
I'm tired of it. This is very bad experiences for users.
p.s. for Chris_NI: I don't have custom build PC, I have Asus ROG.
0 -
Hi Chris, I have answered this question in the other thread. I am working on a custom PC with an AMD 8Core Ryzen, 64GB Ram, Windows 10. Meanwhile I have sent over my specs to the Hardware support team of NI via Support ticket. And I am sure, that it is a software issue and not a hardware problem with the keyboard. Funny enough, Cubase recognizes the device and receives the incoming MIDI Data.
0 -
Yes ! , After having 'slept on it' then I have reached the conclusion that the reason that N.I. suggests the use of a hub probably is that it is because of driver problems (built into FW/HW) in the Sxx MK3 versus some USB C chipsset or their drivers why N.I. attempt to use the hub as go-between to alter what the Sxx MK3 is (inter)facing. This is of course purely conjecture on my part me not having any real insights into the inner workings of it all. It do however appear to be the logical conclusion..
0 -
Update from my side, to whom it may concerns.
The firmware update for the S88 MK3 worked perfectly well using my old Mac Book Air !!
So maybe all Windows users that are sitting frustrated in front of your machines, it is not a hardware problem, it is a software issue and I am sure, NI will come with an updated Updater version for Windows.
2 -
I suspect you may have an issue a bit different than what seems to be the one fairly widespread among some windows users.
Still just as frustrating no doubt.
0 -
Ever since the industry has moved exclusively to digital distribution faulty software releases are the norm rather than the exception for most companies. That's because there's no significant cost to release new versions like they had to do in the past so the software testing regimen has been significantly bypassed in many, if not most companies. Especially those that sell primarily to consumer markets rather than corporate markets. Back in the day when I was in commercial software product development it was pretty standard to have a MINIMUM of 3 full time dedicated testers for every single software developer. I seriously doubt, given what I see nowadays, that's very common in software production...and NI is no different from what I can see. Especially when it comes to integration testing with other hardware and software.
I know I'll do what I normally do with these new models of the Komplete keyboard which is wait until the product matures a bit before I jump in. That's why I'm still on Windows 10.
1 -
I prefer the way things are now... messy though it is.
Those that want more stability can lag behind the curve a bit.
Those that want to explore the front edge (pitfalls and all) can help blaze a trail.
Both practices satisfy a consumer's choice to do what they enjoy.
Just needs a bit of structure and communication from the developer.
NI could do a better job of having an available "front edge" and "stable point" for their users.
Easier roll-backs when needed... and more heavily cautioned, but readily available "public betas".
Native Access could have a "public beta" section.. and a "legacy" section too...
2 -
You are absolutely right. I purchased the keyboard with me knowing that it is not a finished product. I was expecting the missing software functionality. And this issue we all have is definitely just a case of bad communication what's going on and is a matter of time to be resolved either by replacement or new software release. With the Ableton Push 3 launch earlier this year I had to wait for my 3rd replacement unit until I got one that is working and in the end they have fixed the issues I had in recent firmware updates.
0
Categories
- All Categories
- 19 Welcome
- 1.4K Hangout
- 60 NI News
- 735 Tech Talks
- 3.9K Native Access
- 15.9K Komplete
- 1.9K Komplete General
- 4.1K Komplete Kontrol
- 5.5K Kontakt
- 1.5K Reaktor
- 365 Battery 4
- 817 Guitar Rig & FX
- 417 Massive X & Synths
- 1.2K Other Software & Hardware
- 5.5K Maschine
- 7K Traktor
- 7K Traktor Software & Hardware
- Check out everything you can do
- Create an account
- See member benefits
- Answer questions
- Ask the community
- See product news
- Connect with creators