Native Instruments Support › General and Guidelines

NKS Connect Troubleshooting Guide

This article helps you troubleshoot common setup and connection issues when using NKS Connect with AKAI MPK mini IV or MPK mini plus II.



NKS Connect does not appear in Native Access

Problem:

NKS Connect is not shown or available in Native Access after connecting the controller.

Expected behavior:

When a supported controller is connected, Native Access should detect the device and guide you through the required software setup.

Try this:

  1. Make sure the controller is connected via USB.
  1. Confirm that the LEDs on the controller are on.
  1. Open Native Access and sign in with your Native ID.
  1. Update Native Access to the latest version.
  1. Disconnect and reconnect the controller while Native Access is running.
  1. Restart your computer and open Native Access again.
  1. Try another USB port or USB cable if the controller is still not detected.
  1. If Native Access still does not offer NKS Connect, search for NKS Connect and Hardware Connection Service in the Library and install them manually. See “Installing NKS Connect” in NKS Connect - How to set up and use.


NKS Connect does not open in the menu bar or system tray

Problem:

The NKS Connect menu bar / system tray icon does not appear after connecting the controller.

Expected behavior:

NKS Connect runs in the background. When the controller is connected, the NKS Connect icon should appear in the menu bar on macOS or the system tray on Windows.

Try this:

  1. Make sure the controller is connected and powered via USB.
  1. Check that NKS Connect has not been closed manually:
  • macOS: check Activity Monitor.
  • Windows: check Task Manager.
  1. Check that Hardware Connection Service is also running. If it is not, see “Hardware Connection Service is not running” below.
  1. Restart your computer.
  1. Open NKS Connect manually from Native Access:
  • Open Native Access.
  • Search for NKS Connect.
  • Click Open

.

Hardware Connection Service is not running

Problem:

The controller does not appear in NKS Connect, or NKS Mode does not work, because Hardware Connection Service is not running.

Expected behavior:

Hardware Connection Service runs in the background and lets supported controllers communicate with Native Instruments software. It must be running for NKS Connect to work.

Try this:

  1. Open Activity Monitor on macOS or Task Manager on Windows.
  1. Look for NIHardwareConnectionService in the list of running processes. This is the process name for Hardware Connection Service.
  1. If it is not running, open it manually:
  • Open Native Access.
  • Search for Hardware Connection Service.
  • Click the three dots (...) next to the application.
  • Select Installation Paths.
  • Click the folder icon to open the installation folder.
  • Double-click NIHardwareConnectionService (the app on macOS, the .exe file on Windows).
  1. Check that the controller appears in the NKS Connect menu bar / system tray application and is blue.


NKS Connect system tray app does not reopen after inactivity

Problem:

The NKS Connect app may not reopen after a period of inactivity or after reconnecting the controller.

Expected behavior:

The NKS Connect app is designed to appear automatically when the controller is connected and disappear when the controller is disconnected.

Workaround:

Open NKS Connect manually from Native Access:

  1. Open Native Access.
  1. Search for NKS Connect.
  1. Click Open.


The controller is shown as inactive in NKS Connect

Problem:

The controller appears in the NKS Connect menu bar / system tray application, but it is not active.

Expected behavior:

When the controller is active, it should appear blue in NKS Connect. A blue keyboard icon appears next to the controller.

  • Blue: controller is active and connected to NKS Connect.
  • Grey: controller is detected but inactive.

Try this:

  1. Open the NKS Connect menu bar / system tray application.
  1. Click controller to activate it.
  1. Confirm that the controller appears blue with a blue keyboard icon next to it.
  1. If it remains grey, disconnect and reconnect the controller.
  1. Check that Hardware Connection Service is running. See “Hardware Connection Service is not running” above.
  1. Restart your computer if the controller still does not activate.


NKS Mode does not work

Problem:

The controller does not enter NKS Mode, or NKS Mode does not control the loaded instrument.

Expected behavior:

When an NKS-compatible plug-in is loaded on the selected track, pressing Plugin / DAW on the controller should switch between DAW mode and NKS Mode.

