Maschine Mk3 not working properly

Hi,
I just set up a new PC (Win 10). I installed the Maschine software via Native Access. I can start the Maschine software, the hardware is detected BUT I cannot play the pads, cannot start/stop etc. I actually cannot do anything on the hardware, while the software is running fine. I can load e.g. drums sets and also play from the software.
The LEDs on Maschine are all "okay", the Maschine display shows everything, but basically I cannot do anything on the hardware.
All hardware worked on my old computer, but not on the new one.

What I tried so far: re-installing the Maschine software, "reset" of the Maschine (removing the registry entry as adviced in the NI help section), rebooting, unplugigng the USB cable, different USB hubs (Elektron Overhub and a Plugable USB hub).
I am attaching 2 screen shots: 1 after starting the software and the 2nd one with a loaded group/drum set. (second image: shows that I was just setting midi channels on the software)
Any help is very welcome.

 

and if you play a sequence the pads light up?

Uwe

 

Hi Uwe

Yes, "light show" is on when playing sequences. It looks like the way into the Maschine works, all lights up, values are displayed, just the way into the computer does not work (at all).

best
oliver

 

in addition, I am not sure, if that's related, that's why I am mentioning it hear: I also have a Midi configuration problem with Maschine on the new computer: I run a RTP Midi setup (iconnectivity mioXM and -L). All works fine, but when I set a midi in and out in Maschine (software) the previous sound on that track still plays with the midi channel. Wasn't the behaviour before that the previous instrument is not played anymore when I set Midi in and out to an outbound midi-expander, or do I remember this wrongly? (while writing this I am actually thinking that this in fact the expected behavior...)

P.S. please ignore this - I definitively think this is working as expected, I think it was just me being confused now doing the setting on the software and not on the hardware any more

 

Update: it must be a Maschine hardware problem. I was able to test from a laptop (all different: MacOS, USB on the Mac, obviously a different software installation, using only the audio from the laptop, no midi).
Any idea? Can I somehow factory-reset the hardware?

 

Sounds like what I've been experiencing for a while: https://www.native-instruments.com/...ttons-and-encoders-on-boot-up-windows.409615/
Only workaround/fix I've found so far is turning the hardware off and on again.

 

It's resolved! Unfortunately I don't really know why. Thanks for the other link, Mr36 I think I read it but did not relate it 100% to my problem. Nevertheless... It's resolved.

Amongst other things, I played around with the controller editor app and switched off Maschine with the power button (opposing to just unplugging the USB and power chord). At one stage the Maschine did not start for a while, I assume that then the firmware was restored somehow, which may have done the trick. I was thinking that it would be a good idea to have the option to overwrite the firmware actively as a user and not just have the option for "self healing" (although I understand that NI prevents users from messing around...)

 

I agree and think the firmware updater should have the option to reflash the firmware, just for troubleshooting issues like these.

That's great. For you! The expected behaviour did return to mine a few times, but I could never nail down why it did or why it would soon after return to failing. Very annoying.

 

too bad, in reality it is not fixed anymore. I now "manage" to trigger the incident but just playing around So, I removed the "solved" flag form the thread again. Now, that's the good in the bad news, I can quickly fix it by turning the device off and on again. Still very annoying... In particular as I am only working in the NI universe (okay, once I dared to load a Diva VST instance).
This smells like a USB issue? (speculating as it worked well on my old PC, although I had not used Maschine intensively there yet)
Is it worth to open a bug report? What information would be required?

Thanks and best
oliver

 

I would recommend maybe not hot-unplugging the MK3.

The only reason I say that, despite it being a USB device, is that the windows driver for the MK3 does not trigger windows insert/disconnect-state notifications. The driver seems to be in an always "connected" state, regardless if the device is powered on/off or even plugged in. Perhaps a more experienced user or NI engineer can check me here -- does the USB driver for windows for the MK3 remain in an "always connected" state? If so, and windows was therefore trying to send/receive data to the MK3 as it was physically disconnected, can a firmware or a windows USB driver/plug state issue arise? Thinking outside the box here.

 

Humm... But using the back on/off button is the same thing as hot-unplugging, no? AFAIK any USB device other than something that writes data (drive/HD/SSD or thumb drive) is designed to handle that; in this case power cycling it's actually the only solution.

 

Good point. If the driver is in "always connected" mode, then indeed power off/on would pretty much act the same, as far as the device and windows is concerned. Then again maybe the on/off button transmits something to the driver? Not sure, but thought I would make a suggestion based on the different behavior I noticed from the MK3 driver, as opposed to other devices. I dont know if the MK3 is reading/writing data to any volatile or nonvolatile internal memory.

 

do you use a laptop? maybe try to set power mode to full\energy save mode off

 

Hi Uwe303 : No, I am on a desktop computer

 

what processor (cpu) is in your Desktop?

 

Ryzen 7 3700X

 

Ok, there have been others who have been having issues with Ryzen based computers and certain NI hardware. Was following another thread where Adil@ni stated it is an issue and is being investigated. A workaround for the user with a similar issue (different controller) was to get an unpowered USB hub. Here is a link to the thread, maybe this workaround will work for you as well...
https://www.native-instruments.com/...nised-on-windows-10-3rd-gen-amd-ryzen.413757/

worth a shot!

 

strange i have "only" a ryzen 5 2600 x on a msi x470 gaming pro carbon board and everything works perfectly, i guess if than it´s more a chipset\chipset driver issue and not a cpu issue

Uwe