Arturia Forums
Controllers => KeyLab MkII => KeyLab MkII - Technical issues => Topic started by: Rik-The-Mix on November 06, 2020, 01:37:07 pm
-
I was so happy to finally see a Firmware update from FW 1.1.3 to FW 1.2.4 which states in the Bug Fixes that the stuck notes issue has been fixed. Sadly I can report this is not the case. I'm still getting stuck-on notes using MIDI out of the USB connection into Logic.
So, back to the workaround which is to use the 5-Pin MIDI connection which doesn't suffer with the problem. Remember to turn off USB MIDI in inside your DAW's preferences.
I'm expecting a complete fix soon Arturia... please!
-
I can confirm,stuck note here too! Strange thing is that I only have this problem in USER mode,not in Analog Lab or DAW mode.
Setup : Analog Lab Mode midi CH1
DAW mode midi CH1
USER mode has always been on midi ch2 but since this morning the note D always hangs.When I change USER mode to midi ch3 the problem is fixed.Very strange that the midi messes up as I don’t have any other equipment apart from the KeyLab 61mkII and an Apollo Twin X.
-
I just tested with my system.
With all my surprise I was not able to get only one stuck note in 3 hours of wild playing!
I have a new much powerful notebook, so I had to install everything new: all my hosts (Reaper and Cantabile) and Arturia USB driver which is quite new.
To me this seems the most important piece of software, it was already getting better, this last one seems perfect.
Then I upgraded firmware of Keylab mkII 61 (1.2.4).
Now everything seems extremely solid, I tried in every way to make my system fail: no way.
I am so happy!!!
-
Just got the Mkii a few days ago. I can only comment on the new (1.2.4) firmware, as I immediately updated the unit before a note was played. Notes stuck within a minute of playing.
As evident from numerous posts throughout the model's history:
1) This is pervasive
2) This is ongoing
3) This is a problem.
I'd wait for a fix, but it's apparent that strategy doesn't work. I'll soon be selling this off to the next victim.
-
Hi all,
I've just received a replacement Keylab Essential 61 unit from Arturia under warranty. I suffered stuck/hanging notes on the new unit almost immediately. I'm using the supplied USB cable for power and MIDI connectivity.
Looking over the various threads, this seems to be a common issue. My question is; does this relate ONLY to the KeyLab ESSENTIAL range, or does it also affect the KeyLab MKII units?
Is the issue solved by using the MIDI DIN connectivity?
It would be good to have my expectations set, and I can decide if I need to get a controller from another manufacturer (NI or Novation maybe).
Thanks
James
-
I seem to be having this issue also - stuck notes at the low end....
I have updated firmware but to no avail...
any help Arturia? I need to solve this problem fairly sharpish.... using logic pro x
-
Hi, I am too here waiting for the fix.
I just tested on Presonus Studio One,
I use Keylab MkII as an external device.
The problem seems to be when playing with the block size set to 4098 or 8192, a note is getting stucked and keeps repeating until I close the DAW.
When playing with the block size set to 32 or 64 it seems that it gives you a lower chance to encounter the same problem.
-
I was experiencing this same issue but I found out that in my case it was related to using USB2 ports in my desktop PC. After switching the KeyLab to USB3 ports in my PC, and on my Surface Pro 7, the missing/stuck notes issue went completely away (I've been using it for over a week now). I have a Keylab 61 MkII with firmware 1.2.4.
Hope this helps someone else.
-
I'm experiencing this myself. I received my KLII 88 a few days ago, and had enough dropped notes/Key Offs so as to make it unplayable, in addition to the device sometimes being unable to even be enumerated on the USB bus. I updated the firmware to 1.2.4, and while it's much improved, the dropped notes/Key Offs are still noticeably present. I also switched from USB MIDI to running 5-pin DIN cables to my MOTU M4 interface, which improved things further, but again still did not completely eliminate the problem. I don't experience a single dropped event when putting my 32 year-old Yamaha SY-77 through the M4 over the same cables, so I'm reasonably sure it's an Arturia issue. When using the KeyLab II, running Reaper and FLStudio doesn't make a difference - events are missed in both packages with equal frequency. For reference, I'm running on a 32 GB system under Windows 10. All USB cables have been demonstrated to work fine with other devices, and USBView shows information that looks good.
Edit: USB is going in through a port on the machine's motherboard, not through a hub.
It's been a pretty disappointing experience that's kind of soured me on the idea of any further Arturia hardware purchases. As a professional embedded firmware coder myself, my initial thought was that perhaps it was a USB issue, but given that there are still lost events over the 5-pin jacks going to a known working USB MIDI interface, I'm inclined to think there are still issues within the KeyLab II firmware itself. It's been close to a year since the last firmware update - does anyone know if there are there any plans for another anytime soon? If not, I may have to consider returning the instrument, because I can't just eat a thousand bucks for a device that has doesn't work reliably. I think the only troubleshooting step I have left is to put the device on a stable bench power supply (instead of USB) and determine if the lost messages still occur over the 5-pin ports.
-
An update - after putting the KeyLab on a solid 12V 10A external supply, the issues appear to have been completely resolved, and the unit no longer drops any events on either USB MIDI or external MIDI. Looks like 1.2.4 does in fact fix the "stuck notes" problem, but there's still a potential for problems since the KeyLab could possibly need a bit more current than the USB port is supplying. At least, that seems to be the case on my hardware.
Interestingly, the USB configuration descriptor that USBView shows for the KeyLab II has a MaxPower value (0x32) that corresponds to 100 mA of current, which seems awfully low for something that has this many LEDs on it. In any event, if someone reading this is still experiencing dropped/stuck notes after updating their firmware to 1.2.4, try putting your KeyLab on an external power supply that can provide a couple of amps of current. The manual specifies 1.0A, but it won't hurt to be able to give it a bit more if needed.
-
I am getting stuck notes on my Keylab Essential 88 using the USB output as my midi connection. I switched to using a midi cable into the midi input of my Focurite 8i6 and a seperate power supply and the problem no longer exists. My suspician is that the problem is NOT with the keyboard but with my computer.
-
I just had to register to this forum to let others know that I'm a +1 with stuck notes still happening with the latest firmware. Pretty disappointed that it only took me 2 days to stumble across this issue. It is surely a show stopper for serious use of the Keylab mk2... It renders it useless for live performances to say the least.
I've also tried it with an external 9V 1A power supply, but no change.
-
I am having the same issues with my KeyLab 61 MK2 and am using a power supply as well, with the latest firmware update.
-
I am having the same issues with my KeyLab 61 MK2 and am using a power supply as well, with the latest firmware update.
I may have fixed my issue. It seems like it for now at least. Can you try with another usb cable? And also try to plug it in without anything else plugged in to usb connectors close to it.
I haven't had the hanging notes after doing both those things. I'm not sure which solved it, but I have a suspicion that the Keylab is not getting enough power when It is connected to a usb port that shares it power delivery with other ports close by...
I'm currently using the included Ground adapter to always ensure that I feed the input with a steady 1A through a usb charger...
-
June 2022 - MKii just arrived in the mail from Amazon. Stuck keys multiple times within 1 minute right out of the box. USB to Mac mini M1; using LogicPro w Omnisphere.
I don't want an unnecessarily complicated extra midi cable setup. I want it to work like other keyboards.
I am not yet invested in this thing. Should I just send it back to Amazon?
-
By "stuck notes" do you mean that they don't work? Cause I am having an issue where one D and one A# out of 2 don't work, over the whole keyboard. It's really bad for a premium keyboard.
-
+1 for this issue...just got the KL61 MKII today and noticed the issue within 5 minutes of messing around with Analog Lab V.
I have the KL61 plugged into a USB port on the back of my LG USB-C monitor. MacBook Air M1 w/macOS Monterey.
No power supply on the KL61 itself. Lastest firmware.
-
+1 for this issue...just got the KL61 MKII today and noticed the issue within 5 minutes of messing around with Analog Lab V.
I have the KL61 plugged into a USB port on the back of my LG USB-C monitor. MacBook Air M1 w/macOS Monterey.
No power supply on the KL61 itself. Lastest firmware.
Plugging it into a USB socket in the back of a monitor is frankly asking for trouble. They're really only designed for mice and keyboards, or something similar requiring really low power.
With the latest firmware installed, in nearly all remaining instances this is being caused by the USB host not supplying enough power to the controller. If plugging it directly into you Mac still doesn't cure it, try powering it with an external barrel power supply, 9-12V DC capable of delivering 1A.
-
+1 here
Keylab MKII 61
Firmware 1.3.1
on Windows 10
Using it for over a Year now. I always used the regular MIDI OUT on it, so recognized the problem pretty late, when I played arround with some MIDI scripts.
Was switching from 5pin MIDI-Out to USB-MIDI, because the keyboard stopped sending MIDI after sometime (after maybe 5- 20min) and only worked again, when reconnecting. It doesnt turn off, you just hear the Windows-sound for disconnected USB-devices (mostly 2 times: first for the control section and second for the keys).
So I just tried only USB, bc who knows?
(I think it has something to do with the Vegas-/Sleepmode, because it appears that it happend quicker when I don't actively use the keyboard for a while, maybe also in combination with a buggy FL Studio Script [the official one], but it won't change when I turn it off... will test it some more).
This problem aside, regular MIDI is working just fine.
On the other hand USB-MIDI is on my keyboard kind of a mess. I got stuck notes (no note off signal is sent) and more frequently: missing notes, when playing more than one note.
I tried powering the Keyboard via USB with the Ground Loop Adapter and different USB-Chargers (old one with 5V-1A & newer one 5V-3A/9V-2A/12V-1.5A).
USB-powersaving plan on Windows is disabled. Powersaving in general is disabled.
Tried different USB-cables, different lengths, different brands and different combinations. Connected it with the PC via USB 3.0 and/or 3.1.
Same problems everytime.
So I tried an optional power supply (an universal power supply with the right polarity. I tested it on 9V and 12V with 3A.
still the same problems. Maybe there were a fewer stuck notes, but it is hard to replicate it evenly. Oh yeah, and I checked the power supply with a multimeter, just to be sure.
I did a reset to factory settings before i try all this.
I didn't test the keyboard on another system (mine is kind of old: AMD 1800x on a Asrock motherboard), but will do it til end of the week.
I attached an example of a MIDI recording (in FL Studio) where I recorded USB-MIDI and regular MIDI at the same time. I moved one two octaves lower to show the missing and stuck notes over a period of 50secs.
First I thought it's a power problem, because the more keys I press the higher is the chance of 1 (or sometimes 2) stuck notes, but with all the combinations for power supply i think it's still a software issue or a general flaw in the usb connection?
I don't know. Some people find a solution, some people don't. I wish there was an explanation for this...
It's a huge bummer, when you pay 500 bucks for this trouble.
-
+1 here
Keylab MKII 61
Firmware 1.3.1
Brand new unit plugging into my Kronos 88 via USB - I get stuck notes. Seems to work fine using the Midi Din connector.
I've tried:
- Different USB Cables
- Powering the unit off of a wall Cube
- Disabling Vegas Mode and Set Low Power to on.
I'm going to open a ticket with Arturia...
John
-
Hi,
*This is with Firmware 1.3.1*
I found a workaround for stuck on midi notes that worked for me.
I have my MKII plugged in via USB to my Kronos and was getting Midi notes stuck on. I added a small cheap UNPOWERED USB hub and it fixed the issue. You can purchase the one I used on Amazon - https://www.amazon.com/dp/B00L2442H0?psc=1&ref=ppx_yo2ov_dt_b_product_details
I'm not sure - but I believe that for some people the issue is a result of power and they need to use the wall cube or a powered USB hub.
For others like me, it may be a timing issue on slower USB 2.0 host devices and adding the USB hub adds a little delay which allows the host to digest the data. I'm not sure - just a guess...
I have a ticket open with Arturia. They are trying to blow me off - but I will keep pushing. Everyone with this issue needs to open a ticket so we can get them to fix this. All of my other controllers work fine with no issues. It is an issue with their design or firmware.
John