Try this:

  1. Make sure NKS Connect and Hardware Connection Service are running.
  1. Confirm that the controller is active in NKS Connect.
  1. Make sure the latest controller firmware is installed using inMusic Software Center.
  1. On macOS, reset the controller MIDI device after updating the firmware. See “macOS: NKS Mode does not work after firmware update” below.
  1. Install the available controller DAW scripts using inMusic Software Center.
  1. Restart your DAW after installing DAW scripts.
  1. Load an NKS-compatible plug-in on the selected track:
  • Kontakt
  • Komplete Kontrol
  • Maschine
  1. Select the track containing the NKS-compatible plug-in.
  1. Press Plugin / DAW on the controller to switch to NKS Mode.
  1. If you use Logic Pro, see “Logic Pro: NKS Mode or DAW mode does not work as expected” below.

For NI instruments that do not run inside Kontakt, such as Massive, Massive X, Monark, or Conflux, load the instrument in Komplete Kontrol to use NKS Mode.


DAW mode does not work

Problem:

The controller does not control your DAW after installing NKS Connect.

Expected behavior:

NKS Connect works alongside the controller’s standard DAW integration. DAW mode requires the correct controller DAW scripts from inMusic Software Center.

Try this:

  1. Open inMusic Software Center.
  1. Select the controller.
  1. Install the available DAW scripts for your DAW.
  1. Restart your DAW.
  1. Press Plugin / DAW on the controller to switch between DAW mode and NKS Mode.


NKS Mode or DAW mode does not work after setup

Problem:

NKS Connect is installed and running, but either NKS Mode or DAW mode does not work correctly.

Try this:

  1. Confirm that NKS Connect and Hardware Connection Service are installed and running.
  1. Confirm that NKS Connect is running in the menu bar / system tray.
  1. Confirm that the controller is active in NKS Connect.
  1. Install the latest controller firmware using inMusic Software Center.
  1. Install the available controller DAW scripts using inMusic Software Center.
  1. Restart your DAW.
  1. Restart your computer.
  1. On macOS, reset the controller MIDI device after updating the firmware.
  1. On Windows, make sure your system and required drivers are up to date.
  1. If you use Logic Pro, see “Logic Pro: NKS Mode or DAW mode does not work as expected” below.


macOS: NKS Mode does not work after firmware update

Problem:

NKS Mode does not work on macOS after updating the controller firmware.

Cause:

After a firmware update, macOS may continue using the old controller MIDI device profile. This can prevent NKS Connect from using the updated MIDI ports correctly.

Try this:

  1. Disconnect the controller.
  1. Open Audio MIDI Setup.
  1. Select Window > Show MIDI Studio, or press Cmd + 2.
  1. Delete the existing controller device.
  1. Reconnect the controller.
  1. Restart your DAW.

macOS will create a new device entry with the updated MIDI configuration.


Ableton Live: NKS Connect does not work as expected

Problem:

NKS Mode or DAW mode does not work as expected in Ableton Live.

Try this:

  1. Update Ableton Live to version 12.4.1 or later.
  1. Install the controller DAW scripts using inMusic Software Center.
  1. Restart Ableton Live.
  1. Connect the controller.
  1. Open a project with Kontakt, Komplete Kontrol, or Maschine.
  1. Select the track containing the NKS-compatible plug-in.
  1. Press Plugin / DAW on the controller to switch between DAW mode and NKS Mode.

Known limitation:

Maschine Pad Mode is currently affected when using Maschine as a plug-in in Ableton Live. To use Maschine Pad Mode, use Maschine in standalone mode.


Logic Pro: NKS Mode or DAW mode does not work as expected

Problem:

NKS Mode or DAW mode does not work as expected in Logic Pro.

Expected behavior:

NKS Connect works in Logic Pro after the required software, controller firmware, and DAW scripts are installed. Logic Pro creates the controller’s control surface when you restart Logic Pro or reconnect the controller.

