Kore 2.1 is acting very weird

I am having this problem and it really did make me wonder if my Kore 2 controller was broken. I have indeed tried rebooting my mac as suggested by ew. I have also tried setting my hardware sensitivity to lower values and also at 0%. The problem still occurs frequently. The red ring jumps around to different controls and also random buttons are being pressed while I'm not touching them. The button problem occurred while I was toggling a button on and off to modulate a bass sound. During which other buttons where randomly being pressed without me touching them.

This is playing havoc with me as I'm trying to create a number of presets for VST's that I'll share on the forum. Hope you can come up with a fix sometime very soon.

 

Yeah I was afraid that this might be a hardware issue too so today I tested my computer with a friends Kore 2 (that isn't having this issue on his system). Sho nuff, when I plugged it in I experienced the same issue. So this probably isn't a hardware issue as my friends unit works fine on his computer and hates life on my computer in the same exact way that my Kore 2 does.

 

Hmm, I hope NI is aware of this big problem and will fix it soon.

 

I don't really understand how it made it past beta like this. It seems to me that it's only affecting mac users. But don't they a own a few macs to test on? And was there not some dude trying Kore 2.1 on of them going "Bloody hell, the thing's going nuts!"

Not a good update, I think I'll go back to 2.0. I've just been afraid that would mess something up. But this is too annoying.

 

I'm on a PC and have this problem

 

I also have a PC running XP service pack 3 with Pro Tools 8 LE and Ableton Live 8.0 and noticed this behavior after installing the latest Kore 2.1 drivers.

I sent a support request and they asked me to send them my controller to see if it needed to be replaced. All I wrote was that I had tried all of the suggestions on the support site and that nothing had worked. The controller constantly sends data from the third knob from the top left. In a program like Pro Tools, this means that every control message received from Kore is counted as another Undo level. Since the messages happen so fast, I am left with zero levels of usable undo, not to mention erratic automation data from that knob.

My Kore 2 controller worked fine for months with 2.0. I'll report back to share what happens. Has anyone else been asked to send their controller back in? Any success stories? Please share.

 

Try setting the "InPort" and "OutPort" in the same dialog to "None". Note: When you open that dialog again, Kore resets those back to the default. (Prolly a bug).

Your issue sounds similar to mine:

 

Same 4 me. Just want to show up, that there's another user outside who's annoyed. ;-)
I really like the Kore2 controller, but with this behaviour...

 

Thanks jbone for the hint however it didn't change anything. The controller still acts weird. Any NI guy reading this thread?

 

This 2.1 is the most misbehaving version of Kore yet. I keep checking to see if there is a maintenance update in development. I don't see how they can let this version be out for long.

 

They are aware. Just so all you guys know, it's not a software problem or else they would have fixed it in the last update. I had this problem since day one. It's a hardware problem. I don't think there will be a fix for this.


.-.

 

No it isn´t.

With the previous version of Kore the controller definitely works. I have tried this with PC and Mac.

 

Dam straight this is not a hardware issue!

I have had a problem with my kore hardware being broken and just got a brand new one a little while back. It worked perfectly up until this new 2.1 update.

It has to be software, I think the fact that all these people stating that they never had this issue before the new update clearly indicates its a software problem.

 

You have a point, I do understand that. But if it were a software problem, then all Kore 2 users would have the same problem. As it stands now, only a select amount of people have stated that they have this problem. This is why I stated that it is a hardware defect. Now, here's the flip side. When I used the Kore 2 controller as a midi controller just the other day, the controller page header functions as expected. So, it might just be a problem with the Kore 2 software. At this point the only people that can figure out what the hell is wrong would be the Native Instruments developers themselves. They really need to look into this and find a resolve.



.-.

 

What if they have the problem, but just haven't reported it?

 

There probably is a percentage of users who have not reported it. If I recall correctly, there are a percentage of users who don't have this problem. Maybe ew or Kymeia can chime in. Also others that are not having this problem.


.-.

 

Ok...you can add me to the percentage of users who have not reported it...but now since this thread...I guess I'm going to unhappily report it.

I would guess many "light" users of KORE would never encounter this issue...especially if they aren't assigning controllers.

 

FYI: I've found that when routing MIDI from one track to another in Ableton Live, if there is a Kore instance on each track, moving one Kore knob on one Kore instance moves the corresponding Kore knob on another Kore instance.

As you might imagine, that can lead to all sorts of confusion.

Setting all of Kore's MIDI controller parameters to null in Options->Hardware->MIDI Controller seems to remedy this problem. My guess is that somehow, MIDI messages are being sent between Kore instances. Its weird, because I thought that Kore uses host automation, not MIDI.

See also: http://www.native-instruments.com/forum/showthread.php?t=98614

 

So about 2 months ago I was experiencing the same problem. The top third knob from the left was constantly sending data. No matter what I did it would just jump back to that knob. I sent the unit in and they sent a replacement. It took about 2 months to get a replacement because they were on back-order. This is my third Kore 2 unit. The first one I had failed on me after my first firmware update to 2.0.2. The second one failed and started acting in the way that this thread describes after I updated the driver to 2.0.1 and then the 2.0.4 update.

Tech support said that it is unusual for a Kore 2 unit to fail in this way and they were surprised to hear that it had happened to my second unit. Lets hope that this 3rd unit is more robust. It came with the latest firmware update and everything is working properly, so I don't plan on updating any of its software now that its working.

My personal take on this, based on my experience, is that some of the units don't like firmware updates. I could be wrong, as I know nothing about firmware. However my faith in hardware updates is shaken.

Although it took a while to get a replacement, I feel like Tech Support was very helpful and has always taken care of me when I had a problem.



-Brau

 

Just adding my voice to the fray here. Even at 0% sensitivity, I've got things jumping around and going nuts.

Kore 1 hardware, G5 Quad, Leopard 10.5.8, Kore 2.10.009

I really hope this gets fixed. It's useless in this state.