As long as FL Studio has been around you could map nearly every parameter in the software to a midi controller, however the transport controls are unmappable. If FL doesn't natively support a certain midi controller it is impossible to get transport controls working for that device, this needs to change. I urge Image Line to expand the Transport Control mapping capabilities so that one can manually map these controls to any desired parameter, this would improve live performing and looping in FL Studio for so many people.
On top of that, it would be nice if FL Studio provided a list of omni controls such as Modwheel, Pitchwheel and Aftertouch on default, so that it is easier to map them, at the moment one has to hope that FL Studio recognizes the controls on your device, but if you have for instance two different keyboards connected, it will almost certainly only accept these controls of one of the two, and you can't add a second row of Omni controls.
Transport Controls and Omni Controls
Return to “MIDI Controller Support”
[You can only see part of this thread as you are not logged in to the forums]
Re: Transport Controls and Omni Controls
Hello Auro_Prime,
FL Studio uses MMC messages ...
Re: Transport Controls and Omni Controls
The transport controls are MMC, but they still ...
Re: Transport Controls and Omni Controls
Alright I fixed it, the problem was, that the M...
Re: Transport Controls and Omni Controls
FidelityMusic (IL) wrote:Hello Auro_Prime,
FL ...
Re: Transport Controls and Omni Controls
"...Korg Taktile for instance. I cannot get it ...
Re: Transport Controls and Omni Controls
NTO wrote:"...Korg Taktile for instance. I cann...