Glitchy noises when moving faders in DAW mode

[diordna]

Hello.

I recently got the Keylab MKII 61. Really nice so far. I have encountered a problem that I would appreciate assistance with please. The faders in DAW mode sometimes will generate a high pitched noise that sounds kind of like a really fast hard sync or even a geiger counter click. This happens when using my DAW (Ableton Suite 10.0.5) or when using the Keylab with Arturia VST software in stand-alone mode. When it happens in my DAW the issue isn't exclusive to Arturia instruments. My Keylab firmware is 1.0.10 and this is running on a Windows 7 OS. I can share an audio sample of the sound if you wish.

[Solaires]

This also happens to me, same Ableton version, but on Windows 10. Super strange

[markpray]

I had the same issue but was able to eliminate the sound by making sure the inputs are not using "all ins" and instead selecting a specific input device. In this case I think it should be "KeyLab mkII 61".

[diordna]

Solved:
Ha. Yes, Markpray. I was just jumping on to say it has been fixed. We had the same issue apparently.

For anyone else that may be experiencing this, in Ableton under Preferences/Link MIDI the Keylab shows up in a couple places. #1 Under Control Surface (where it should be) but also under the midiports right below it. Turned off tracking on those other instances and problem fixed. YAY.

[diordna]

Addendum:
Everything was working with the exception of being able to select the MKII in the "Midi From" port in Ableton. After a bit of fiddling with the midi setting I finally got it to work. I'm guessing my situation is kind of a fluke as I haven't seen a lot about this in the forums or online but if anyone else has similar issues, maybe my setup can work for you. (pic attached)

[mscman]

Thank you! Just upgraded from the Essential 61 to the MkII and couldn't figure out why my piano track in my live set was acting up when I touched the volume fader. It made an awesome sound like scratching a coin across a piano string, but it was NOT what I needed during practice. So glad to have found the cause here.

[backbackpump]

hello - I've got the same issue. Is there supposed to be two listings for the keylad under midi ports, or is this a glitch?

attached an image of mine

[LBH]

hello - I've got the same issue. Is there supposed to be two listings for the keylad under midi ports, or is this a glitch?

attached an image of mine

Hi and welcome to Arturia forums.

Have you looked at the solution posts in this thread - including the posted images?

[seec1111]

hello - I've got the same issue. Is there supposed to be two listings for the keylad under midi ports, or is this a glitch?

attached an image of mine

The first one is Keylab MIDI signal, and the second one is Keylab Daw Signal.
I think the glitchy noise is generated by Ableton routing the daw signal as midi signal to the track.
I tried to turn off the "track" button of the second one and solved.

(If turn off the "track" button on both signal, there is no sound even I play the keyboard, I think the reason might be there is no midi signal from keylab can go into the "track" even the keyboard. So I keep the first one on)

[tosbenson]

I have the same problem with my brand new Keylab 49 MK2 which i just purchased. However i use Logic Pro X. Does anyone know how to fix this in Logic. Thanks

[Sandmath]

Hi guys, same kind of problem here...

I have the mkII up to date, working in DAW mode with logic pro 10.6.2. I can't assign any fader to automation quick access, bu I can assign a knob without any issues... Very weird !

I tried reinstalling Logic, same with the MkII, looking in the preferences, deleting the old files in the user library... It seems that a conflict between midi signals is occuring but I can't figure how to solve this...

Thanks for your help !

[soundlake]

Hello, is there any Reason user here?

I could fix Ableton Live, but in Reason, I'm lost. Any idea?

[Wacho76]

Hello how are you?

Did you solve the problem, I have the same problem

[is_ryan]

I had the same issues in Ableton Live 11. Removing the Port 2 Track setting fixed the problem for me.