asked Oct 11 '17 at 03:23 by AndyZehner (21)

I get the message "Nektar Impact LX25+ crashed | array index out of range" each time I try and start Bitwig Studio 2. I had been using Butwig 8-track OK, but this new error message is happening all the time since I upgraded.

Opened a ticket with Nektar, they are aware of the issue and working on a fix. I'll post here when I get more info.


answered Aug 18 '18 at 04:02 by ctrauma (21)

I have the same problem.. did you ever get around this?

here is the stack trace from the log:

[2018-06-10 14:32:17 notifications error] IMPACT LX25+ crashed: Array index out of range: 53
[2018-06-10 14:32:44 float-gui-widgets error] :
    java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 53
    at jdk.internal.dynalink.beans.BeanLinker.rangeCheck(
    at jdk.nashorn.internal.scripts.Script$Recompilation$1951$59389$IMPACT_LX25+_control.Z8112FC4E83E92470E(IMPACT_LX25+.control.js:142)
    at jdk.nashorn.internal.scripts.Script$Recompilation$1948$58100A$IMPACT_LX25+_control.Z811100C303EB1F922(IMPACT_LX25+.control.js:138)
    at jdk.nashorn.internal.scripts.Script$Recompilation$1946$32396A$IMPACT_LX25+_control.Z81137977D3E8A9321(IMPACT_LX25+.control.js:78)
    at jdk.nashorn.internal.scripts.Script$Recompilation$1945$79975$IMPACT_LX25+_control.nektarinit#L:181#L:181(IMPACT_LX25+.control.js:182)
    at jdk.nashorn.internal.runtime.ScriptFunctionData.invoke(
    at jdk.nashorn.internal.runtime.ScriptFunction.invoke(
    at jdk.nashorn.internal.runtime.ScriptRuntime.apply(
    at com.bitwig.flt.control_surface.proxy.BitwigStudioHost$
    at com.bitwig.flt.control_surface.proxy.BitwigStudioHost$ScheduledTask.invokeCallback(SourceFile:675)
        at fhk.qCA(SourceFile:95)
    at fhk.rEp(SourceFile:91)
    at zwq.YKd(SourceFile:128)
    at GER.Nly(SourceFile:77)
    at YsC.ucN(SourceFile:249)
    at OrX.qCA(SourceFile:241)
    at HXd.YKd(SourceFile:252)

I have to say, being a node developer, this is some butt-ugly js, I'm guessing it is machine generated, no human would write code like this..

It looks like it possibly dies in here in the nashorn js runtime,or the BeanLinker java class above it in the stack,:

for (var c = 0; c < Z810D1D0423EF02DA3; c++) 0 < a && !Z811130D833EAE1290(DIRECT_KNOB_GROUP1_MAPPINGS[c]) && (Z811130D833EAE1290(ACTIVE_MAP_OBJECT.Z8114D80893E74928A[Z810D8E0753EE938DF[c]]) && (DIRECT_KNOB_GROUP1_MAPPINGS[c] = ACTIVE_MAP_OBJECT.Z8114D80893E74928A[Z810D8E0753EE938DF[c]]),
        Z811130D833EAE1290(DIRECT_KNOB_GROUP1_MAPPINGS[c]) ? directParamsInUse.push(Z810739DE93F4EB8BB.Z81121ED093EA0D836[DIRECT_KNOB_GROUP1_MAPPINGS[c]]) : (DIRECT_KNOB_GROUP1_MAPPINGS[c] = b.Z8114FAD773E72106A[Z810D8E0753EE938DF[c]], Z811130D833EAE1290(DIRECT_KNOB_GROUP1_MAPPINGS[c]) && directParamsInUse.push(Z810739DE93F4EB8BB.Z81121ED093EA0D836[DIRECT_KNOB_GROUP1_MAPPINGS[c]])));

According to the OpenJDK sources for the nashorn runtime BeanLinker a range check is failing here:

 private static final boolean rangeCheck(final Object array, final Object index) {
        if(!(index instanceof Number)) {
            return false;
        final Number n = (Number)index;
        final int intIndex = n.intValue();
        final double doubleValue = n.doubleValue();
        if(intIndex != doubleValue && !Double.isInfinite(doubleValue)) { // let infinite trigger IOOBE
            return false;
        if(0 <= intIndex && intIndex < Array.getLength(array)) {
            return true;
        throw new ArrayIndexOutOfBoundsException("Array index out of range: " + n);

The code about ( line 369 ) is trowing and ArrayIndexOutOfBoundsException, is there some fix I can make to the controller js code to not trip the number parser?

Looks like bad number parsing to me but I gave up Java for sanity long ago..

Any thoughts from the support folks on a fix?


answered Jun 10 '18 at 18:58 by ctrauma (21)

edited Jun 10 '18 at 20:56

bump still an issue in 2.4 beta 2


answered Aug 16 '18 at 04:27 by ctrauma (21)

edited Aug 16 '18 at 04:28

still an issue in 2.4 beta 3


answered Aug 24 '18 at 15:54 by tomkarachristos (21)

Just heard from Nektar support, fix is in testing and should be released soon, will post here when it is out..


answered Aug 31 '18 at 15:24 by ctrauma (21)

Just got word from Nektar:

Hi Scott, Just to let you know the issue is fixed and the new integration files will be included in the next update from Bitwig.

Best Regards,



answered Sep 05 '18 at 15:45 by ctrauma (21)

Beta 5 release notes:

Changes in Bitwig Studio 2.4, Beta 5 Improvements:

  • Right-clicking in an empty modulator slot should target the modulator slot
  • "Selection follows notes" in the multisample editor will now scroll selected zones into view
  • Show inspector when undocking a sampler expanded device view
  • Update Nektar controller support
  • Made MPE option in HW Instrument less hidden and more consistent with plug-ins
  • Added pitch-bend range setting to LinnStrument controller extension
  • Auto fades for audio clips and events are now applied in more cases when the user edits audio material

answered Sep 07 '18 at 03:38 by ctrauma (21)

edited Sep 07 '18 at 03:40

I can confirm it does not crash any more, but I can't get the controller to do anything in bitwig. Testing with QSynth shows that the controller is sending MIDI data and plays fine, and I have it selected in Bitwig settings. Tailing in the log doesn't show much although these two warnings seem odd:

[2018-09-06 23:48:46 base-control-surface warning] Could not register Jython interpretter: org.python.jsr223.PyScriptEngineFactory
[2018-09-06 23:48:46 base-control-surface warning] Could not register JRuby interpretter: org.jruby.embed.jsr223.JRubyEngineFactory

I'm testing in Bitwig with the PHASE4 instrument which I can hear in edit mode when notes are selected with the mouse, but no joy with the contoller. Any advice on getting this working?


answered Sep 07 '18 at 06:04 by ctrauma (21)

Looks like I had the driver model setup to use JACK instead of ALSA, now that I have it set to ALSA I can see MIDI note data in the Console Script Console and info shows up in the Studio I/O panel. No sound yet, but I think that was the issue.


answered Sep 07 '18 at 07:18 by ctrauma (21)

edited Sep 07 '18 at 07:21

In info panel, input had to be "IMPACT LX25+ -LX25+ Keyboard" instead of "IMPACT LX25+ -LX25+", now I am able to hear the instruments.. all good..

Hopefully someone finds this info useful.


answered Sep 07 '18 at 07:38 by ctrauma (21)

edited Sep 07 '18 at 07:40

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported



Asked: Oct 11 '17 at 03:23

Seen: 1,169 times

Last updated: Sep 07 '18 at 07:40