Page 1 of 1

Pitch Bend/Mod Wheel problems

Posted: Sun Mar 01, 2015 11:07 am
by Perfect Human Interface
I'm trying out the pitch bend module and I notice something odd. Both the pitch bend and mod wheel on my keyboard adjust the output of the pitch bend module. Clearly I can't utilize both if they're both tweaking the same parameter.

I don't know if this is a Flowstone niggle, if it's part of the MIDI standard, if it's my DAW (FL Studio and I can't find a setting), or if it's my keyboard/drivers. If anyone can confirm for me whether this behavior is unique to my situation that would be cool.

Also I tried linking the wheels to other things in FL while I was fiddling, and afterwards Flowstone stopped responding to both (the module's output wasn't updating). Then as I clicked around the windows the mod wheel started responding (again controlling pitch bend) intermittently, but still nothing from the pitch bend wheel. They still work fine for other things in FL.

I am using the FL version of Flowstone in case there's any chance of that being the root of the funkiness.

Re: Pitch Bend/Mod Wheel problems

Posted: Sun Mar 01, 2015 3:55 pm
by KG_is_back
Pitch bend wheel data is send as message no.224 where data1 is LSB(0-127) and data2 is MSB(0-128). The value for the pitchbend is calculated as MSB*128+LSB=(0-16383).

Mod wheel is send as message midi CC 1 (MSB) and midi CC 2 (LSB) (optional - for higher mod weel precision - not all devices support that). The value of the mod wheel is calculated as (MSB*128+LSB)=(0-16383) or you just use the MSB=(0-127) for lower precision.

MIDI CC are send as message no.176, where data1 is the controller number(0-127) and data2 is the value (0-127)

connect "midi in" in your flowstone to midi splitter prim and have a close look, what it shows in the status byte. 224 is for pitch bend and 176 is for mod wheel or any other midiCC. That way you can check what your daw is giving to Flowstone.

Re: Pitch Bend/Mod Wheel problems

Posted: Mon Mar 02, 2015 2:30 pm
by Perfect Human Interface
I've figured out the problem. I had a "generic link" set up in FL Studio where the mod wheel was permanently linked to the channel pitch setting. Only thing is now I can't receive MIDI from either pitch bend or mod wheel unless I select my MIDI keyboard directly as the MIDI in device instead of going through FL Studio. Is this expected? The confusing thing is that at first it was receiving the pitch bend wheel too, but then quit when I started fiddling. I'm guessing maybe I had generic links on both controls but I had overridden the pitch bend wheel unwittingly.

OK so MIDI splitter shows status 224 for when the channel pitch in FL is adjusted, and status 176 for when channel volume and panning controls are adjusted. Flowstone does not automatically grab pitch bend and mod wheel input from the keyboard unless the MIDI input device is set to the keyboard driver. Otherwise I have to actually link the wheels to something in FL for FL to send the MIDI to Flowstone. Seems reasonable enough.