I have an Arturia keyboard which appear in C15 but the Nektar 49X is not recognized. I searched the web to find a solution but it remains a mistery, so if somebody has an answer he will be most welcomed !!! 
do you perhaps mean the Nektar Impact LX49+, or is there another one besides the older GX49 or SE49 which also use the number (of keys) “49” in its model name?
I’ve been using my Nektar Impact LX49+ since 2020, without any problems also in Cubase Pro 15 (and on Windows 11).
Meanwhile, even Nektar’s 3rd generation of that controller series is available.
Also, for the LX49+ there is a Cubase related software utility available.
Best,
Markus
Cubase doesn’t on its own ‘recognize’ MIDI Ports, it just sees whatever MIDI Ports the OS tells it are there. If you are on Windows do you see the Nektar listed in Device Manager (or on Mac somewhere else that others will need to specify).
Not much info to go by here
- What do you mean by “not recognized”? Is it not showing up in Studio Setup? Is it that there’s a script that isn’t working? Is it that DAW control isn’t working? Something else?
- As others have asked, what is the actual keyboard? Is it the Impact LX49? (Important because if it’s an older panorama one, both macOS and Windows need a firmware update on the device, and if on Windows, you need to stop using their driver afterwards because it fails our signing check)
- What OS are you using?
Pete
Microsoft
-
it does not appear on the studio setup like the arturia do
-
yes the impact lx49+
-
Windows 11
I’ve got one of these, can’t get it to work either.
I did find a midi remote script for it but it doesn’t seem to connect.
@Frederic_Passerin @Riojabilly
Are you using their drivers or the built-in Windows drivers?
Actually, easiest thing for you to do here:
- Open Device Manager (right-click the Windows logo on the taskbar, and choose device Manager)
- Scroll down to “Sound, video and game controllers” or equivalent in your language.
- Paste here a screenshot of that entire section.
- If the Nektar device is visible there, please right-click it and choose “Properties”.
- Paste in the full screenshot of the FIRST tab of that properties dialog.
(Windows+Shift+S is shortcut for taking screenshots)
Examples:
Pete
Microsoft
Next, please paste a screenshot of the entire window for the MIDI page for your Studio setup in Cubase.
Thanks
Pete
Microsoft
Thanks a lot ! I’ll try your way
But i’m not sure there are impact drivers, that’s the first thing i looked on the web. It’s definitely W11 drivers.
Question. Will all MIDI 2.0 devices be listed as being such in Windows or is just on the Device Manager?
Those names come from the devices themselves. In this case, the Iridium lists itself as “Iridium (MIDI 2.0)” when in MIDI 2.0 mode.
Enumerated Legacy API MIDI 1.0 ports show up under Software devices where there will be one entry per port.
Enumerated New API Endpoints show up under MIDI Endpoints, where there is one entry per stream (a stream can include many logical ports/groups).
Pete
Microsoft
Thanks. Can you post the requested screenshots?
Pete
Microsoft
Today i work, tuesday i will
Hi again @Frederic_Passerin,
thanks for your additional info.
So, if it actually is the Impact LX49+, then there definitely are Impact LX drivers:
You just need to create an account and have your device registered with the manufacturer’s website in order to receive the download link. Here are Nektar’s support links:
https://support.nektartech.com/impact-support/
https://support.nektartech.com/cubase-nuendo-setup-and-troubleshooting-impact/
This is what those drivers look like in Windows’ device manager (greyed out if unconnected):
In Windows device manager, you can make previously connected (yet currently unconnected) device drivers visible by clicking the following menu entry (on this machine I’m using Windows in German, but I’m sure you’ll figure it out in English):
Best,
Markus
That Steinberg download is for scripts, not actual Windows Kernel Drivers, correct?
Pete
Microsoft
Hey @Psychlist1972,
yes, you’re probably right.
Doesn’t the Nektar range connect via class compliant MIDI drivers anyway?
Anyway, it’s possible to simply unzip the above mentioned installer package:
The main folder contains a few subfolders that contain scripts and / or script references, various *.XML files, and also there are two folders which have a devices related *.dll file (as x86 and x64), most probably these are the ones customized for Steinberg:
The remaining two folders contain VC++ Redist packages, Registry related files, and installer related resources.
Cheers,
Markus
That’s what I will verify when the screenshots come in 
Pete
Microsoft
Hello all,
Nektar LX+ is class compliant it doesn’t require drivers. MIDI input (keys and pitch/mod wheels) should be working on instrument tracks in Cubase regardless of the integration installer. If not the customer, has a more general issue.
For the integration for LX+ we used the older integration method that pre-dates the MIDI Remote API. Impact LX+ was released 12 years ago and has worked with Cubase since the beginning.
The customer should go to www.nektartech.com, register the controller and there they will obtain the integration installer complete with setup instructions.
FYI, the newer LXmk3 models use the MIDI remote API. We will not be updating the LX+ to use the Remote API.
Regards,
Tim
Thanks Tim.
Please also keep in mind we have two MIDI class drivers in Windows, and it’s possible one works with the LX+ and the other does not. Once I see the screenshots I’ll be able to tell which class driver it was assigned to.
OP mentioned the LX doesn’t show up in Cubase in Studio Setup at all.
Pete
Microsoft
I’ve been using a Nektar Impact LX88+ with Nektar’s Cubase DAW integration and have never had a problem. But you do have to register the device on Nektar’s site.