Hi
 
I have this problem that have me really annoyed, i have Nektar LX88 integrated with sonar platinum, and if i load kontakt 5 with, for example a piano library, after a few minutes that i start playing sonar stops responding and i get that message of ''Sonarplt.exe has stopped working''
 
If i put the task manager to monitorize it doesn't show anything weird....
 
 
It can't be my controller because if i play the same piano library with kontakt standalone it works fine
 
I have win 10 x64, fx8370, 8 gb ram, integrated soundcard with asio4all

tried fl studio and this ain't happening.... is a sonar problem, help, i want to keep using sonar

Reigner
Hi
 I have this problem that have me really annoyed, i have Nektar LX88 integrated with sonar platinum, and if i load kontakt 5 with, for example a piano library, after a few minutes that i start playing sonar stops responding and i get that message of ''Sonarplt.exe has stopped working''
If i put the task manager to monitorize it doesn't show anything weird....
 
It can't be my controller because if i play the same piano library with kontakt standalone it works fine
I have win 10 x64, fx8370, 8 gb ram, integrated soundcard with asio4all
 

At least try dumping Asio4all and trying WASAPI. At best, get a real audio interface. Yes I know it works with FL Studio......

I have an LX88+. Good controller but the Sonar integration has been nothing but trouble for me. I have tried working with Nektar to get it fixed since December. Their support is very good, but still no fixes. Recently I had a problem where Sonar would crash on launch every time. It turned out to be the LX integration again. After messing about, reinstalling etc. I removed it and have given up on the LX integration for now. The problems don't seem to be with Sonar but with Nektar's integration - it never really worked as promised and has stability issues.

35mm
I have an LX88+. Good controller but the Sonar integration has been nothing but trouble for me. I have tried working with Nektar to get it fixed since December. Their support is very good, but still no fixes. Recently I had a problem where Sonar would crash on launch every time. It turned out to be the LX integration again. After messing about, reinstalling etc. I removed it and have given up on the LX integration for now. The problems don't seem to be with Sonar but with Nektar's integration - it never really worked as promised and has stability issues.

oh, that's outrageous! my sonar sometimes crash on launch also, so there's nothing we can do then....

I don't know if there is anything we can do but wait. The LX88+ is a good keyboard/controller, but the integration side has always been problematic for me. It's probably going to be better to set it up as a generic controller because so far I think Nektar's integration is a marketing gimmick. I did at one point have it working ok and it was useful - press the Mixer button and the mixer came up on the screen and the faders and mute buttons worked great. Press the Inst button and the VST instrument GUI would display and the knobs would sometimes control it. But for me, it all went foobar about a month ago and suddenly stopped Sonar from launching. I would send it back if it wasn't for the fact that it's a pretty decent 88 key keyboard. However, as I said Nektar support do actually talk to me - reply (normally the same guy) in a timely manner and do genuinely seem interested in getting to the bottom of the problems. This makes me think they are quite a small company that can still be in touch with their customers. But so far no fix!

I think their main problem is that they have tried to almost hack into popular DAWs via their APIs to get the integration and that is always going to be a major job trying to keep up to date manually coding for all the popular, supported DAWs. The only DAW they really seem to concentrate on is BitWig which they bundle the light version of, and despite it's reported popularity, it seems to be a pile of crap - not that I spent too long trying it out. I also have FlStudio which has built-in support for the LX, but is pretty basic and not very useful.

35mm
I think their main problem is that they have tried to almost hack into popular DAWs via their APIs to get the integration and that is always going to be a major job trying to keep up to date manually coding for all the popular, supported DAWs. The only DAW they really seem to concentrate on is BitWig which they bundle the light version of, and despite it's reported popularity, it seems to be a pile of crap - not that I spent too long trying it out. I also have FlStudio which has built-in support for the LX, but is pretty basic and not very useful.

all the things you say are very disapointing... i will never spend more money in something of nektartech
 
btw, my lx88 comes with studio one artist 2.6, i thought that was the daw with the best integration for this controller, ''bitwig'' looks really bad lol
 
 

May be related, maybe not, but as I have an LX88, thought I'd share this story just in case...
 
I use my LX88 in a live setup with a laptop running SONAR. It had worked just fine for a few gigs and practice setups, spread out over a couple years. The SONAR integration had worked just fine too, from the start. Then one day a couple months ago after hooking it back up and playing a couple minutes, it would just hang up, with any held notes just droning on forever until I quit SONAR. It was a really hard problem to pin down, as SONAR didn't exactly crash, and it was happening on every synth plugin that was running, and after a seemingly random number of minutes of playing after a cold start.
 
