Midi Wheel not working in FL

Audio Plugin Hosts and other audio software applications discussion
Post Reply New Topic
RELATED
PRODUCTS

Post

:help:
The modulation wheel of my midi keyboard is not working in Fruity Loops when I am using VSTis. Only the midi notes ,the velocity and the pitch bend wheel work. In other hosts my midi keyboard works perfect. What can I do? :?

Post

You have to assign the modulation wheel to the parameter you want to control (menu link to controller).

Post

But I want to use the modulation wheel as a modulation wheel.

Post

brurez wrote:But I want to use the modulation wheel as a modulation wheel.
I believe the Modulation wheel is cc1. Can you map it that way?
-="I beat the Internet...the end guy is hard"=-

Post

drez wrote:
brurez wrote:But I want to use the modulation wheel as a modulation wheel.
I believe the Modulation wheel is cc1. Can you map it that way?
Yes, you are right. The problem is no have a parameter like "modulation wheel" in my vsts synths to link to CC1. :cry:

Post

You have to make a MIDI Out or Dashboard which will send it over. Make the knob or slider set to CC1, and then link it to the modhweel; then port over the MIDI.

Post

More simple : tweak the parameter you want ot automate with the CC1, then go to the plug'in menu -> Last tweaked parameter -> Link to controller -> move you modulation wheel, it's done!

Post

usob solina wrote:More simple : tweak the parameter you want ot automate with the CC1, then go to the plug'in menu -> Last tweaked parameter -> Link to controller -> move you modulation wheel, it's done!
Simpler, but really just a workaround. It doesn't solve the problem, and is lacking for many (if not most) situations.

Post

usob solina wrote:More simple : tweak the parameter you want ot automate with the CC1, then go to the plug'in menu -> Last tweaked parameter -> Link to controller -> move you modulation wheel, it's done!
the problem is that i dont have the parameter to automate (virtual modulation wheel ), i cant link the virtual modulation wheel with the real one. :o

Post

What synth are you using?

Some synth's don't respond to CC1, so you can't use a MIDI Out.

Others don't expose the mod wheel as a vst parameter, so you can't use the last tweaked method.

Post

some synths just require you to choose what you modulate with your CC- I for one prefer this method as I have a choice.
Yes, you are right. The problem is no have a parameter like "modulation wheel" in my vsts synths to link to CC1. Crying or Very sad
the mod wheel on a hardware synth is just tweaking a predetermined parameter on the synth anyway[/quote]

Post

Hello Relik (or anyone else that can help),

You had made a post regarding the modulation wheel in Fruity Loops, well I read your post of a solution...

"You have to make a MIDI Out or Dashboard which will send it over. Make the knob or slider set to CC1, and then link it to the modhweel, then port over the MIDI."

I don't really understand what you mean by using the whole MIDI OUT function in FL, the reason being is if you are using a MIDI controller or keyboard, the don't receive MIDI OUT messages, they just send them, so my question is for example using any the CM or Linplug plugins how does MIDI OUT work to solve the problem of the modulation wheel? Are you supposed to try to get the plugin to answer the MIDI OUT signal somehow?

I have a Evolution mk-461C, and the modulation wheel is set to CC1 already, but Fruity Loops does not recognize the mapping, just the pitch wheel, why it does that is a mystery to me?

Thanks in advance.
Rellik wrote:You have to make a MIDI Out or Dashboard which will send it over. Make the knob or slider set to CC1, and then link it to the modhweel; then port over the MIDI.

Post

Right; the MIDI Out's signal is sent over to the CM or Linplug plugins. FL *recognizes* the signal on CC1 that is sent when you move your mod wheel on your mk-461C, but it does not sent it over to the plugins automatically, so Fruity Wrapper does not itself recognize the MIDI signal. However, if you align the Wrapper's MIDI In port with a MIDI Out's MIDI Out port, then it WILL recognize all CC signals.

For FL to recognize MIDI coming from your controller, it must be mapped specifically to a knob or slider. But within FL, MIDI can be sent freely over the MIDI ports, which is why the Fruity Wrapper will recieve the signal correctly from a MIDI Out, but not from your mk-561C. The solution, therefore, is to explicitly map the CC's from your mk561C to knobs in a MIDI Out, and configure those knobs to send on the correct CC. Then you can align the MIDI ports between the MIDI Out and the Fruity Wrapper so that the plugins recieve the MIDI. The reason for this is so that you don't have to explicity map everything for every plugin you want to use; you only have to do it once, on the MIDI Out, and it will send all the MIDI you have already mapped to whatever plugin it is aligned with.

I think it's pretty clear that I don't understand your question :P but I tried to be as clear as possible, but it's not easy for me to explain. I don't know why Image-Line decided that FL should send over the Pitch Wheel data to the plugins but not the Mod Wheel data; that is a mystery.

Post

Because if they didn't - you would have to "Always" use Mod wheel as mod wheel. Instead - you have flexibility to do that, and much more - because FL allows you to bind it to anything.

Post Reply

Return to “Hosts & Applications (Sequencers, DAWs, Audio Editors, etc.)”