I'm not actually sending midi data from FL to RC (I've tried with and without the pipe from the Notes channel, just to see if it mattered. It does not.) Rapid Composer defaults to MIDI Channel 1 when being hosted as a VST, so that isn't the trouble either.dsan@mail.com wrote: I'm not completely familiar with FL Studio so may be off base here; however, the most common mistake made is routing. I wonder if you have told RC which port/channel to transmit MIDI notes on and if you have told Patcher which port/channel to receive on.
FL Studio is a little weird here. What you would normally call a MIDI Channel is actually called a Note Color in FL (goes all the way to the fruityloops days, not sure why its done that way.) MIDI 0 is a port (there are 256 midi ports internal to FL Studio; each one has 16 "colors.") which we send to in Patcher #1.dsan@mail.com wrote:It appears you have told Patcher to receive on MIDI 0 ("Activate MIDI In 0 for Patcher #2"), but have you instructed RC to send via MIDI 0?
dsan@mail.com wrote:Can you post a pic of the RC track dialog? Right click on the left side of the track to bring up the track dialog.

VST.dsan@mail.com wrote:Are you using RC as vst or in stand alone mode?
If i host in Reaper (v5), then RC works as I would expect. I can also use the VST version of RapidComposer along with the VST version lf FL Studio, both hosted via Bidule, and everything works. I conclude there is specifically an incompatibility with FruityWrapper.