After a good night's sleep it occurred to me to try to reproduce the problem while running MIDI-OX, to see if the MIDI stream would tell me anything. Sure enough, it hung again, and then the clue revealed itself: when it hung up, it would always happen on a Sustain Pedal Down event. What in the world? I then confirmed by playing with the original SONAR setup, and sure enough, I would get beautiful music and no hangs as long as I never pressed on that sustain pedal.
 
My mind started to race... I started to think that my LX88 somehow went bad somewhere in its sustain circuit. I started to file through my order history to see if it was still under warranty. Nope. Dang! Then as I thought about the LX88's sustain circuit, as is oft the case, my thoughts went backward up the chain, and then drifted out through the Sustain Pedal Jack, down the cord, and then stopped at the pedal. Could it be? It *was* after all a rather cheap-o pedal, one from Hosa that I had picked up expressly for live gigs:
 
 

 
Dripping with curiosity, I ran down to the basement studio and pulled a known-to-be-good M-Audio SP-2 sustain pedal from the controller on my desk. My heart racing from the thrill of the hunt, I ran back up, yanked that Hosa out of the jack, plugged the SP-2 in the LX88, and commenced playing and sustaining. Guess what? No hangs. Even after hours of practice (and then performance) with *lots* of sustains.
 
My best guess as to what happened is that the switch contacts in the Hosa got dirty or corroded, which made the switch chatter, enough so to overwhelm the switch debouncing algorithm in the LX88 controller's firmware. In retrospect, that is a remarkable thing, that a switch could be that bad, and/or that it could overrun a processor's debounce buffer to the point that it would CRASH the keyboard's own internal firmware OS. It speaks to me of firmware that did not go through as rigorous a testing cycle as perhaps it should have. They do say hindsight is 20-20, but quite frankly, in over 40 years of playing, I've never had a keyboard crashed by a sustain pedal. Until now.
 
To the OP - based upon your system's symptoms, your issue is probably a bit different, but based on this experience, you may try to see if a MIDI-OX trace would reveal something of value?

losguy
May be related, maybe not, but as I have an LX88, thought I'd share this story just in case...
 
I use my LX88 in a live setup with a laptop running SONAR. It had worked just fine for a few gigs and practice setups, spread out over a couple years. The SONAR integration had worked just fine too, from the start. Then one day a couple months ago after hooking it back up and playing a couple minutes, it would just hang up, with any held notes just droning on forever until I quit SONAR. It was a really hard problem to pin down, as SONAR didn't exactly crash, and it was happening on every synth plugin that was running, and after a seemingly random number of minutes of playing after a cold start.
 
After a good night's sleep it occurred to me to try to reproduce the problem while running MIDI-OX, to see if the MIDI stream would tell me anything. Sure enough, it hung again, and then the clue revealed itself: when it hung up, it would always happen on a Sustain Pedal Down event. What in the world? I then confirmed by playing with the original SONAR setup, and sure enough, I would get beautiful music and no hangs as long as I never pressed on that sustain pedal.
 
My mind started to race... I started to think that my LX88 somehow went bad somewhere in its sustain circuit. I started to file through my order history to see if it was still under warranty. Nope. Dang! Then as I thought about the LX88's sustain circuit, as is oft the case, my thoughts went backward up the chain, and then drifted out through the Sustain Pedal Jack, down the cord, and then stopped at the pedal. Could it be? It *was* after all a rather cheap-o pedal, one from Hosa that I had picked up expressly for live gigs:
 
 

 
Dripping with curiosity, I ran down to the basement studio and pulled a known-to-be-good M-Audio SP-2 sustain pedal from the controller on my desk. My heart racing from the thrill of the hunt, I ran back up, yanked that Hosa out of the jack, plugged the SP-2 in the LX88, and commenced playing and sustaining. Guess what? No hangs. Even after hours of practice (and then performance) with *lots* of sustains.
 
My best guess as to what happened is that the switch contacts in the Hosa got dirty or corroded, which made the switch chatter, enough so to overwhelm the switch debouncing algorithm in the LX88 controller's firmware. In retrospect, that is a remarkable thing, that a switch could be that bad, and/or that it could overrun a processor's debounce buffer to the point that it would CRASH the keyboard's own internal firmware OS. It speaks to me of firmware that did not go through as rigorous a testing cycle as perhaps it should have. They do say hindsight is 20-20, but quite frankly, in over 40 years of playing, I've never had a keyboard crashed by a sustain pedal. Until now.
 
To the OP - based upon your system's symptoms, your issue is probably a bit different, but based on this experience, you may try to see if a MIDI-OX trace would reveal something of value?

Good information you provide, the curious thing is that the hanging of my sonar happens also when i use the sustain pedal with the piano library in kontakt 5.... but if i play in kontakt standalone with the sustain pedal there's no problem at all

So, can't be my sustain pedal (and also is new, i bought it with the lx88 like a month ago)

I will check with midi ox then