Seriously dissaponted with my new S61 Mk2

This is spot on. The regression in feature set (removing MCU) wasn't mentioned anywhere in the NI marketing materials, and it being called "MK2" implied it was a direct upgrade just like Maschine is from one gen to the next. Very misleading.

 

Indeed, thank you JesterMgee. And, I feel like we have been very clear on this. Further explanation should not be needed. Adil @ NI, can you have your folks bring a fix? It's kind of a big deal.

 

If somebody is a journalist here, why not to write an article about NI‘s Customer Support behaviour incl. Product politics like Kore, the missing MCU Feature in a Upgrade and so on...Or if somebody has enough time and money prepare some legal action and take NI to the Court...Just for fun, i would bet, the MCU support is back in no time...

 

NI doesn't care about negative press it seems.

 

I run Previous Magazine, but as Behringer/Music Group has proven recently, you can file a lawsuit against publications and forum users for defamation/libel: http://www.factmag.com/2018/06/20/behringer-dave-smith-libel-case/
With $59m in investment, NI could probably tie most people up in knots and drag out the lawsuit for longer than they can afford, which is a very common tactic.

I think the best thing to do is to just keep pointing out the facts to NI, to other users, to would-be buyers, and keep citing the sources of NI's own marketing materials and communications.

Further food for thought: Marcel claimed that MCU isn't "very important". So if it isn't very important, why not advertise that it's been deprecated in the marketing materials in favor of select, deeper integration with specific DAWs? That would have been fair enough, and we wouldn't have been missold these products.

 

I surely would have just kept my MK1 or gotten a Maschine MK3. We couldn't even use our templates when we bought these.

 

Marcel has become famous. Good Job NI way to handle this situation

 

But for the users of the few daws that k mk2 works with they are very happy because of the deeper integration. So some people upset some get more functionality.

I would like maschine and kk to more easily control the transport of pro tools. But I'm not too upset about it. I just have an extra keyboard for now. I don't think transport control of protools is ever coming.

 

If all you want is transport then map some of the white buttons using cc.

 

How many times are you going to cite this as a solution and be told it is unacceptable? One of my colleagues is legally blind. This does NOT tie in with NI's accessibility support (a voice over system), nor my colleague's muscle memory.

You have misunderstood the problem. MCU would give support to every DAW like the KKMK1 has, including Pro Tools. It is a standard. The whole point of the product is in the name: complete control. Like the MK1 has. Customers should not need another keyboard, especially at this price point.

NI lied by omission over this. This is why people are upset.

 

Yeah. Somehow I can't get it to work. Cc transport. I'll try again today. I have a big ass console so I have deep integration with protools. I just need to start play and stop from maschine and kkmk2 for when I am programming drums etc...

 

Does the transport on the machine studio already send out the right cc message? So I just need to receive it in protools?

 

I'm citing it as a possibility for this person who just wants transport support, it works for me as a temporary workaround and should work for anyone who wants to use it for that basic function, I'm not suggesting it as a substitute for what should really be there and never have but there is no reason whatsoever why people should not do what they can to make stuff work for them just because it doesn't work perfectly, especially since a ProTools solution is possibly further off than some.

btw I was one of the first to raise this issue with NI so saying I 'misunderstood' this is ridiculous.

 

I don't know - I think Maschine Studio still supports MCU so if you have that use that then.

 

Pro Tools supports MCU. KKMK1 works just fine with Pro Tools via MCU. There's no shortage of people asking for MCU support to be returned to KKMK2. One stone, many birds.

 

Yeah for that simple thing I meant use the white buttons, not transport controls - but since you have Maschine anyway probably use that.

 

I know

 

I must be dense. I cannot get maschine to work transport in protools. Anyone in NYC? Willing to come to my studio and set it up? Lol.

 

It's probably a question of going into the NI controller editor to select MCU mode, then going into ProTools settings to tell it to use MCU protocol as control standard and make sure Maschine midi in is selected (I don't have either but that's roughly how it would work in most hosts). Obviously Maschine should be in midi mode (not running as a plugin)

 

Oh. I run as a plugin. Any way to control protools transport using maschine as a plugin?