![]() ![]() So with that in mind, I think everybody deserves the best Mikro mk3 unit and if you can easily return it or are willing to wait you have my blessing! That is probably the only way to get a ‘10/10’ maschine mikro unit and honestly it’s what I would personally do (but I have other units to play with in the meantime). This is just to illustrate how NI can get away with not changing anything about how they make their hardware or quality control or factory calibration while at the same time making it seem as if they “fixed” the problem (which if you look at it a certain way is actually what they did… I mean, if that happens they did fix it, just not in the way we sensitivity hungry people would like). They will just make the Mikro’s ever so slightly less sensitive and nobody will notice/care and the difference is that not just a few unlucky folks are dealing with less sensitivity, but everybody who upgrades their firmware / controller editor will be dealing with it, including me with my ‘impeccable’ maschine mikro devices So… My suspicion is that if there’s gonna be a firmware update, or controller editor update after which the problems are gone, that could very well be what happened. It will look the same, everybody will set it to most sensitive and will feel like that’s good and they’ll be happy (just like I was with the setting in the screenshot) and NI doesn’t have to deal with units being returned. ![]() So just to clarify: If we consider the current slider to go from 0 to 100, they will just make the slider go from 0 to 90. If NI keeps getting reports of this, and they want to deal with this quickly and cost-effectively, they will probably release a firmware update and/or a controller editor update that effectively does the exact same thing as us scaling back the sensitivity setting. Now, there are a bunch of Mikro devices triggering too much on the most sensitive setting. Their engineers probably decided upon this “sensitivity threshold” in controller editor as the best they could do. ![]() NI tweaks their firmware to make their devices function on the edge of being as sensitive as possible while at the same time not ghost triggering or permanently triggering too much. ![]() However, you can also look at it this way: I understand that point of view and in a way I agree. I do understand that as a matter of principle this should not happen, NI “should not get away with this” so to speak. If you use this sensitivity and you start playing and it feels good, this might be the best option in some cases. So anything between that and most sensitive might be an acceptable workaround for those who just wanna start playing and stop dealing with NI customer support. (The $350 Nekar Aura seems to maybe be a little better but its more than $100 extra) I tested it out a little and here’s a screenshot of the sensitivity setting that to me still feels comfortable to play. In my experience however, the maschine mikro mk3 set to a little less sensitive is still the best 4x4 controller out there for the money by far. Obviously, increasing the threshold for triggering is not a real solution to the problem, but rather a workaround of an inconsistency in the pads. The other pads on the device are not that sensitive so they will function normally on the most sensitive setting. In my experience, what this means, is that the pad that get’s stuck is so ‘sensitive’ that it will permanently stay triggered on the most sensitive setting. So, I’ve been searching the interwebs for other people having problems like these and I noticed another thread somewehere where someone with a Maschine studio and a pad that got stuck and the solution was, just like mentioned here, to set the sensitivity slider to less sensitive. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |