Good evening. I need a simple answer on how to fix this issue: When using C15 on a Window 11 Pro system (Intel Ultra 9 Chip, 32g Ram) and using a Nektar Impact LX88+ MIDI Keyboard Controller, Cubase instruments will hang up when playing. I have to close Cubase completely (and in some cases restart the computer) to resolve the problem. I cannot find a pattern which is causing this behavior. I have another Win 11 Pro (Surface 7) in which this problem does not occur. The only difference I can see between the two is that the O/S on the newer computer started with MIDI 2.0 while the older computer has legacy MIDI 1.0 on the machine. The drivers are the most recent from Nektar. I have yet to be able to use the new computer in a performance setting with this issue. I have limited experience with MIDI at this stage of the game. Thank you in advance.
Can you be a bit more specific about what you mean by “hang up” please?
Is it just that VST instruments stop producing sound, or does the entire computer freeze?
Regarding MIDI 2.0, have a look at the post below and then click the link to the Discord server where you can discuss this directly with Microsoft personnel and other Windows MIDI users.
In particular, see the part about third-party drivers – many of which are no longer needed on Windows 11.
Thank you for your response. Only the application (C15) will freeze/hang up. The computer does not freeze. I often import audio tracks to practice with the various VST instruments I use for performance. When practicing, a VST instrument will not release (?) on a note while the audio track will continue. In some instances, I can unplug the USB connection, reinsert the connection and, after a couple of seconds, continue with the session. In other cases, I have to exit Cubase and restart the application. In my previous professional career, I was heavily involved in testing software, so isolating issues was the standard practice. However, with this problem, I cannot locate a specific pattern or event which causes the issue.
We haven’t had any issues with Nektar, other than their P-series drivers being completely blocked due to signing issues (they’ve since released a firmware update and asked customers to discontinue using those drivers, putting it on par with macOS).
However, it is correct that third-party MIDI drivers are usually not required anymore, and we’ve love folks to move away from them.
Just to be clear, MIDI 2.0 is unrelated. I know folks use that as short-hand for Windows MIDI Services (which includes a complete rewrite of MIDI 1.0, plus MIDI 2.0 support).
Hangs like this have only happened with inMusic drivers (AKAI, Rane, m-audio, etc.), but if you are up to date on updates, you shouldn’t be seeing that unless you pull the plug on an inMusic device while in use.
If you join the Discord server Windows MIDI / Audio and read the full pinned post in #start-here I’ll work with you to figure out what’s going on.
Pete
Microsoft
Thank you Pete. I appreciate the information. I will start clawing my way through this. I look forward to learning more so I can become more competent. I will keep you posted on how it is going.
Hey all,
Just to say the Nektar Impact LX88+ is class compliant, there is no MIDI driver. There is a control surface bundle written with the older integration (legacy) SDK. You will see the Impact LX88+ listed in Studio | Studio Setup under 'Remote Devices (legacy).
Yo can try disabling that entry to ensure there is no interference coming from the legacy SDK.
The newer Impact LX88mk3 uses the remote API for integration rather than the legacy SDK method.