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

[gregbinko]

Good evening, I have a question because since version 2.0.7 my MK3 s88 keyboard is no longer recognized and I cannot use it to use it on studio one 7.2. I heard through conversations that maybe it is necessary to downgrade to 1.9 I managed to find it and download it but unfortunately impossible to install it because 2.0.7 is installed in the MK3 keyboard and impossible to change it, unless someone has a solution? I thought about putting the factory default settings back but it keeps the latest version. I don't know how someone can help me to reuse my MK3 S 88 keyboard on studio one 7.2 thank you.

 

[OutrageProductions]

You should ask this question about reverting SW/FW on the device over at the NI Forum. They have all the current answers.
And yes, the latest FW update for the MK3 S series keyboards has an issue [mostly specifically] with S1, with some complaining that the entire keyboard is bricked.
This is stated clearly on the NI update website. and in many places in the NI Forum. No date for any resolution is currently given.

 

[TimC340]

Woah, there... slow down! The issues with the new firmware were resolved (and discussed in detail here in this very thread back in August - see from here. There was a problem with NI Hardware Connection Services in the initial update to 2.0.0 which was resolved with the issue of 2.0.4. These numbers are not related to the keyboard firmware v2 - this is purely HCS within Native Access. There was a temporary workaround - which I went through and was covered in this thread - of going back to HCS 1.9.4 (IIRC) which, in my case, did not fully solve my problem, which was that my particular instance of S1 on one particular computer lost communication with the keyboard - very much as @gregbinko reports. The later updated S Mk 3 firmware 2.0.3 (again, IIRC) did resolve that issue, but not without some further work, and I was back to where I'd been before the v2 updates had been introduced. Everything is now working normally, but - as we also discussed at length - the advantages of the v2 upgrade are not yet available to Studio One users.

To complete the story and save you a trawl through the thread, this is how I eventually solved it: solution

 

[Vocalpoint]

And I am not aware of any MKIII "2.07" firmware - unless something VERY new has just been issued.

Not a single blurb about this on the NI forums.

VP

 

[TimC340]

I think Greg is referring to HCS - the current version is 2.0.7.

 

[dkaimone]

I took a leap of faith and got a Kontrol s49 mk3. So far so good, without the fancy stuff, obviously. Hope that will happen soon. I also updated to Omnisphere 3, which is supposed to have built in integration for the whole Native Instruments keyboards range and certainly my model. I haven't been able to get it to work yet. No problem selecting the right keyboard on the Omnisphere side, but with the keyboard in the required midi mode no matter what knobs I turn nothing happens. In the automation pane top left in S1 I can see that the data is being received but nothing happens in Omnisphere. I've set the track to receive on all midi inputs and selected the keyboard as controller in the yellow selector in the instrument window.

Has anybody been able to get this to work? Hopefully this isn't part of the not yet available fancy integration. I would have thought not, given that the integration is built into Omnisphere, but no luck yet.

I'm teetering on the edge of the 61 key mkIII but kind of waiting for the full integration (since I'm in no rush). The only other two keyboards I was considering was the Korg KeyStage (build quality doubts) and the SL 73 mkii, but that is a totally different beast with few controllers on it.

 

[dkaimone]

Just daydreaming if a hardware company like Presonus might want to release its own controller keyboard? Avid (ProTools) did it with their M-Audio division, at least for a while, after acquiring the company, then selling it just a couple of years later. Seems like not the worst move for Steinberg/Yamaha either.

My thought has been if they don't create their own, they should definitely get fully on board with the NI keys soon. There really isn't anything else like them, warts and all.

 

[Ferdinand]

@sintil8 : I created a custom image with the template using the steps described here:

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

 

[sintil8]

@sintil8 : I created a custom image with the template using the steps described here:

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

View attachment 2013

Thank you for posting.
The information that intrigued me, if you change a patch in Omni 3 do the Filter, Reso, Envelope, etc on your NI MK 3 update to match the settings of the Omni Vst Main display. I am asking about amounts and settings for each patch.

Or, do you have to tweak the encoders on the NI K/Board so that it engages a (Latch function) pick point when rotating the enconders.

I imagine when NI/SO1 are all working in unison the NI display will automatically match exactly the Omni 3 setting when moving from patch to patch?

Kindest regards for posting. Ta!

 

[dkaimone]

So, just to summarize: connecting a S Mk3 to Studio One on a MAC and installing the latest firmware WILL or WILL NOT brick the keyboard? If not, it's just set up to use as a regular controller without the NI bells and whistles?