I just got my hands on a Keylab 88 MKII and I have to admit its been a bit of a headache assigning all the midi after upgrading from a old M-Audio 61 that was almost ALL plug and play. I seem to have mapped out a User profile that allows me to play my VSTs within FL Studio with no issue. However, I seem to have 2 issues left.
I can get use out of my mod wheel within an instance Omnisphere, however, I am having to assign the mod wheel every time I open Omnisphere instead of FL Studio knowing that is where I want that CC controlled. There is a way for it to have settings saved for every time I open Omnisphere?
For the life of me, I cannot seem to get the pitch wheel to respond, again in Omnisphere. I feel like there must be a setting somewhere in Midi Control Center that I have wrong in my user profile.
My apologies in advance for idiot questions, I have spent all weekend watching youtube videos and reading forums to no real avail.
Win 10 Home 64 bit
FL Studio 24 (latest)
Keylab 88 MKII
RME Babyface Interface
If you have a standard normal default setup, then the controllers modwheel is set to midi CC#01 with the range 0-127, and the pitch wheel/ bend is simply that.
It should be just as easy as you say M-Audio was, as that this setup is standard generel midi setup.
Have you checked your controller work and is set to send out the correct midi messages?
I suggest you use a midi monitor to check the controller midi output work and is correct.
Perhaps follow the controllers manuals instructions to do a factory reset, if you get no midi output.
The rest should be about your DAW and/ or instrument - in this case Omnisphere.
I would assume Omnisphere by default react to this setup and then does what it’s set to do. If the controller messages do not arrive to Omnisphere then it’s something in your DAW that need to be set correct. That is if the controller work as it should.
I don’t use FL Studio or Omnisphere. I also don’t have the controller.
If your keyboard has mod and pitch set to send the default MIDI messages, then using the default FL Studio project template will let mod and pitch control those things in all the VSTs - provided the VST itself can/will respond to them.
If you use your own template (like me), you can add those controls to the plugin wrapper - the ‘container’ FL Studio uses for VSTs - very simply. They then work with any VST that responds to those messages.
EDIT: I don’t have Omnisphere to try, but I saw this in the FL Studio forums:
In omnisphere, right click a control and choose ‘enable host automation’, your chosen control is then able to be linked from the browser under current project/ generators / omnisphere…
Hope that helps you
1 Like
_Need help ?
When you can't find the answer online or in the product manual, the Technical Support Team is here!.
_Stay tuned
Follow us for the hottest sounds, fresh content, exclusive offers and Arturia news as it happens.