New NI MKIII S-Series Firmware (v2.0.x) in Studio One 7

[Vocalpoint]

For all users of the latest MKIII NI keyboards - you may have read about the hot new firmware on the block (v2.0.4) that brings a stack of cool new functionality to your favorite keyboard controller. There is a post in the Lounge with a brief discussion on this:

How long before we see the new advanced integration between Komplete Kontrol S mk3 and Studio One?

Just a reminder for those of you who own a Kontrol S mk3.:cool: https://community.native-instruments.com/discussion/47164/kontrol-s-series-mk3-2-0-extended-daw-control-and-accessibility#latest Hopefully, it'll be available soon.

studiooneforum.com

Now it appears - that a few S1 users on the NI forums have taken the plunge on this update - assuming this firmware is just as compatible as the prior version - but if one reads the fine print (in the NI forums) on the thread that introduced this new firmware - you will see this:

And now judging by this new post on the NI forums - this issue is taking a turn and not for the better:

Kontrol mk3 cannot see or connect after firmware update, broken integration with Studio One - Community

This discussion was created from comments split from: Issue with the Kontrol S mk3 new firmware/Hardware Connection Service .

community.native-instruments.com

Then - to add more confusion (via the NI thread above) - we have the NI Tech Lead (TimRaeNI) for the Komplete Kontrol hardware - saying this is a Presonus problem:

We haven't removed anything. Studio One have their own implementation of Kontrol MK3 support built into the DAW, and however they've implemented it is not working with the new firmware update. As the protocol changes are backwards compatible, this points very strongly to a problem in their code.

So Tim (NI) now seems to think S1 v7.22 has a problem and once a user flashes their MKIII board - you lose all DAW control and have no choice but to roll back (via a very convoluted method) - to v 1.9 - in order to get a MKIII board back to a working integration with S1.

What we need is Presonus to connect with NI and see exactly what is going on here. Judging by that thread and the amount of S1 users over there - AND the fact that nobody reads release notes and just runs the updater - seems like a lot of users there - and maybe here too - are going to find out what a dead MKIII board feels like.

Hoping someone (Ari, Lukas, Trucky) can give Presonus a heads-up and maybe initiate a chat with NI.

VP

 

[Vocalpoint]

Update from Tim at NI:

"Guys, the update clearly said studio one is not supported at launch, yet you still decided to update. They have told us they don't have time to work on this yet, but hope to in the future."

Appears that NI has in fact spoken with Presonus and the support for the new (2.0.x) MKIII firmware - is in Presonus's court.

I guess we wait until they have time to suss this out.

Meanwhile - know that updating your MKIII is not supported and you will end up with a dead board for DAW control in S1

VP

 

[TimC340]

I'm the poor sucker whose post started that thread (it was split off from another).

I must warn any Windows-based Studio One users who are also Native instruments Kontrol S Mk3 users: DO NOT UPDATE YOUR KEYBOARD!

The farce over the Windows Hardware Connection Service update has been resolved, so the temptation to do as your keyboard tells you and update it to Firmware version 2 is strong, but resist. I did it and lost all connection between my DAW and the keyboard - Studio One fails to connect to the S Mk3. I've removed and re-added the keyboard several times, without success, In the thread linked above, Tim_NI says you can roll back the drivers to v1.9.4 (from this link: https://www.native-instruments.com/fileadmin/drivers/audiohardware/KSMK3_Updater_3.25.0_Win.zip), but that hasn't worked for me - Studio One Pro 7.22 and my S88 Mk3 still cannot talk to each other.

Tim_NI says it's PreSonus' fault; I disagree. But whoever's fault it is, doing this update will effectively brick your S Mk 3 as a controller and input device for Studio One. It will, however continue to work with their supported DAWs (Bitwig, Ableton, Logic, Cubase and GarageBand), with the added functionality they are touting for users of those products.

Edit: for the rollback to be successful, you also need to downgrade Hardware Connection Services to v1.9.4 (link: clicky).

Further edit:, sadly, rolling back HCS to v1.9.4 does not restore functionality. Once it's broken, it stays broken.

 

[Resonant Serpent]

I had a lot of issues with NI products and Studio One. I found several incompatibilities with S1, Maschine and Reaktor. Last time I checked the bugs were still there. Note that I didn't have any of these issues in four other DAWs.

 

[TimC340]

NI are now suggesting that a full uninstall and reinstall of Studio One is required. With my slightly dodgy 30mb/s connection in my garden studio, a full reinstall of Studio One Pro 7.22 Plus takes around 36 hours (I know - I rebuilt this computer a few months ago!), so I'm going to try a fresh installation of bare-bones Studio One in a new directory. I'll report back sometime tomorrow with my findings.

 

[Midiboy]

You know what my friend used to do in his studio where he didn't access to his WiFi from the house? He literally went and bought a 200' Ethernet cable and ran it from his studio to his house and plugged it into his router when he needed to download stuff.

I don't know how far your garden studio is, if that is even viable, but it's worth a thought? Maybe? What about tethering to your phone? Do you have unlimited data on your phone? Another suggestion...go into your house, or somewhere that has a really good net connection...download the EXE file and the 30 or sound soundset files, copy them to a jump drive, and take them out to your studio and install them. You don't have to download it from the Internet on the same computer you install on.

 

[TimC340]

All of those are great suggestions - I have gigabit internet in the house, and laying a Cat 6 cable is on the cards eventually!

 

