Nektar IMPACT LX88+ midi controller not working properly with Cubase 15 Pro

Hello Steinberg Forums,

After updating from Cubase 14 Pro to Cubase 15 Pro my Nektar IMPACT LX88+ midi controller isn’t working properly. Although Cubase recognizes and records the keyboard itself, none of the transport/function buttons or sliders work. This wasn’t an issue with Cubase 14 Pro.

Thanks

5 Likes

same here

Same problem.

Same problem with Impact LX49+

Hello,

We (Nektar) are aware of a problem with older Nektar device scripts (those not using the MIDI remote mapping method) in v15.0.5. We are currently looking into this issue and I will update this thread as soon as possible.

Nektar CS12 and Nektar Impact LXmk3 all appear to be working fine. Should you experience any issues with CS12 or LXmk3 please contact support. For other products, please await my response with more info.

4 Likes

LX61 user here. Will wait for a fix before upgrading to Cubase 15.

1 Like

Impact LX88+ user here, following……..

1 Like

Thank you for the report. Is it Mac, Windows or both?

We’ll try to reproduce the problem to then find a solution. (Internal reference: CAN-63277)

Thanks!

2 Likes

It’s Mac for me.

1 Like

LX88+ user here. Was just about to upgrade. Now, I’ll wait. Windows 11 Pro, Cubase 14, all up to date.

Hey Janne,

Thanks for assisting, I’ll send you what we’ve discovered privately.

2 Likes

Same Problem with Aruba (Windows 11)

I will say, I have exact same keyboard as OP, and mine works perfectly, as soon as I started up Cubase 15 on Windows 11. Hopefully that helps with the troubleshooting process. I don’t use MIDI Remote, just the custom integration that was provided by Nektar.

I also utilize the custom integration files provided by Nektar, and on my Windows 11 system the IMPACT88+ works only 10% of the time. Sometimes the transport buttons work, but most of the time none of them do.

Hi @Mark_McGee are you talking about Cubase 15 or 14 or both?

My initial post stated that my Nektar IMPACT88+ worked flawlessly with Cubase 14 Pro but upon upgrading to Cubase 15 Pro only the keyboard itself seems to work.
I’ve emailed Nektar support regarding this and they said they’re investigating. My thoughts are that the Nektar support files require some kind of rewrite.

Yes, the initial post is understood and it’s correct, that Tim and I are collaborating, to sort this out. I’m optimistic that we can solve it.

But I didn’t get the essence of your last post:

After reading it again, I think you’re saying that in Cubase 15 the Transport-Buttons work in about 10% of the time, right?

When I first open a project (or a new project for that matter), none of the buttons/sliders work. I see the midi input being recognized by Cubase (via the Midi In Activity window), but no resultant action. Sometimes, however, all of the transport buttons begin to work after I’ve had the project open for several minutes, and sometimes only the forward/backward buttons work.

1 Like

We can reproduce the issue and we have a fix which now is under test.

5 Likes

Very happy about this! Thanks.