Hi, I was waiting for mk3 - and I have it now… keybed is great for my need (silent and responsive in playing, although a bit sharp for glissando on B3 )
But I have a huge issue with random latency when playing Virtual instruments - it happens without recognisable pattern - and just for a few brief moments (comping or arps, for a few notes/chords only… pure random). I don’t have such behaviour with my other keys using the same configurations (IK iRig I/O, Yamaha YC61)…
It is the same in Logic Pro (11) as well as in Cubase Pro 13…
It is the same on Mac (MBPro M3 Pro), as well as on Windows (Thinkpad T14, i5, Cubase)…
It is the same on standalone VI (Halion 7, Kontakt 7, Pianoteq 8)
It is the same on different USB ports (direct port on computer, or through hub)
As it is something I have never experienced before - I suppose it should be a kind of firmware issue - but as noone mentions it here - could it be my device is broken?
I concur with @LBH here, it sounds like something computer related with the ‘random latency’, can you try Midi over the Midi DIN ports and see if it still occurs?
from an IT perspective, have you tried a different cable? I assume you are using the usb port though you didn’t say in the post.
on the computer side, what is your I/o buffer set to? and can you better describe the total chain on connection. like what sort of cable you are using? the M3 MBP doesn’t have a usb-a port on it so are you using your own cable or what sort? using a usb hub? all parts in a chain that could isolate where the issue is coming from or how it may be compounding.
direct USB connection to computer (yes, there is no USB-A port on MBP, but there is Apple USB-C to USB-A adapter… as well as there are USB-C to USB-C cables…)
I was using standalone versions on both systems, as well as AU plugins in Logic Pro on MBP, as VST3 plugins on Cubase 13 MBP and on T14
I’ve removed my EVO4, and tried with Presonus Audiobox 96, by using MIDI DIN cables, also…
So - it is not a IT HW issue (well, if it is - I have two “broken” premium laptops, that works with other keyboards well)
It is not a “cable” issue, as I have tried different cables
It is not a “DAW” issue, as it is happening in Logic and in Cubase the same way
It is not a “VI” issue, as I have tried different instruments by different brands
It is not a “direct computer connection” issue, as it is the same through TB4 Dock, as well as direct connection to computer…
Trust me - I have tried all of the above, and one thing I left for the last possible solution was to disable the aftertouch (as it could in some dimensions cause the issue) - but as it is not an option on MK3 (???), I’ve choose to use the Custom curve for Aftertouch, and made it 127 all across (so it picks only the 127 values to engage - ergo, very rarely)… And it seems to work much better now…
If it is not a FW issue, the only one left I can see is that my device is broken?
You wrote you have issues with arps. Is this with arp presets or when using the controlers arp? if it’s a arp preset and the controller is’nt used, then i can’t see it’s about the controller.
But i can’t test and can’t rule out issues then.
I meant a preset in a Arturia instrument application.
I don’t have the applications you mention.
It sound like you are not using Keylabs onboard arp features. Then i can’t see how it should be a Keylab issue.
But again - I don’t have a Keylab MK3. You are welcome to contact Arturia support.
Can you post a audio recording showing the issue?
What soundcard do you use? What Samplerate do you use?
Keep in mind, that different instruments, and even different presets in the instrument can use more or less CPU power. I don’t know if this can explain what you experience.
A buffer of 64 can require a very fast CPU. A buffer of 256 can still require a very good CPU. That all depend.
Well - to sum some recent “findings” in several different environments.
It looks like when I am not using the Sustain - it works as it should (without latency “poppings”).
But when I engage the pedal (for Piano, ePianos, …) - it is here again - random popping and it’s not just latency, but some kind of like there are too many information sending to the DAW/standalone virtual instrument (on both platforms - Mac and PC, using different DAWs and/or different Virtual instruments… but it last just for that very few (mili)seconds… and then again happens occasionally
I’ve even tried to move my pedal to Aux pedal (and allots CC# 64 to it) - but it is the same - so it is not an HW issue with Sustain pedal jack… and I have tried different Pedals (Kurzweil, Yamaha, M-Audio) - the same, so it is not “the pedal issue”
I have even noticed the same behaviour when using sustain pedal for rotary engagement on B3 VI’s…
So - to make a kind of conclusion up to now: it seems there are issues with CC messages for CC# 64 (when using CC# 1 for rotary it just works as it should)…
I want to point out that I have used several different keyboards (M-audio, Native Instruments, Studiologic) in the past few weeks using the exact same settings, same software, same PC, same audio interface etc., and never experienced this random latency issue.
From my perspective, this must be a problem with the unit.
Seems to me it also comes form pressing the damper pedal, did not think about it before you mentioned it.
I’ve already contacted customer service and am hoping there’s a fix or solution.
Well, orck19w got the support answer, and it seems it really is an issue…
and it can be a kind of “resolved”, but at the moment exclusively in USER mode - you need to make “Sustain Pedal” type to “Control” (as it is exp.pedal, ie), and not to “Switch” mode… And it really resolves the issue completely.
BUT! it works only for User mode - when you are working in DAW mode, you cannot change the type of Sustain Pedal input to “Control”, as it is - still - “hardcoded” to Switch mode
So - the only way to use the “keyboard controller in a DAW” is not to use it in a DAW mode?
thankyou for that info solution. I am not sure if you have tested it, but is the pedal also mis-assigned in Arturia mode as well? So do you need to run all pedal control inside of UserMode or is just the DAW configuration that is hardcoded wrong?
Pedal is - well - a pedal, not a continous controller (in a MIDI world, I am not talking about reallife acoustic instruments), and this is a workaround, not a permanent solution.
As they wrote:
This issue has been spotted a few days ago, reproduced on our side, logged and developers are working on a fix now. I added your comments and experience to the log.
→ A “hotfix” will be deployed before the planned update for the KeyLab to fix it among other things.
)