[Aifu]

I'm using macOS 13. I did lose control of my S1 7.2.2 after updating the firmware, but after restarting my computer and keyboard, everything worked fine.

The above information is for your reference.

 

[TimC340]

Aifu, that's interesting but this is a Windows-version issue. NI are reporting that they've installed S1 v7.2.2 on a test rig, updated Komplete Kontrol on that installation and it worked (by which they mean that no functionality was lost - the update adds no functionality for Studio One users), however I suspect that's a new bare-bones installation without any significant history of KK updates. I haven't yet tried the bare-bones installation I mentioned above as I've been busy with Real Life (TM), but I may get to try it later tonight.

 

[Aifu]

Aifu, that's interesting but this is a Windows-version issue. NI are reporting that they've installed S1 v7.2.2 on a test rig, updated Komplete Kontrol on that installation and it worked (by which they mean that no functionality was lost - the update adds no functionality for Studio One users), however I suspect that's a new bare-bones installation without any significant history of KK updates. I haven't yet tried the bare-bones installation I mentioned above as I've been busy with Real Life (TM), but I may get to try it later tonight.

Software issues are truly frustrating, as their closed nature and complexity make them inaccessible to ordinary users. I understand your situation, and I hope you can resolve the issue soon. I'm also looking forward to seeing S1 and Kontrol working more effectively together. Good luck!

 

[lokeyfly]

It's a good message/post, particularly for those who just update their specific (in this case MkIII) NI controller. At a risk of sounding a little cold to the meek who've faltered, just the way someone would identify they have a MKII, or any iteration of hardware, if one doesn't read system, DAW, or minimum requirements from the source, I'd probably say shame on you. Of course here, we're looking after our own. A good thing!

NI as often seen, even when they do provide a release that works on your system, caution should be observed. There's just too many manufacturers hinging on being a part of the Komplete Kontrol ecosystem now, let alone NI's own ensuring something fully works with their own products, works equally well with many forms of Maschine, obsolescence, etc.

I'm in a good place currently with NI, but here's a thought. The next time Native Instruments releases something new. Get some feedback and do a little research first. A working studio environment takes time to have everything functioning and playing all nicey, nicey. Do you really want to potentially throw a wrench into the works with some latest bell and whistle. I kind of doubt it.
If not, have fun grunting under your breath, while you potentially re-install. Wink, wink.

If you never even looked at system requirements, you get no wink, and no soup today, for you.

 

[TimC340]

You're right, of course, and I should probably have waited a little longer before installing the update. That said, I think it's likely there's something in my combination of Studio One, my installed proprietary plugins, and my particular installation history that would have had this result however long I'd waited. It's one of those bumps in the road that will be a good story once it's resolved!

 

[Vocalpoint]

If you never even looked at system requirements, you get no wink, and no soup today, for you.

Agreed 100%. Especially when it comes to firmware - every user should be carefully scanning every possible shred of data before pulling the trigger.

I have not yet unpacked my MKIII - but even if I did have it active - there is no way I would subject my studio to a complete uninstall/reinstall of Studio One - just to get this going.

There s something seriously out of wack if a guy has to wipe his entire S1 layout - just to get a keyboard working.

VP

 

[TimC340]

I think in fact I'll be able to resolve this without the suggested full uninstall and reinstall. I'm able to do a new installation while isolating the existing installation, so if it works I can then transfer everything over to the new installation. I hope...!

 

[Vocalpoint]

It's one of those bumps in the road that will be a good story once it's resolved!

This is why - when the time IS right - I want Presonus to tell me it's good to go. Not NI, not via some experimental lab process where everything is removed and reinstalled etc.

Some of us have very detailed installs with very unique layouts and recreating that - is not as simple as clicking Uninstall.

VP

 

[lokeyfly]

I think in fact I'll be able to resolve this without the suggested full uninstall and reinstall. I'm able to do a new installation while isolating the existing installation, so if it works I can then transfer everything over to the new installation. I hope...!

@ TimC340, I read further into the post. Yikes! I'm hoping you can get around the full uninstall/reinstall. Particularly when having a slower network.
Vocalpoint, and a few others here will quite often add a helpful heads-up about such things as NI and others snags.
Good luck, going forward.

 

[TimC340]

Thanks! It's not quite as catastrophic as it might sound; I have a duplicate Studio One installation on my home computer which is not affected by all this. I have a Nektar keyboard attached to that one which of course is working perfectly. I didn't get a chance to look at the studio computer today, and I'm having a day out playing with cars tomorrow, so I'll pick it up on Monday morning.

 

[lokeyfly]

...... I'm having a day out playing with cars tomorrow, so I'll pick it up on Monday morning.

"My Pappy said, "Son, you're gonna drive me to drinkin'
If you don't quit drivin' that Hot Rod Lincoln"
- Commander Cody and His Lost Planet Airmen ‧ 1971

Enjoy!

 

[lokeyfly]

I have not yet unpacked my MKIII - but even if I did have it active - there is no way I would subject my studio to a complete uninstall/reinstall of Studio One - just to get this going.

Understood. Congrats on the MkIII!

 

[TimC340]

"My Pappy said, "Son, you're gonna drive me to drinkin'
If you don't quit drivin' that Hot Rod Lincoln"
- Commander Cody and His Lost Planet Airmen ‧ 1971

Enjoy!

More fun than mucking around with recalcitrant computers!