Yes, you’re right. The latest version does bugger all. I reverted back to the previous version and all works as expected.
To turn off the other user presets just go to the area below where you set Vegas etc.
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!
2 Likes
It’s like they have never tested it. Im on Mac so it’s a pretty close OS compared to Windows, how hard can it be 
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”
Thanks
2 Likes
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.
Hello there.
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.
Sorry for the inconvenience.
Cheers !
1 Like
Does this mean no more love for KeyLab Mk2 ?
Hello.
No this does not mean that.
This only means that we made a mistake on the latest controllers that will be fixed soon.
Cheers.
1 Like
Thank you very much for verifying and seeing that this gets addressed. It’s greatly appreciated!
Is it fixed yet? I dont want to update only to find it’s still the same version and have to revert back again.
Not yet.
Note that:
- the bugged version is 1.18.0
- the fixed version will be 1.18.1
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.
Hello, could someone make available the mcc with the problem fixed for Mac? I have the same problem with my ARTURIA MK3 essecial
One could think that a (regression) fix like this could be rolled out quickly? Going on 3 months since the last MCC patch release.
Click on “_Support” at the top of the page then click on “Downloads and Manuals”. Enter “Midi Control Center” in the product search field then click on “Show Archives” under the Software section and download the 1.17 version for your operating system.
2 Likes
@brian99 - Oh right, thanks, great point. BTW, I had missed your previous comment about your reverting back to 1.17. Sorry about that.
On my end, after looking at the MCC Release Notes. I’m noticing that there wasn’t any apparent change for the Minilab 3 (and Keylab Essential) since 1.17 (and even before for Minilab). So there’s no need to be waiting for the next patch release that’ll revert the breaking change. Looks like 1.17.2 is the best candidate to avoid the template naming issue. Thanks again!
Hello.
We did release the 1.18.1 version yesterday.
It should fix almost all preset name send/recall problems.
The only exception is MiniLab3 preset name recall that will need a FW Update to be working.
Don’t hesitate to report here if you are still experiencing issues on this particular topic.
Cheers !
1 Like
(EDITED)
@Tim.Arturia - Thanks for the info. Reading the MCC Release Notes bullet for Minilab 3: MiniLab 3: Fixed the preset name transfer when using the “Store To” feature.
So it’s the Recall From functionality that’ll require a Minilab 3 FW update, corrrect? If so, can you confirm that the Minilab dev team has that in their next update to be released relatively soon? Just asking because there hasn’t been a FW update for a while. I’m not really depending on this because I always push but I can imagine other users wanting that.