Try this:

  1. Install the Logic Pro scripts for your controller using inMusic Software Center. Restart Logic Pro.
  1. Rebuild the control surface defaults. See “Logic Pro: rebuild control surface defaults” below.
  1. Go to Logic Pro > Control Surfaces > Setup.
  1. Make sure NKS Connect is listed, with Output Port and Input Port set to NKS Connect. If it is not listed, click New > Install, search for NKS Connect, select it, and click Add.
  1. Make sure your controller is also listed, with Output Port and Input Port set to its MIDI Port (for example, MPK mini IV MIDI Port or MPK mini plus II MIDI Port). If its control surface looks wrong, remove it from the list, then restart Logic Pro or reconnect the controller. Logic Pro creates it again, and removing it does not change the rest of your setup.

Logic Pro control surface setup with NKS Connect and the MPK mini IV.Logic Pro Control Surface Setup window showing the NKS Connect device and an MPK mini IV device, with Output Port and Input Port set to MPK mini IV MIDI Port.

Image file: logic-control-surface-setup-device.png · Alt text: Logic Pro Control Surface Setup window showing the NKS Connect device and an MPK mini IV device, with Output Port and Input Port set to MPK mini IV MIDI Port.

Logic Pro control surface setup with NKS Connect and the MPK mini IV.

  1. Go to Logic Pro > Settings > MIDI > Inputs.
  1. Make sure the controller ports and NKS Connect are enabled. Only disable the Plugin Port if you use Maschine Pad Mode. See “Logic Pro: Maschine Pad Mode does not work” below.

Logic Pro MIDI inputs with the controller ports and NKS Connect enabled.Logic Pro Settings, MIDI tab, Inputs view, listing the MPK mini IV ports and NKS Connect.

Image file: logic-midi-inputs.png · Alt text: Logic Pro Settings, MIDI tab, Inputs view, listing the MPK mini IV ports and NKS Connect.

Logic Pro MIDI inputs with the controller ports and NKS Connect enabled.

  1. If the problem continues, reset the control surface preferences file. See “Logic Pro: reset the control surface preferences file” below.


Logic Pro: Maschine Pad Mode does not work

Problem:

Maschine Pad Mode does not work as expected when using Maschine in Logic Pro.

Expected behavior:

Logic Pro requires additional setup for Maschine Pad Mode.

Try this:

  1. Open Logic Pro.
  1. Go to Logic Pro > Control Surfaces > Setup.
  1. Remove any existing controller control surface if it was created before installing NKS Connect.
  1. Restart Logic Pro.
  1. Go to Logic Pro > Control Surfaces > Setup.
  1. Click New > Install.
  1. Search for NKS Connect.
  1. Select NKS Connect and click Add.
  1. In the Device settings, set Output Port to NKS Connect.
  1. Set Input Port to NKS Connect.
  1. Go to Logic Pro > Settings > MIDI > Inputs.
  1. Disable MPK mini IV Plugin Port or MPK mini plus II Plugin Port.

This setup allows Maschine Pad Mode to work correctly in Logic Pro.

Logic Pro creates the controller’s control surface again when you restart Logic Pro or reconnect the controller. Removing it does not change the rest of your setup.


Logic Pro: rebuild control surface defaults

Problem:

Logic Pro does not recognize the controller or NKS Connect after setup, or the control surface setup looks incorrect.

Expected behavior:

Rebuild Defaults resets the control surface setup in Logic Pro so it detects your controller again.

Try this:

  1. Disconnect the controller from your computer.
  1. Open Logic Pro.
  1. Go to Logic Pro > Control Surfaces > Rebuild Defaults.

Logic Pro Control Surfaces menu with Rebuild Defaults selected.Logic Pro menu with the Control Surfaces submenu open and Rebuild Defaults highlighted.

Image file: logic-rebuild-defaults.png · Alt text: Logic Pro menu with the Control Surfaces submenu open and Rebuild Defaults highlighted.

Logic Pro Control Surfaces menu with Rebuild Defaults selected.

Then reconnect the controller. If NKS Connect is no longer listed, add it again. See “Logic Pro: NKS Mode or DAW mode does not work as expected” above.


