If that’s the case with the current keylabs then I agree that’s a bit of a backwards step. When the first Keylabs were launched, you could modify pretty much everything by putting the unit into Edit mode with the Edit button under the display and scrolling through the setup menus. It was way harder than just using Midi Control Center, but it was very possible.
I recently watched a video programing the Keylab MK2 manually like you said.
LoL, one of the comments i read " i watched the video ten times then smashed my keyboard"
It was soooo painful to follow.
The Keylab MK3 from what i seen, maybe improved… im not sure.
Best Regards,
I will test this on the MK3 on Tuesday. I’ll let you know then 
At least it is possible to make custom modes and name everything on the device itself.
Alright, replying to myself. Indeed you can configure everything on the nice built-in screen itself on the Keylab MK3. It is gonna be perfect for my dawless setup. Out of curiosity, I tried to run Analog Lab Pro from Linux via Crossover (Wine). It works out of the box but obviously I have to investigate how to enable low latency audio.
I use a recent Linux distribution (KDE Neon based on Ubuntu 24.04) which uses Pipewire so it should be pretty capable without much tweaking, but I am definitely looking for pieces of advice and… a Linux build 
But as far as I am concerned, my objective is to keep from the computer as much as possible anyway
BTW, I played a little. It is indeed a very good keyboard, looks great & sturdy. You can play with expressivity. I think I slightly preferred the feel of my former Blofeld keyboard (Fatar TP/9S), which was more firm, but it was also kinda clacky / noisy and the velocity curve was unsatisfying on mine. (might be my unit ; I tested a STVC which was better, while supposedly exactly the same keybed) So. Yes. The Keylab MK3 is great. I hope it’s gonna be durable. I think so.
I plan to keep this very setup (Keylab + Roland Verselab) for years Maybe just add a single external synth (a Minifreak maybe) to spice things up with an extra layer. (as the Verselab has 7 synths / samples tracks + a vocal or external instrument track)
Salut Bidinou, 
The best way to decrease latency is by going native, using ALSA and native plugins like Surge XT. Wine, Yabridge, Pulseaudio, Pipewire all add a extra layer and extra latency.
« ALSA (Advanced Linux Sound Architecture) est le système audio fondamental utilisé sur les systèmes Linux. Il gère directement les interactions avec le matériel audio, comme les cartes son, les microphones et les haut-parleurs, grâce à une couche de pilotes matériels»
CF. PipeWire, PulseAudio et ALSA : tout savoir et les différences, malekal.com.
“ALSA (Advanced Linux Sound Architecture) is the fundamental audio system used on Linux systems. It directly manages interactions with audio hardware, such as sound cards, microphones and loudspeakers, through a layer of hardware pilots.”"
“ALSA (baked into the Linux kernel) provides necessary device drives to read and write from the sound card.” But ALSA takes control of the hardware, one app at a time, which is what you want for a low-latency DAW.
PulseAudio and PipeWire are global sound server allowing many apps to use ALSA.
Hi ! Thanks for your reply !
Agree regarding ALSA. I kinda had the feeling Jack (which can used on top of alsa or oss, right ?) would maybe eventually be superseded by Pipewire or at least would lead to better latency than Pulse (on top of Alsa).
I already had great sub 1 ms latency with a good sound card and Jack (on top of Alsa) in the past but thought that kind of setup kinda turns away users who just want low latency audio to work out of the box on a regular distro without tinkering too much. I really barely followed the Pipewire subject. I thought it could answer to this issue.
Sorry for the quick kinda clueless reply. My former low latency Jack or pure Alsa with no pulse experiments were in… 2012
I’ve used Jack extensively. By default, Jack uses ALSA as driver.
Jack is more efficient than Pipewire or Pulseaudio but it’s not as transparent as ALSA when it comes to mapping in the Graph window. It uses generic tags like Capture and Playback while ALSA will use tags like hw: impact for Drumbrute or hw: A37 for Keystep37.
The drawback with using ALSA is that you have to stop Puseaudio or Pipewire from using ALSA because ALSA is a one only app (like Reaper, Ardour).