hey, i bought arturia keylab mk3 61 last week. my keyboard works perfect with analog lab, no problems.
so i wanna do sound design in logic pro with faders and knobs and i almost did it. (with stock sounds and stock plugins)
but the problem is when i (even slightly) touch the 4th knob, it mutes the whole sound. when i touch it back, unmutes again. basically i constantly have to keep my hand on knob 4 to hear anything. also if i never touch the 4th, all of the other faders and knobs working perfectly.
this is my first midi keyboard, sorry if i sound ignorant but im gonna lose my mind over it. someone PLEASE help agh
(pc: macbook air m2 (2022) (sequoia))
(also i did all the logic updates, installed logic script and got firmware uptades of keyboard etcā¦)
I use Logic but not a Mk3 KeyLab. Sounds like it could be a mapping problem. It could also be that Arturia has made it clear that their software (which I guess includes their hardware drivers) is not yet Sequioa compliant and advised Mac owners not to upgrade until it is.
This may or may not be part of the reason. When you rely on third-party (non-Apple) apps itās always wise to check if the developer has 'okād the OS upgrade before succumbing to Appleās nag-screens. I have no plans to upgrade to Sequoia until Arturia tells me to.
Maybe other Mk3 owners using Logic can chime-in with their experiences.
(EDIT: I guess you probably upgraded the OS before buying the keyboard which is unfortunate.)
I have KL3 61 and Logic Pro - and Iāve had that happen (Iām on Sonoma btw, I donāt think Sequoia is the issue)ā¦
Just checking the output in midi monitor and touching knob 4 is sending 'control 1 - with a value of 127 - then when you let go it is sending ācontrol 1 = 0ā
Hereās the output in midi monitor (touch, let go, of knob 4)
04:41:25.238
From KeyLab 61 mk3 DAW
Control
1
Expression (coarse)
127
04:41:25.882
From KeyLab 61 mk3 DAW
Control
1
Expression (coarse)
0
I canāt get it to do it right now - but Iāve seen it, when I was first messing
What plugin are you controlling at the time - Analog Lab 5? And what mode are you in on the KL3 - Arturia?
If you are in DAW mode (either plugin or mixer, there are 2 sub-modes) try going into Arturia mode for your sound design - and then switch to DAW.
Iāll keep a check on my system and report back if I get it to do it again and have more insight.
Hello,
I was going to report it too as Iām facing this issue exactly for a couple of weeks.
KeyLab 61 mk3
Logic Pro 11.1
MacOs Sequoia 15.2
MacMini M4
To me this happens on non Arturia plugins only (eg Alchemy, Pianoā¦). As soon as the knob is touched, the sound gets muted and remains so. Strangely, touching the knob resumes the audio, but only when a finger touches it ; when untouched, the instrument keeps mutedā¦
There is no systematic recovery strategy. Sometime turning off then on the plugin is enough, sometimes itās not. Alchemy recovers this way, Piano randomlyā¦
This happens in DAW mode, not in Arturia mode (seems the midi is not directed to the DAW).
I havenāt dived in the Midi details here, no expertise for that. But itās obviously a bug either in the integration script or in our kbd firmware (I doubt)
Iām experiencing a similar issue. The knobs and fadersā progress displays blink in and out, then after several seconds of making changes, the audio cuts out completely and I have to reset the controller. Iām using the following:
KeyLab 61 mk3, Firmware 1.1.1, set to Logic as DAW
Logic Pro 11.1
MacOs Sequoia 15.2
MacBook Air M3
Iām not using a USB hub. Perhaps itās down to waiting for Sequoia certification, but either way looking forward to a resolution.
Hello. Iāll add my name to those experiencing the same problem. As well as sounds cutting out, Iāve had random pan/balance issues too.
Iāve tried using Mainstage to see what MIDI signals are being sent out by my Keylab and itās not just the 4th knob at fault. Iāve found that - in DAW mode with Logic as the DAW - when any knob is touched, a MIDI CC message is sent with a value of 127 and then the same CC sends the value 0 when it is released.
Knob 1 sends CC8 (balance), knob 2 CC9 (undefined), knob 3 CC10 (pan), knob 4 CC11 (expression) and so on ā¦ this makes DAW mode unusable at the moment. In fact, in Mainstage, you can even see the expression control on the channel strip flip from 0 to 127 as knob 4 is touched and then released.
If it helps, Iām using a Keylab 61 Mk3, firmware 1.1.1 connected to a MacBook running MacOS 12 Monterey and Logic Pro 10.7.9.
Looking forward to a fix as Iām having to try to adapt one of the user profiles to control Logic at the moment ā¦
You are right, we discovered this issue with the 4th encoder and also the 3rd one that will pan the sound in Logic stock plugins when using the Logic script and DAW program.
The problem is, as you describe it, related to the touch sensitive function. Very sorry for that.
ā This has been discussed with all teams involved and developers are already working on a fix. It should come in the next firmware and Logic script update.
In the meantime, a workaround exists: youāll need to add on the Logic stock plugin track a CC filter (MIDI FX āModifierā) for CC11 for the 4th encoder as follows:
ā So Input event to CC11 Re assign to Off and Thru button deactivated.
ā For the 3rd encoder the concerned CC is number 10.
Please let me know if yuou have any other feedback,
Kind regards
