I have a keylab essentials mk3 and a minilab3 and the behavior is the same for both of them. I have created several user templates that are saved in the midi control center application for both keyboards. When I store my user templates to the device memory slots, the first one shows the actual name of the template and the name doesn’t show for the rest. It keeps the “User 2”, “User 3”, etc name. I’ve verified that it is indeed uploading the template to the device but is there a way or something I’m doing wrong that is preventing the name from showing up when I’m selecting on the device? Any help is greatly appreciated.
EDIT: The name of the first user template seems to be baked in the User 1 slot because now when I store a different user template to User 1 it still shows the name of the template that I originally stored there. Extremely confused, I just want to simply scroll through templates on the controller and have each one be the name I’ve given it in the software . . . . is this not possible?
I have two templates made up. One called Drawbars (for my organs with have the faders reversed, and on midi channel 2) and one called Mixer, which I use to adjust volumes in GigPerfomer.
On my E3 I can scroll through them and the name comes up on the screen. I have user 3-6 turned off so they dont appear on the screen.
Is this what you want to do but can’t?
Im at work at the moment so can’t try this, but im sure I saw that both Drawbars and Mixer are under User 1. I remember thinking it strange at the time. I could be wrong, but AFAIK ive never used User 2.
Try loading them both to User 1.
I think it’s probably a bug with MCC, because I watched a video on this topic and it worked for the person who created the video and he had the same firmware version that I have for the minilab3 and the video was created before the latest version of the MCC was released which is what I currently have.
Have you created any new templates since the latest release of MCC? I have the latest/greatest release of MCC which is:
Midi Control Center 1.18.0.247
Build 247 Revision: 86275db
Build date: Aug 12 2024 13:56:55
I’m curious to know how to “turn off” user slots. I can delete local templates in the MCC software but have no idea how to delete device memories on the controller. Let me know how you accomplished that and if you are able to get this to work with the latest MCC release. Thanks in advance!
Yup, I went back to the previous version as well and all is working fine now . It’s hard to believe that they don’t have test cases that would go through all these functions to verify that nothing gets broken. And thanks for the heads up on how to disable some of the user slots. I never realized that the ability existed!
Using the previous software version. (1.17.2.94), the name is showing up fine on my keyboards display.
Is it possible for it to also show up under Device Memories in MCC?
For example, I have “Keylab E 49 Halion” as “User 1” and on the Keylab Essentials keyboard , the display correctly shows as “Keylab E 49 Halion”. but under Device Memories in the software, it just says “User 1”
Same problem here. Created a local template titled “SH4d”, stored it to device memory “User 1”, but on my controller (Keylab Essentials Mk3) appears as “Digitakt” when I go to program 1, the name of some other local template I long since have deleted. This is really disappointing from Arturia. I really thought I had found the perfect MIDI controller ecosystem.
You’re all right, this is a regression in the latest 1.18.0 version of the MCC.
It will be fixed very soon in the 1.18.1 where all the templates names will be stored on all our 3 new controller: MiniLab3, KeyLab Essential 3 and KeyLab 3.
I will try to think about notifying you here when we release it.
Or, if you open the MCC and it propose the update to the 1.18.1 version, you can go for it
I wonder if it is planned to release an Apple Silicon native (or universal) version of MCC for the Mac? Currently it shows this as being an intel native application and relying on Rosetta to work. From a functionality perspective it likely makes no difference so it’s likely of low priority, but at some point in the MacOS cycle Apple is going to drop Rosetta and force all silicon native apps as Rosetta adds in a whole lot of extra compatibility overhead.
We understand that there is a time lag between the development and correction of a feature, but can we have any prediction of when this correction will be implemented?
This is really frustrating. At my shows I get lost in which program I’m actually in…
Hi @Rafa_Barros and welcome to The Sound Explorers Forum!
I’m afraid Arturia, rarely, if ever, publicly make announcements such as this.
The best way to be kept up to date is to keep an eye on Arturia’s Social Channels or to subscribe to The Arturia Newsletter to be the first to know about them.
