Erroneous channel muting sent once at startup (custom mode)

Lab KeyLab
#1

Hi everyone !

Been using the KeyLab MK3 (in custom - dawless mode) for a week. I am pretty satisfied with the keyboard, along with a Roland Verselab MV-1 groovebox.

I have one single issue. (also occurs after updating the firmware to 1.1.1 and with the default 1.0.1)
Shortly after powering on the KeyLab, an unwanted MIDI event seems to be sent to the Verselab, muting the current channel on the Verselab (if I switch channel before it occurs, it applies to the new one).

It takes a second to unmute it manually on the Verselab, so it’s not too serious, but still could be bothering.
It does not occur immediatly after turning the KeyLab on. Usually, I can play for half a minute before it occurs, sometimes it is almost immediatly after the KeyLab has initialized. (it starts automatically in custom/dawless mode).

It happens with default out of the box settings.

Any idea ? I am sure it is almost nothing, probably just an option to untick somewhere ! Thanks for your help !

#2

Hi!

If this problem continues, please raise a ticket with our suppor team and they will be able to troubleshoot this with you.

https://www.arturia.com/fr/support/ask-for-help

Thanks

#3

Hi Joe. Thank you for your reply, much appreciated.

So, I opened a ticket and quickly got a very kind and exhaustive answer from the Arturia team. The investigation continues, I’ll let you know ! :slight_smile:

#4

OK so, we figured the issue out.
The Verselab, for some reason, mutes the current track when it gets the following MIDI event (sent by the Keylab about 20 seconds after startup) :slight_smile:

20:0 Control change 7, controller 11, value 1

It can be disabled by disabling the expression pedal on the KeyLab (which I don’t have anyway).

I also noticed that some seemingly random keys were sustained. This time it was due to the following event, worked around by disabling the aux pedal :

20:0 Control change 7, controller 66, value 126

So : problem fixed for me. But, is that due to a bad MIDI implementation on the Verselab side, or on the Keylab side ?

If I ever need to add an expression pedal to my Keylab, I might have an issue. (expression pedals ARE supported by the Verselab)

I’ll mark this issue as solved as soon as I figure out if this is normal behaviour or not :slight_smile: