Nektar LX 61 User Remote Script isn't recognized

toonableton · Post by **toonableton** » Fri Sep 02, 2016 3:31 pm

Hey,

I bought an Nektar Impact 61 and want to use it in Ableton Live 9.2.2.
The problem is that the User Remote Script, you can download from the Nektar website, isn't recognized when placed in the right folder.
Any solutions?

This is the link to the page of Nektar which contains the User Remote Script and an explanation.
http://www.nektartech.com/s.nl/ctype.KB ... /KB.746/.f

Regards
Toon Bosch

koranek · Post by **koranek** » Sat Sep 03, 2016 5:17 pm

You could try adding it to the app resources. I only know how to do that on a Mac. If you right click on the Live app and select "Show package contents," there is a folder for midi scripts:
Contents > App-Resources > Midi Remote Scripts.

Adding it there might work.

S4racen · Post by **S4racen** » Sat Sep 03, 2016 7:03 pm

Live 9 changed some stuff, and then again in 9.2 and 9.6....

It's fair to say the Nektar is no longer supported and you should contact them...

Cheers
D

oogah · Post by **oogah** » Sat Jan 21, 2017 5:16 am

Hi guys - I am having the same issue and cant see LX in the control surface drop downs after correctly installing the script. Was there an outcome after you contacted Nektar?

mlake89 · Post by **mlake89** » Fri Nov 10, 2017 4:57 am

I'm having the same issue. Plugged my impact lx49 in for the first time in a while, and midi does not play anything when i hit the keys. I tried re-installing the user remote script, but had no luck .

Has anyone heard back from Nektar?

Sonisphere · Post by **Sonisphere** » Sun Dec 03, 2017 3:31 pm

I have the same issue. Can't see the Impact LX in the control surface at midi preferences. Lucky I haven't buy nektar lx49+ yet.
I was just checking it at the store I work. I wrote to nektar's support. I'm going to share it here if I find the solution.

Frawnz · Post by **Frawnz** » Sun Dec 03, 2017 7:30 pm

Same problem, LX88+. I notice Nektar withdrew it's detailed Ableton setup page, so at least they're not just asleep like so many manufacturers. Working with Reaper and Bitwig until further notice. To its credit, Ableton generally has fairly painless and usually transparent keyboard recognition. Except where I really need it. Love that LX feel, good compromise between synth and escapement! I think you can still get the LX keys working as generic midi, but forget the buttons.

Sonisphere · Post by **Sonisphere** » Sun Dec 03, 2017 8:26 pm

I just saw the issue. It's funny how missed it.

http://www.nektartech.com/s.nl/ctype.KB ... /KB.746/.f

Here it says copy the folder. Not just the script file inside of it.

Well the midi keyboard is not with me but I can see Impact LX in the control surface section at the preference window. I will try it whenever I get to the store and let you all know if it works or not.

Frawnz · Post by **Frawnz** » Mon Dec 04, 2017 1:54 am

Thanks for the heads-up! It's Monday morning in Norway, somebody must have worked this weekend.

Sonisphere · Post by **Sonisphere** » Tue Dec 05, 2017 9:59 pm

Sonisphere wrote:I just saw the issue. It's funny how missed it.

http://www.nektartech.com/s.nl/ctype.KB ... /KB.746/.f

Here it says copy the folder. Not just the script file inside of it.

Well the midi keyboard is not with me but I can see Impact LX in the control surface section at the preference window. I will try it whenever I get to the store and let you all know if it works or not.

It's working. As I wrote in my previous comment, the folder should be copied. Not just the file. Therefore control surface is working. All of the buttons are working. I'm happy about it

Jaymeson · Post by **Jaymeson** » Sat Jan 13, 2018 2:43 am

Ok so i had found this link before, and have followed it to a T. Not finding it in the control surface. I have no idea what to do and the only resources i can find are discussions giving this link. HALP!

I must add that i am using an Impact ix61. I realize it says LX/GX but everything i look up leads to that. It should work still right? I just dont see Ableton not supporting a midi keyboard in general. It picks up the controller in every other part except Control Surface.

S4racen · Post by **S4racen** » Sat Jan 13, 2018 2:16 pm

Umm, if it hasn't got a control surface script it can't be a control surface...

Cheers
D

Street Spirit · Post by **Street Spirit** » Wed Oct 31, 2018 3:49 am

Hey very informative post. Looking at getting the LX25 key.
Does anyone one who has an LX model, know if the pads work as clip launchers?
Similar as the Novation Keyboards.

Cheers

Chrome Head · Post by **Chrome Head** » Fri Nov 16, 2018 5:09 am

Hi--using the Nektar LX 49+ with a Live 10 trial. Followed the procedure for putting the Remote Script folder in the user remote scripts section.

Nektar nor Impact are appearing in the drop down menu of control surface still after doing all of this. Has Live 10 stopped supporting anything Nektar altogether? Seemed to have worked here for users in the past.

S4racen · Post by **S4racen** » Fri Nov 16, 2018 6:26 pm

Probably broken.... Live 10 changed a little but there were big changes in 10.0.2 and 10.0.4 so unless you have a script thats been updated in the last few weeks I would;dn't give it much hope...

Cheers
D

Nektar LX 61 User Remote Script isn't recognized

Nektar LX 61 User Remote Script isn't recognized

Re: Nektar LX 61 User Remote Script isn't recognized

Re: Nektar LX 61 User Remote Script isn't recognized

Re: Nektar LX 61 User Remote Script isn't recognized

Re: Nektar LX 61 User Remote Script isn't recognized

Re: Nektar LX 61 User Remote Script isn't recognized

Re: Nektar LX 61 User Remote Script isn't recognized

Re: Nektar LX 61 User Remote Script isn't recognized

Re: Nektar LX 61 User Remote Script isn't recognized

Re: Nektar LX 61 User Remote Script isn't recognized

Re: Nektar LX 61 User Remote Script isn't recognized

Re: Nektar LX 61 User Remote Script isn't recognized

Re: Nektar LX 61 User Remote Script isn't recognized

Re: Nektar LX 61 User Remote Script isn't recognized

Re: Nektar LX 61 User Remote Script isn't recognized