Hi,
Since the very last updates with Arturia Software Center (I don’t know if it has anything to do with it) I’ve got the following message when adding a new Arturia instrument in an existing project in my DAW (Cubase 14 Pro).
I don’t see where I can disable the MIDI out port. The only thing I can do is make it visible or not.
If I click OK, the message disappears and it seems to work, but it’s still quite annoying and not very reassuring.
Ich bekomme dieselbe Fehlermeldung seit Update auf “V Collection 11 Intro”.
Es ist egal, ob man auf Abbrechen oder Ok klickt. In beiden Fällen scheint die Software danach normal zu funktionieren, aber schön ist das natürlich nicht.
(Win11 Pro / Cubase Pro 14 / KeyLab 61 MK3 / V Kollektion 11)
I have the exact same problem. Can anyone help me? Is this a known bug?
Hi !
Please make sure that you disable this port :
Once done you would not be prompted to disable the midi port again.
Do let me know if there’s any further occurence,
Kind regards.
Thanks for your answer.
I will try to disable the Keylab MK3 DAW midi output but isn’t it necessary for the keyboard to function properly?
I remember that if I try to disable it I have a message telling me that the port is in use.
Unfortunately, disabling both MIDI outputs ports has no effect.
The message is still there when creating a new Arturia instrument track.
same problem
Cubase Pro 14
W11
will follow
Same, even though the port is already disabled. Clicking OK bypasses the error.
Win11
Ableton Live 11
Same error started after last update.
Win11
Studio One 7
+1 … same deal, someone broke something!
Problem solved!
I guess the problem is solved via the new MCC v1.20.0.172 and MIDI Driver 1.5.0.
Thank you Arturia!
I have updated to 1.20.0 / 1.5.0 and still get this error.
According to Arturia Support the only difference between MIDI driver version 1.4.1 and 1.5.0 is Keylab 88 Mk3 support.
You are absolute right!
After I installed the new driver 1.20 /1.5 all work’s well. I swear it!
Next day the same issue with “port error” occured again.
I hope Arturia will address this annoying thing very soon.
The error occurs in Cubase 14 Pro and Studio One Pro+ as well.
This MIDI DAW thing in Keylab mk3 is a nightmare, I never use this mode.
The “Port Error” issue is a bug that has been occurring since V Collection 11. I hope Arturia takes this issue seriously.
I get exactly the same problem with my Keylab 88.
Disabling the MIDI output port as requested has no effect.
Oddly disabling the MIDI port might seem to have an effect for that current Cubase session, but even with the MIDI output port disabled the messages start to appear again the following day (or maybe the change just has an effect for that session and the message appears again as soon as you shut Cubase down and then start it up again?).
I have got around the problem by having the Keylab switched off when Cubase 14 is started. Once Cubase has started I then turn on the Keylab 88. It takes a minute or so, but then Cubase will eventually recognise the instrument. Then the message does not appear during that Cubase session. However, this means that I can’t use the Generic Remote commands that I have set up to use from the buttons on the Keylab 88 for functions like Delete, Undo , Go to next marker etc.
Not being able to use these buttons is EVEN more annoying than the MIDI Port Error message as using these are now part of my ‘work flow’ so I’m just having to put up with the annoying error message which is less annoying!!.
I have contacted Arturia Support about this and apparently it’s with their development team so maybe we will get a fix at some point in the future?
What you describe is very interesting. Turning off the Keylab before starting the DAW also helps with my problem. The interesting thing is that I don’t use Cubase but Pro Tools on Windows.
And my problem is not just the error message, but when the error occurs, i.e. the Keylab is switched on when starting up, then the Keylab display feedback doesn’t work at all. I can still browse presets but I do not see what I do on the display and for example the encoders are not set to the current values of the current preset.
Note that I have set up the Keylab to use the Arturia plugin program and not the DAW program.
Does the Keylab display feedback work for you when the MIDI port error is displayed?
I have already contacted Arturia Support and the problem is currently being investigated by quality assurance.
Hi Jay
I can still browse presets too, but the display on my Keylab doesn’t seem to show the encoder positions according to their position in the presets whether I’ve started the Keylab before the Cubase DAW was started and I’ve had the error message displayed or if it was turned off and didn’t get the message displayed. It just doesn’t do it at all.
I’m wasn’t sure if this was because I was going through Cubase so I tried using VST instruments {native) through Windows without Cubase in between the Keylab and the VST. The Keylab still doesn’t reflect the encoder positions in the presets.
The display does show the position of the encoder on the Keylab though and reflects any movements of the knobs and sliders but it never reflects the positions of the encoders on any of the presets (I’ve tried a few of their instruments and it’s the same for all of them).
I suspect that it has always been like this with my setup and I’ve just thought that was the way it was supposed to work and so I’ve just used the encoders like that. As long as the encoders were mapped to something logical on the instrument (such as filter cutoff or ADSR values) then I’ve been happy. For anything that didn’t appear to be mapped to something I needed to use I just use MIDI learn.
I use a lot of Cherry Audio instruments which aren’t mapped and so I use MIDI learn most of the time so I suppose I’ve never notice how the display worked!!
I hope we get a fix soon as though I can actually use the VSTs this is getting annoying!
Pro Tools uses the AAX plugin format. Unlike the VST format, there is no limitation that only the first instantiated Arturia plug-in type is supported for display feedback in the current session. I don’t know if there are any differences in the encoder support.
At least with AAX it works like this: You change the preset, whether on the computer screen or via the Keylab doesn’t matter. The plugin sends the parameter names and current values for the encoders to the Keylab via USB. If you now touch the encoder, you’ll see the plugin parameter name and value on the Keylab display. Turning the encoder, the Keylab sends a MIDI controller change (via USB) with the correct absolute value.
In case the feedback is not working, nothing is sent to the Keylab. When you touch the encoder, only the encoder name and value are displayed. In the beginning the value is zero, regardless of what it should be according to the preset. If you now turn the encoder, the parameter value in the plugin jumps to the encoder value, Initially zero.
Yep, again +1, after installing the latest MIDI driver from Arturia it did go away, but now a couple days later, it’s back… wtf? This happens on my machine with a KeyLab mk2 connected, but also happens on my laptop with no MIDI devices connected.
Hello friends. First post here. This issue has occurred for the first time for me today.
I’ll keep an eye on this thread to see if there is a fix.
I’m using:
Windows 11
Ableton Live 12 Standard 12.1.11
Keylab 49 Essential firmware v 1.1.10
MIDI Control Centre 1.20.0.172
MIDI driver updated to v 1.5 this morning ( I think).
Disabling midi output hasnt helped.
Follow us for the hottest sounds, fresh content, exclusive offers and Arturia news as it happens.
