Quote:
Originally Posted by GeckoLikesMartini
Hmmm, just realised the same problem with bx_oberhausen in Reaper on macOS. the thing is... it seems to work in Ableton Live Lite 11, Ableton Live 10 and Reason 12 as expected with every midi channel ?
What's the difference in Reaper ?
Regards, mj
|
I found out it's not a problem, it's by design. Most of the Plugin Alliance synths only receive midi input on Channel 1, so in Reaper your midi input device must be set to channel 1, or you can use the JSFX Midi_tool II in vitalkers post.
In Ableton/Reason I believe it's to do with the default routing. It receives midi input on all channels (like Reaper can) but then assigns the midi input to channel 1 of the instrument track by default, even if your device is inputting on channel 3 (much like how the JSFX Midi_tool works).
Reaper receives midi input on all channels too, but it doesn't assign input to channel 1 by default like in Ableton. So if your device is inputting on channel 3, it will go in to BX_Oberhausen on Channel 3 too, and thus won't work because it needs to go through channel 1.