Hi
I have successfully got Arturia Keylab Essential 49 to work as a standalone in all areas advertised.
In Cubase 13 i can load an instrument Into a track and all is great again.
If i make a second instrument track and load in another instrument even in the Arturia range, Knobs and sliders work but the centre screen where you change sounds shows the last instrument sound on the last track. You can scroll though your new instrument sound and press then press the centre Knob to establish the sound, but the screeen still shows the last sound on the first track instrument.
It seems to me that it will only allow one instrument full operation.
I even tried giving a track a different midi channel to no avail.
If anyone knows what i mean and can help, it would be very much appreciated
Is it possible for all sound changes to be made on the Arturia Essential 49 on different tracks or multi tracks?
Hi,
I totally see what you mean and I have exactly the same problem.
Unfortunately I didnāt find the solution.
I agree with you, itās very frustrating!
I wonder if the new Keylab MK3 (not Essential) have the same problem.
I just have had the black screen of death and hardware problem and just ordered a new machine from Scan.
When i get my new machine I will report back.
It was beginning to struggle with Artuia VST X plugins and was 7 years old.
Apart from that the Arturia support said it is a known problem waiting for an update.
All the Best
John
Ok, just installed it. So, just to be clear, what you both describe, is that when we change our selected track, its title is not shown on the display? (Weāre not talking about the instrument name, right?)
JohnS explained very well the problem.
I canāt verify now but if you start by loading an Arturia instrument (or Analog lab) everything works fine : youāve got the name of the instrument and the name of the preset displayed on the Keylab screen .
If you load a new instrument on a second track, Keylab always displays the first track.
Instrument title and track title are two different things, this is why Iāve asked. So, to me, itās not clear what you both expect to see on the screen and what is actually seen. Note that Analog Labās and V-Collection instruments can surely be seen correctly on the display, even whichever patch is selected. This is not the same, when weāre talking about the midi remote and other instruments. Anyway, from what I see in the script, it properly sends the trackās title (totally irrelevant with the plugin name). If you would like to see the plugin name as well, they should simply add the mOnChangePluginIdentity event, and send it from there.
Sorry m.c, Iām not very precise because Iām not in front of my computer. Iāll look at it as soon as I can but what is certain is that the script cannot manage the display of several instances of Arturia plugins. The Keylab display remains stuck on the name of the track and the name of the instrument of the first instance.
if there is no Arturia plugin, the Keylab displays the name of the tracks without any problem.
I was able to test and I can now specify the problem. In DAW mode the Keylab displays the name of the tracks in Cubase and it works. In Arturia mode the Keylab displays the name of the instruments and presets. In standalone mode it works well since only one instance of Arturia plugin is open. But in Cubase you can of course create several tracks with different Arturia plugins. And in this case if you switch to Arturia mode, the Keylab will only display the name and presets of the first Arturia plugin opened, regardless of the selected track. So I donāt know if itās a problem related to the Cubase script or a limitation of Arturia that doesnāt allow the Keylab to display several instances of Analog Lab on different tracks.
That is it in a nutshell.
We will have to wait until Arturia bring the update out.
Meanwhile as you say. The first track works in Cubase displaying sounds. All other tracks work but you have to change sounds on the vst itself and the dial works and you can go between sections to a sound that you want but no display. Only on the first track.
Itās quite normal, totally on Arturiaās side BUT I wouldnāt blame them at all. The thing is that Arturiaās implementation has to know somehow the VST instance loaded in the track.
NI dealt with this by adding a special parameter in its Komplete Kontrol VST. This parameter reflects an index of Komplete Kontrolās instance. So, then, NIās implementation, knows that in track X, an instance Y is loaded and properly reflects this to NIās Keyboards. I know because when I created a midi remote script for the Komplete Kontrol MK2, I had to get into this thing deeper.
Now, Arturia can do pretty much the same: Add a special parameter to each VST (itās not just AL), then the midi remote script can actually read when requested, this parameter, and notify the controller accordingly.
I opened a ticket at Arturia support and have already an answer.
Apparently they didnāt understand the problem (or I explained it badly).
But what surprises me is their recommendation for configuring MIDI ports in Cubase :
āDo not forget to disable the KeyLab Essential mk3 MCU/HUI / KeyLab Essential mk3 DIN THRU / KeyLab Essential mk3 ALV port in āStudio/Studio Setup/MIDI Port Setupā, otherwise` it is possible that you will hear some pops and notes when using the Transport function.ā
āKeyLab Essential mk3 ALVā isnāt it necessary for display?
They seem to advise enabling WinRT too.
In any case I donāt think this changes anything to our display issue.
I assume they meant to disable the checkbox in the column In āAll MIDI Inputsā.
This doesnāt prevent Cubase from receiving signals from that port, but merely stops that port from sending notes and CC messages to a Track thatās using āAll MIDI Inputsā as the source port.