Logic Pro: reset the control surface preferences file

Problem:

NKS Connect or the controller still does not work in Logic Pro after rebuilding the control surface defaults.

Expected behavior:

Logic Pro stores its control surface setup in a preferences file. Removing this file resets the control surface setup. Logic Pro creates a new file the next time it opens.

Note: This resets your control surface setup in Logic Pro. You will need to add NKS Connect again afterward.

Try this:

  1. Close Logic Pro.
  1. In Finder, select Go > Go to Folder.
  1. Enter ~/Library/Preferences and press Return.
  1. Find com.apple.logic.pro.cs and move it to the Trash.
  1. Open Logic Pro.
  1. Set up NKS Connect again. See “Apple Logic Pro” in NKS Connect - How to set up and use.

Advanced: use Terminal

If you prefer, you can remove the file in Terminal. This deletes the file immediately.

  1. Close Logic Pro.
  1. Open Terminal.
  1. Run the following command, replacing <USERNAME> with your macOS username. To find your username, run whoami.

rm /Users/<USERNAME>/Library/Preferences/com.apple.logic.pro.cs


Cubase: NKS Connect does not work as expected

Problem:

NKS Mode or DAW mode does not work as expected in Cubase.

Try this:

  1. Update Cubase to the latest available version.
  1. Install the controller DAW scripts using inMusic Software Center.
  1. Restart Cubase.
  1. Connect the controller.
  1. Open a project with Kontakt, Komplete Kontrol, or Maschine.
  1. Select the track containing the NKS-compatible plug-in.
  1. Press Plugin / DAW on the controller to switch between DAW mode and NKS Mode


Maschine Pad Mode does not work in a DAW

Problem:

Maschine Pad Mode does not work as expected when Maschine is loaded as a plug-in inside a DAW.

Expected behavior:

Maschine Pad Mode works as expected in Maschine standalone mode. When using Maschine as a plug-in inside a DAW, additional DAW setup may be required.

Try this:

  • For Ableton Live: use Maschine in standalone mode for Maschine Pad Mode.
  • For Logic Pro: follow the Logic Pro setup steps above.
  • For Cubase: update to the latest version and make sure the required DAW scripts are installed.

Parameters do not show or control correctly

Problem:

The knobs do not control the expected parameters, or parameter names and values do not appear on the controller display.

Try this:

  1. Confirm that the controller is in NKS Mode.
  1. Confirm that an NKS-compatible plug-in is loaded on the selected track.
  1. Confirm that the controller is active in NKS Connect.
  1. Load a Kontakt, Komplete Kontrol, or Maschine instrument.
  1. Try another NKS preset or instrument.
  1. Restart the DAW.
  1. Restart NKS Connect from Native Access.


Preset browsing does not work

Problem:

Preset browsing from the controller does not work, or the expected preset list is not shown.

Expected behavior:

In NKS Mode, the controller follows the filtered preset list shown in Kontakt, Komplete Kontrol, or Maschine.

Try this:

  1. Confirm that the controller is in NKS Mode.
  1. Confirm that Kontakt, Komplete Kontrol, or Maschine is focused.
  1. Select the track containing the NKS-compatible plug-in.
  1. Check whether filters are applied in the software browser.
  1. Clear or adjust filters if the expected presets are not shown.
  1. Use the encoder to browse presets.
  1. Hold Shift while turning the encoder to move through the list faster.


If the issue continues

If the issue continues, please contact Support and include the following information:

  • Operating system and version
  • DAW and version
  • Native Access version
  • NKS Connect version
  • Hardware Connection Service version
  • Controller model (MPK mini IV or MPK mini plus II) and firmware version
  • NI software used: Kontakt, Komplete Kontrol, or Maschine
  • Whether you used standalone mode or plug-in mode
  • Whether NKS Connect and Hardware Connection Service were running
  • Logic Pro only: whether you rebuilt the control surface defaults or reset the control surface preferences file
  • Steps to reproduce the issue
  • What you expected to happen
  • What actually happened
  • Screenshots or videos, if helpful

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article