After updating to version 5.3.3, the MIDI Learn function on my Mac Mini (MacOS 27) no longer works.
It’s not the controllers; they are fine. Everything works in Cubase and in the standalone instruments.
What could be causing this?
It is the same problem on my MacBook…
Do you mean you cannot set up midi learn?
Or do you mean that controllers that were set up previously using midi learn do not seem to continue working?
I mean midi-learn. I use midi-learn to control instruments. For example the change the cutoff of a bass vst3 bass instrument or a vst3 percussion instrument.
Let’s see the global MIDI monitor. Are your controllers sending Sysex messages by any chance?
Thank you for your answers, I think I have found the issue. It seems that only Korg nanoStudio and nanoKontrolStudio have the poblem.
Thank you for your answers, I think I have found the issue. It seems that only Korg nanoStudio and nanoKontrolStudio have the poblem.
Nothing about MIDI Learn changed between 5.2.2 and 5.3.3
Please share what you found - as I said, nothing has changed with the latest release and so if those worked before, they should still be working
Oh, thanks…I didn’t notice that.
OK - so to be clear - the confusion was around “Midi Learn” because you weren’t in fact trying to have GP learn your MIDI messages, you were trying to have a plugin learn them and that requires all messages to pass through a MIDI In block.
We decided to block CC messages by default because we were seeing too many issues where CC messages were being passed to plugins inadvertently by moving sliders or even by having sliders move slightly due to vibration, and consequently often screwing up the sounds.
I would encourage you to read this blog article and switch from having your plugins learn MIDI messages and instead use Gig Performer’s support for host automation which is far more flexible.
Thank you for the information. I usually use widgets too, but sometimes—especially when things need to be quick and spontaneous—I need direct access to the instrument.
