USB Solo mk2 SysEx device ID

This page discusses the USB Solo’s SysEx device ID, in which circumstances you may wish to change it from its default value of 1, and the extra configuration steps that you may have to carry out if you do.

When should I change the SysEx device ID?

The device ID allows software that is communicating via SysEx messages (such as our Configuration Manager) to identify a particular USB Solo when there are multiple USB Solos connected. If you have only one USB Solo, you do not need to change the device ID. If you have multiple USB Solos, there are particular circumstances in which you should ensure that each device has a unique device ID.

The device ID is used in the USB device name. By default, the USB Solo’s USB device name is KentonUsbSoloMk2-01. Changing the device ID, and therefore the USB device name, on a USB Solo that has already been connected to your computer requires some additional configuration steps, which are detailed below.

I have a single USB Solo mk2

If you have a single USB Solo, there is no need to change the device ID. You do not need to read the rest of this page.

I have multiple USB Solo mk2s and they are connected via USB only

In most circumstances, you do not need to change the device ID, as there is only ever one USB Solo connected to a particular USB port. However, if you are using browser-based applications that communicate with it using MIDI SysEx messages (such as our Configuration Manager), the browser cannot see multiple identical USB MIDI devices, even though the Operating System can. In this instance, you should ensure that each USB Solo has a unique USB device name (see Changing the SysEx ID below).

I have multiple USB Solo mk2s and they are connected via DIN only

If you have multiple USB Solo mk2s connected to a single MIDI port on your computer, and you are using any software that communicates with them using MIDI SysEx messages (such as our Configuration Manager), you should ensure that each USB Solo has a unique device ID (see Changing the SysEx ID below).

I have multiple USB Solo mk2s and they are connected via both USB and DIN

If you are using browser-based applications that communicate with it using MIDI SysEx messages (such as our Configuration Manager), the browser cannot see multiple identical USB MIDI devices, even though the Operating System can. In this instance, you should ensure that each USB Solo has a unique USB device name (see Changing the SysEx ID below).

If you have multiple USB Solo mk2s connected to a single MIDI port on your computer, and you are using any software that communicates with them using MIDI SysEx messages (such as our Configuration Manager), you should ensure that each USB Solo has a unique device ID (see Changing the SysEx ID below).

Changing the SysEx device ID

The device ID is set by Parameter 91 on the USB Solo, and can be changed from the front panel or by using the Configuration Manager. If already connected via USB, the USB Solo should then be turned off and on again in order to update the USB device name as the computer only requests the device name when the device appears on the USB bus.

In an ideal world, you should change the device ID prior to connecting it to the computer that runs your DAW, either by using a USB power supply (or a powered USB hub that is disconnected from your computer) to power the USB Solo and changing the device ID from the front panel, or by using a different computer and setting the device ID using Configuration Manager.

To change the device ID using the front panel, press the DEC button until P91 appears on the display. Then press the SEL button to see its current value. Press INC and/or DEC to change the value, then press SEL to save the change.

This will ensure that when first connected to your main computer, the USB Solo is installed with a unique USB device name. See Using browser-based MIDI software on Windows below for further information.

If you have already connected the additional USB Solo to your main computer, then you will need to take additional steps in order to change the device ID:

I have already attached my additional USB Solo to my Windows PC

If you have already attached your USB Solo to your Windows PC, you will have 2 identical KentonUsbSoloMk2-01 USB devices, and browser-based applications will not be able to distinguish between them. To resolve this, you will need to uninstall the device then re-install it using its new USB device name as follows:

  • Change the device ID on the new USB Solo, then power it off.
  • Search for devmgmt.msc in the Start menu, right-click the result, and select Run as administrator.
  • Find the Kenton devices under Sound, video and game controllers, right-click on it and select Uninstall. Reboot when prompted.
  • Once you have rebooted, power on your USB Solo so that it registers with its new USB device name.

See Using browser-based MIDI software on Windows below for further information.

I have already attached my additional USB Solo to my Mac

If you have already attached your USB Solo to your Mac, you will have 2 identical KentonUsbSoloMk2-01 USB devices, and browser-based applications will not be able to distinguish between them. To resolve this, you will need to uninstall the device then re-install it using its new USB device name as follows:

  • Change the device ID on the new USB Solo, then power it off.
  • Open the Audio MIDI Setup app, and select Window -> Show MIDI Studio to see your MIDI devices.
  • The USB Solo you just powered off will be greyed-out – select it and then select MIDI Studio -> Remove Selected Device.
  • Power on your USB Solo, and it should be added with its new USB device name.

Using browser-based MIDI software on Windows

Windows has traditionally had some issues with using multiple identical MIDI devices on browser-based applications. If you have 2 USB Solos attached, even after setting unique device IDs on each, you may find that you don’t always see them in your application.

If you only have one powered on, then the application will see it, but if you have more than one connected, neither will be seen.

The work-around is to open your application with one USB Solo powered on – it should be seen by the application . Then turn on the next USB solo and refresh the application: the additional USB Solo should then be seen.

This limitation appears to be fixed by Windows MIDI Services (which replaces the older WinMM/MME API). Windows MIDI Services is being rolled out to Windows 11 PCs from February 2026.